Hi folks,

  I'm getting this error ocationally on a customer's computer.  The software
was compiled using Indy 9 and BCB6.  The component that is giving off this
error is the TIdTCPServer

EIdSocketError :: Socket Error # 10053
Software caused connection abort.

  I looked in the Indy source files, and it doesn't say anything particular
to this socket error.  Any idea on what could be causing it?

  A faulty TCP Stack?   The server is running in a WinXP box, and it ran
fine for over 10 days, sudenly it started doing this.  Also some packet loss
has been registered in the network which may or not be related.

  Thanks for any help,

-Art

"Art Alvarado"  wrote in message
news:3f32ccd7@newsgroups.borland.com...

> When it says "software", what software does it refer to?

Usually the WinSock stack itself.


Gambit

> Software caused connection abort.
>
> An established connection was aborted by the software in your host
machine,
> possibly due to a data transmission timeout or protocol error.
>

When it says "software", what software does it refer to?   Indy?  Windows?

I catch timeout separetely so that "should" not be the problem.  What could
cause a protocol error?  I don't do any low level protocol handling.

-Art

"Art Alvarado"  wrote in message
news:3f32cafd$1@newsgroups.borland.com...

> EIdSocketError :: Socket Error # 10053
> Software caused connection abort.

WSAECONNABORTED
(10053)

Software caused connection abort.

An established connection was aborted by the software in your host machine,
possibly due to a data transmission timeout or protocol error.


Gambit