*** WSAENETDOWN – 10050 ***
A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.
*** WSAEADDRNOTAVAIL – 10049 ***
Cannot assign requested address.
The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0).
*** WSAEADDRINUSE – 10048 ***
Address already in use.
Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing.
*** WSAENOTSOCK – 10038 ***
Socket operation on nonsocket.
An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.
*** WSAEALREADY – 10037 ***
Operation already in progress.
This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
*** WSAEWOULDBLOCK – 10035 ***
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
Could not | Failed to Allocate memory ***
Memory resources not available to process request.
Could be due to limited resources, or anti-virus interference.
WSAETIMEDOUT – 10060 (140) – config|input|notification| socket timeout ***.
Communication dropped to device.
Likely network related.
WSAECONNRESET – 10054 – *** socket closed by peer ***.
An existing connection was forcibly closed by the remote device.
This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close. This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress.
audio|close|command|connect|create|http|receive|recv|soap|socket|select|send|stream error #number#
Standard networking socket error codes.
In Windows they are usually 5 digits. In Linux, 3 digits.