This is a quick reference to the winsock errors that may appear on Nuclear RAT console

===================================================================================

WSAEADDRINUSE

(10048)

Address already in use. 

Only one usage of each socket address (protocol/IP address/port) is normally 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 wasn't closed 
properly, or one that is still in the process of closing. For server applications that 
need to bind multiple sockets to the same port number, consider using 
setsockopt(SO_REUSEADDR). Client applications usually need not call bind at all - connect 
will choose an unused port automatically.

===================================================================================

WSAEADDRNOTAVAIL

(10049)

Cannot assign requested address. 

The requested address is not valid in its context. Normally results from an attempt 
to bind to an address that is not valid for the local machine, or connect/sendto an 
address or port that is not valid for a remote machine (e.g. port 0). 

===================================================================================

WSAEALREADY

(10037)

Operation already in progress. 

An operation was attempted on a non-blocking socket that already had an operation in 
progress - i.e. calling connect a second time on a non-blocking socket that is already 
connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already 
been canceled or completed. 

===================================================================================

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. 

===================================================================================

WSAECONNREFUSED

(10061)

Connection refused. 

No connection could be made because the target machine actively refused it. This 
usually results from trying to connect to a service that is inactive on the foreign 
host - i.e. one with no server application running. 

===================================================================================

WSAECONNRESET

(10054)

Connection reset by peer. 

A 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, 
or the remote host used a "hard close" (see setsockopt for more information on the 
SO_LINGER option on the remote socket.) 

===================================================================================

WSAEFAULT

(10014)

Bad address. 

The system detected an invalid pointer address in attempting to use a pointer argument 
of a call. This error occurs if an application passes an invalid pointer value, or 
if the length of the buffer is too small. For instance, if the length of an argument 
which is a struct sockaddr is smaller than sizeof(struct sockaddr). 

===================================================================================

WSAEHOSTDOWN

(10064)

Host is down.

A socket operation failed because the destination host was down. A socket operation 
encountered a dead host. Networking activity on the local host has not been initiated. 
These conditions are more likely to be indicated by the error WSAETIMEDOUT. 

===================================================================================

WSAEHOSTUNREACH

(10065)

No route to host. 

A socket operation was attempted to an unreachable host. See WSAENETUNREACH 

===================================================================================

WSAEINPROGRESS

(10036)

Operation now in progress. 

A blocking operation is currently executing. Windows Sockets only allows a single 
blocking operation to be outstanding per task (or thread), and if any other function 
call is made (whether or not it references that or any other socket) the function 
fails with the WSAEINPROGRESS error. 

===================================================================================

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. 

===================================================================================

WSAEMFILE

(10024)

Too many open files. 

Too many open sockets. Each implementation may have a maximum number of socket handles 
available, either globally, per process or per thread. 

===================================================================================

WSAENETDOWN

(10050)

Network is down. 

A socket operation encountered a dead network. This could indicate a serious failure 
of the network system (i.e. the protocol stack that the WinSock DLL runs over), the 
network interface, or the local network itself. 

===================================================================================

WSAENETRESET

(10052)

Network dropped connection on reset. 

The host you were connected to crashed and rebooted. May also be returned by setsockopt 
if an attempt is made to set SO_KEEPALIVE on a connection that has already failed. 

===================================================================================

WSAENETUNREACH

(10051)

Network is unreachable. 

A socket operation was attempted to an unreachable network. This usually means the 
local software knows no route to reach the remote host. 

===================================================================================

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. 

===================================================================================

WSAEPROCLIM

(10067)

Too many processes.

A Windows Sockets implementation may have a limit on the number of applications that 
may use it simultaneously. WSAStartup may fail with this error if the limit has been 
reached. 

===================================================================================

WSAESHUTDOWN

(10058)

Cannot send after socket shutdown. 

A request to send or receive data was disallowed because the socket had already been 
shut down in that direction with a previous shutdown call. By calling shutdown a partial 
close of a socket is requested, which is a signal that sending or receiving or both has 
been discontinued. 

===================================================================================

WSAETIMEDOUT

(10060)

Connection timed out. 

A connection attempt failed because the connected party did not properly respond after 
a period of time, or established connection failed because connected host has failed 
to respond. 

===================================================================================

WSAEWOULDBLOCK

(10035)

Resource temporarily unavailable. 

This error is returned from operations on non-blocking sockets that cannot be completed 
immediately, for example recv when no data is queued to be read from the socket. It 
is a non-fatal error, and the operation should be retried later. It is normal for 
WSAEWOULDBLOCK to be reported as the result from calling connect on a non-blocking 
SOCK_STREAM socket, since some time must elapse for the connection to be established. 

===================================================================================

WSAHOST_NOT_FOUND

(11001)

Host not found.

No such host is known. The name is not an official hostname or alias, or it cannot be 
found in the database(s) being queried. This error may also be returned for protocol 
and service queries, and means the specified name could not be found in the relevant 
database. 

===================================================================================

WSANOTINITIALISED

(10093)

Successful WSAStartup not yet performed.

Either the application hasn't called WSAStartup or WSAStartup failed. The application 
may be accessing a socket which the current active task does not own (i.e. trying to 
share a socket between tasks), or WSACleanup has been called too many times. 

===================================================================================

WSANO_DATA

(11004)

Valid name, no data record of requested type.

The requested name is valid and was found in the database, but it does not have the 
correct associated data being resolved for. The usual example for this is a 
hostname -> address translation attempt (using gethostbyname or WSAAsyncGetHostByName) 
which uses the DNS (Domain Name Server), and an MX record is returned but no A 
record - indicating the host itself exists, but is not directly reachable. 

===================================================================================

WSANO_RECOVERY

(11003)

This is a non-recoverable error.

This indicates some sort of non-recoverable error occurred during a database lookup. 
This may be because the database files (e.g. BSD-compatible HOSTS, SERVICES or 
PROTOCOLS files) could not be found, or a DNS request was returned by the server with 
a severe error.

===================================================================================

WSASYSNOTREADY

(10091)

Network subsystem is unavailable. 

This error is returned by WSAStartup if the Windows Sockets implementation cannot 
function at this time because the underlying system it uses to provide network 
services is currently unavailable. Users should check:

·that the appropriate Windows Sockets DLL file is in the current path,
·that they are not trying to use more than one Windows Sockets implementation simultaneously. 
 If there is more than one WINSOCK DLL on your system, be sure the first one in the 
 path is appropriate for the network subsystem currently loaded.
·the Windows Sockets implementation documentation to be sure all necessary components
 are currently installed and configured correctly. 

===================================================================================

WSAVERNOTSUPPORTED

(10092)

WINSOCK.DLL version out of range.

The current Windows Sockets implementation does not support the Windows Sockets 
specification version requested by the application. Check that no old Windows Sockets 
DLL files are being accessed.

===================================================================================

WSAEDISCON

(10094)

Graceful shutdown in progress.

Returned by recv, WSARecv to indicate the remote party has initiated a graceful 
shutdown sequence. 

=================================================================================================
Source: Microsoft Windows Sockets 2 Reference