> > > When a client exits without saying goodbye, the server ... writes
> > > a 10054 (10055?) message to the log
> >
> >This rings a little bell for me.. I've never seen 10055 in a log but I've
> >seen 10054 a fair amount in both production and development.
>
> One means that the server quit unexpectedly (10055, I guess)
> and one means that the client quit (10054). I can never
> remember which is which and didn't feel like looking it up
> again.

C:\Documents and Settings\Martijn>net helpmsg 10054

An existing connection was forcibly closed by the remote host.


C:\Documents and Settings\Martijn>net helpmsg 10055

An operation on a socket could not be performed because the system lacked
suffic
ient buffer space or because a queue was full.

> >In development, if it's 10054 then client apps being "reset" while

running

> >may be the cause and not faulty NICs under these circumstances.
> >But in production, if it's 10054, then it may be the PC getting
> >Ctr-Alt-Del'ed which cuases this log entry and also not a faulty NIC.
>
> Anything that causes the connection to end without going through
> the shutdown sequence will cause that error. If you see a lot
> of them when your clients are well behaved, then suspect the NIC,
> but I'd suspect a three-finger salute first.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com