Discussion Locked

10054 Disconnected by peer

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I run an Telnet application over an ISDN routed connection. At the most inconvenient times the application fails and I get an error message of 10054, Disconnected by peer. Does anyone know what causes this and how I may prevent it. The remote machines are logged onto a local domain but not logged to the applications domain.

5 replies

by microsloth

Source: Server
Reason: Server closes the connection unexpected (sends reset)
Severity: Server mistake (congestion) 10054 Connection reset by peer.

This can happen if a sockets client (which includes SPX) is actively
sending or receiving data to or from SQL Server, and the network
connection is lost. This error is usually seen in conjunction with
error 17824 when on sockets-based connections. For example, an NT client
using the NWLink SPX transport could be selecting data from SQL Server, and
if the network cable is unplugged from the SQL Server machine, you will see error 10054.

An existing connection was forcibly closed by the remote host. This normally occurs if the peer application on the remote host is suddenlystopped, the host is rebooted, or the remote host used a "hard close" (see setsockopt(SO_LINGER)) on the remote socket.

by mike (from canada)

It is most likely that the person that disconnected the internet from the computer you saw this message did it. If the phone plug accidently fell out of the socket, you could get this message. your modem might be defective.

This discussion is closed to new replies.