***EADDRINUSE – 102 ***
Description
Another socket is already bound to the address specified in bind
***EADDRINUSE – 102 ***
Another socket is already bound to the address specified in bind
*** EADDRNOTAVAIL – 101 ***
Endpoint address not available. This error occurs when a match for the requested address is not found in the routing table.
*** WSAEHOSTUNREACH – 10065 ***
No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
*** WSAECONNREFUSED – 10061 ***
Connection refused.
No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.
*** WSAETIMEDOUT – 10060 ***
Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.
*** WSAENOTCONN – 10057 ***
Socket is not connected.
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
Replacing default serial number with MAC address %1.
%1 – The MAC address of the Server. %BR% If the streampi config is corrupted or not found, a default config is loaded. In this case, the serial number is changed to the server’s MAC address.
*** WSAEISCONN – 10056 ***
Socket is already connected.
A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence.
*** WSAENOBUFS – 10055 ***
No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
*** WSAECONNRESET – 10054 ***
Connection reset by peer.
An existing connection was forcibly closed by the remote host. 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 (see setsockopt for more information on the SO_LINGER option on the remote socket). 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. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.