socket error 错误码

 

10058<o:p></o:p>	WSAESHUTDOWN<o:p></o:p>	Cannot send after socket shutdown. <o:p></o:p> 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. <o:p></o:p>
10060<o:p></o:p>	WSAETIMEDOUT<o:p></o:p>	Connection timed out. <o:p></o:p> 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.<o:p></o:p>
10061<o:p></o:p>	WSAECONNREFUSED<o:p></o:p>	Connection refused. <o:p></o:p> 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. <o:p></o:p>
10064<o:p></o:p>	WSAEHOSTDOWN<o:p></o:p>	Host is down. <o:p></o:p> 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. <o:p></o:p>
10065<o:p></o:p>	WSAEHOSTUNREACH<o:p></o:p>	No route to host. <o:p></o:p> A socket operation was attempted to an unreachable host. See WSAENETUNREACH<o:p></o:p>
10067<o:p></o:p>	WSAEPROCLIM<o:p></o:p>	Too many processes. <o:p></o:p> 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. <o:p></o:p>
10091<o:p></o:p>	WSASYSNOTREADY<o:p></o:p>	Network subsystem is unavailable. <o:p></o:p> 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: <o:p></o:p> that the appropriate Windows Sockets DLL file is in the current path, <o:p></o:p> 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. <o:p></o:p> the Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly. <o:p></o:p>
10092<o:p></o:p>	WSAVERNOTSUPPORTED<o:p></o:p>	WINSOCK.DLL version out of range. <o:p></o:p> 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. <o:p></o:p>
10093<o:p></o:p>	WSANOTINITIALISED<o:p></o:p>	Successful WSAStartup not yet performed. <o:p></o:p> 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. <o:p></o:p>
10094<o:p></o:p>	WSAEDISCON<o:p></o:p>	Graceful shutdown in progress. <o:p></o:p> Returned by WSARecv and WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.<o:p></o:p>
10109<o:p></o:p>	WSATYPE_NOT_FOUND<o:p></o:p>	Class type not found. <o:p></o:p> The specified class was not found. <o:p></o:p>
11001<o:p></o:p>	WSAHOST_NOT_FOUND<o:p></o:p>	Host not found. <o:p></o:p> 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.<o:p></o:p>
11002<o:p></o:p>	WSATRY_AGAIN<o:p></o:p>	Non-authoritative host not found. <o:p></o:p> This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful. <o:p></o:p>
11003<o:p></o:p>	WSANO_RECOVERY<o:p></o:p>	This is a non-recoverable error. <o:p></o:p> 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.<o:p></o:p>
11004<o:p></o:p>	WSANO_DATA<o:p></o:p>	Valid name, no data record of requested type. <o:p></o:p> 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. <o:p></o:p>

<o:p> </o:p>