I will let Antoine reclose if he thinks appropriate. WinSock description: No equivalent. Ran out of disk quota. Berkeley description: The protocol family has not been configured into the system or no implementation for it exists. have a peek here
The WSAGetLastError function returns the last error that occurred for the calling thread. It also has a specific meaning for setsockopt(). Resource temporarily unavailable. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database. https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx
Return code/valueDescription WSA_INVALID_HANDLE 6 Specified event object handle is invalid. I puzzled over this again and again. The values for WSANO_DATA and WSANO_ADDRESS (11004) are duplicates, so we don't count one of them. Berkeley description: A file descriptor argument was out of range, referred to no open file, or a read (write) request was made to a file that was only open for writing
A problem was encountered with some part of the filterspec or the provider-specific buffer in general. Connectionless protocols will not throw an exception because they simply establish a default remote host. User suggestions: see WSAHOST_NOT_FOUND for details. Socket Error 10054 Connection Reset By Peer Berkeley description: A message sent on a socket was larger than the internal message buffer or some other network limit.
Berkeley description: Only one usage of each address is normally permitted. Developer suggestions: for protocols and services consider using a hard-coded value for the protocol number or service port number in case your resolution attempt fails, and you can have your cake WSAENETRESET 10052 Network dropped connection on reset. https://social.msdn.microsoft.com/Forums/vstudio/en-US/f29f93a4-fabb-443d-a599-37fb1ee281ac/10035-socket-error-on-connect?forum=vclanguage This won't reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way.
A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the Socket Error 10049 This can help you (or your support staff) to zero-in on what's wrong when your application runs into a problem. Note that this error is returned by the operating system, so the error number may change in future releases of Windows. WinSock description: a quick comparison to the Berkeley counterpart, and a long description of WinSock error.
This error is returned by the WSCGetProviderInfo and WSCGetProviderInfo32 functions if the protocol entry specified could not be found. WinSock description: Similar to Berkeley & Microsoft C, but in reference to sockets rather than file handles (although the descriptions in the v1.1 specification say "no more file descriptors available"). Wsaewouldblock Sap It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed. What Is A Socket Error WHY???
This usually happens when you needed to authenticate to gain access to the local area network in the first place.. navigate here 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. Try a "traceroute" to the host you were connected to. It appears that there is a known issue with Windows sockets where this type of problem may occur with non-blocking sockets. Socket Error 10053
Berkeley description: A bad option or level was specified in a getsockopt()(2) or setsockopt(2) call. You could also try to resolve another hostname you know should work, to check that the name resolution server application is running. You can attempt to avoid the error by calling WSAIsBlocking() before making any WinSock function calls. Check This Out Additional functions: Any functions that takes a pointer as an input parameter: inet_addr(), inet_ntoa(), ioctlsocket(), gethostbyaddr(), gethostbyname(), getservbyname(), getservbyport(), WSAAsyncGetHostByName(), WSAAsyncGetHostByAddr(), WSAAsyncGetProtoByName(), WSAAsyncGetProtoByNumber, WSAAsyncGetServByName(), WSAAsyncGetServByPort(), WSASetBlockingHook() WSAEHOSTDOWN (10064) Host is down.
See also: WSAEINVAL WSAENOTCONN (10057) Socket is not connected. Socket Error Codes Linux WinSock functions: recv(), recvfrom(), send(), sendto(), FD_CLOSE Additional functions: Any function that does I/O on the network could generate this error. User suggestions: Check that you have a name server(s) and/or host table configured.
Look for options to configure your Anti-Virus/Spyware to trust your app. (4) a firewall on the remote server is blocking inbound port 25 (or whatever port the SMTP server is using), See other suggestions under WSAECONNABORTED. WSAEINTR 10004 Interrupted function call. Socket Error 10061 Connection Refused WSAEFAULT 10014 Bad address.
WSAENOTSOCK 10038 Socket operation on nonsocket. The error can also occur in an attempt to rename a file or directory or to remove an existing directory. msg184511 - (view) Author: Kristján Valur Jónsson (kristjan.jonsson) * Date: 2013-03-18 20:05 Here is a patch for 2.7 Since 2.7 doesn't have pytime.c, we export floattime() as _Py_floattime out of time.c http://devstude.net/socket-error/windows-socket-error-value.php You cannot use more than one WinSock implementation simultaneously.
User suggestions: Try to ping the destination host, to see if you get the same results (chances are, you will). The missing functions are getprotobyname(), getprotobynumber(), getservbyname(), and getservbyport(). The WSAEWouldBlock indicates a failure to establish a TCP/IP connection with the remote host at the given port. the socket would block for more than the specified timeout).
WSAECONNREFUSED 10061 Connection refused. WinSock functions: the list of functions that explicitly list this error in the v1.1 Windows Sockets specification. Always be sure to allocate enough space. But most of these function-less errors are simply out of place; they are inappropriate to the Windows Sockets API as it exists in the v1.1 specification.