TCP/IP scenario: A connection will timeout if the local system doesn't receive an (ACK)nowledgement for data sent. I always use standard windows sockets which are based on the Berkeley style sockets and routines... WSAEREMOTE 是一个由系统定义的错误码，对应错误发生时，使用函数 GetLastError 将返回该值。也可在程序中主动调用函数 SetLastError 来设置该错误码，以模拟系统错误的发生。该错误码与 Windows 套接字相关。与 Windows 套接字相关的错误码（WinSock Error codes）的范围为 10000~11999。 平台：Windows头文件：
On a datastream socket, some applications use this error with a non-blocking socket calling connect() to detect when a connection attempt has completed, although this is not recommended since some WinSocks please be so kind and go into detail I have no idea what causes the problem. If you are using a name server(s), check whether the server host(s) are up (e.g. The software caused a connection abort because there is no space on the socket's queue and the socket cannot receive further connections.
- For example, the error can occur when an attempt is made to read from a file that is not open, to open an existing read-only file for writing, or to open
- A retry at some time later may be successful.
- This will verify that the destination network is functioning.
- Since Windows Sockets is practically a clone of Berkeley Sockets, and the rule of thumb is "when in doubt, defer to Berkeley", we can adopt the Berkeley Software Distribution error text
- Occasionally the error code could have more variables in Wsaeremote formatting .This further number and letter code are the location of the storage regions in which the instructions are stored at
- A socket already has a type (a protocol), and each sockaddr structure has an address family field to define its format.
- There are 2 methods in which to resolve Wsaeremote error code: Advanced Solution (advanced): 1) Start your computer and then log on as an administrator. 2) Click on the Get started
- WSAEBADF (10009) Bad file descriptor.
- WinSock functions: the list of functions that explicitly list this error in the v1.1 Windows Sockets specification.
- The Windows Sockets errors are listed in alphabetical order below (they're cross-referenced in a list in numerical order further below).
User suggestions: Try to ping the destination host, to see if you get the same results (chances are, you will). There are numerous events which can have resulted in file errors. The ICMP message means that a router can't forward the IP datagram, possibly because it didn't get a response to the ARP request (which might mean the destination host is down). Developer suggestions: Assume bind() will fail with this error.
WinSock functions: With a datastream socket: connect() and FD_CONNECT WSAAsyncelect() notification message. Microsoft C description: Bad file number. TCP/IP scenario: description of the TCP/IP protocol suite network traffic (i.e. WinSock description: Same as Berkeley.
WinSock functions: gethostbyaddr(), gethostbyname(), WSAAsyncGetHostByAddr(), WSAAsyncGetHostByName(), WSAAsyncGetProtoByName(), WSAAsyncGetProtoByNumber(), WSAAsyncGetServByName(), WSAAsyncGetServByPort() Additional functions: It is strange that the asynchronous protocol and services functions can fail with this error, but the synchronous cannot. WinSock description: No equivalent in WinSock. closesocket(): occurs on a non-blocking socket with non-zero timeout set with setsockopt() SO_LINGER. Operating System Compatibility:Windows XP/Vista/7 / 8 (32/64BIT) Download Size: 8 MB Version 2014 Expert Support: Yes System Error Codes (0-499) System Error Codes (500-999) System Error Codes (1000-1299) System Error
Berkeley description: A socket operation encountered a dead network. WinSock functions: socket() See also: WSAESOCKTNOSUPPORT WSAEPROTOTYPE (10041) Protocol wrong type for socket. WinSock description: No equivalent. Do you have a router configured?
WinSock functions: accept(), bind(), connect(), gethostname(), getpeername(), getsockname(), getsockopt(), recvfrom(), send(), sendto(), setsockopt() if buffer length is too small. The values for WSANO_DATA and WSANO_ADDRESS (11004) are duplicates, so we don't count one of them. This usually results from trying to connect to a service that is inactive on the foreign host. WinSock functions: accept(), bind(), closesocket(), connect(), gethostbyaddr(), gethostbyname(), gethostname(), getpeername(), getprotobyname(), getprotobynumber(), getservbyname(), getservbyport(), getsockname(), getsockopt(), ioctlsocket(), listen(), recv(), recvfrom(), select(), send(), sendto(), setsockopt(), shutdown(), socket(), WSAAsyncGetHostByAddr(), WSAAsyncGetHostByName(), WSAAsyncGetProtoByName(), WSAAsyncGetProtoByNumber(), WSAAsyncGetServByName(),
you tried to connect to the wrong destination host address the server application isn't running on the destination host the server application isn't listening on the right port. User suggestions: There are a number of things to check, that might help to identify why the failure occurred. WinSock description: No equivalent. The Wsaeremote error message is the Hexadecimal data format of the error message generated.
User suggestions: see WSAHOST_NOT_FOUND for details. WinSock description: Same as Berkeley TCP/IP scenario: In TCP terms (datastream sockets), it means an attempt to connect (by sending a TCP SYN packet) caused the destination host to respond to The Windows Sockets API provides access to "low-level" API's (like the transport protocols TCP and UDP), so this error is not relevant to WinSock.
Every error description contains at least: Summary Info: Error macro: manifest constant, as defined in WINSOCK.H Error value: as defined in v1.1 WINSOCK.H Short description Berkeley description: text describing the equivalent
after failed calls to inet_addr() or gethostbyname()), then simply test your address value for zero before you pass it to sendto(). The WinSock API does not provide access to the Network File System application protocol, so this error is irrelevant to WinSock. In Berkeley, this error also occurs when you are trying to name the local socket (assign local address and port number) with bind(), but Windows Sockets doesn't ascribe this error to It's not unusual to see an increase of 95%+ in performance.
In WinSock it means a blocking operation was interrupted by a call to WSACancelBlockingCall. Regards Robert Robert Rostek -=[[email protected]]=- Reply With Quote November 22nd, 2001,03:11 PM #4 Andreas Masur View Profile View Forum Posts Visit Homepage Member Power Poster Join Date May 2000 Location KY, Apparently, the Windows Sockets specification left this out by oversight. WinSock functions: recv(), recvfrom(), send(), sendto() WSAENAMETOOLONG (10063) File name too long.
Additional functions: a generic description of the type of functions that can return this error, which may include functions other than those listed by the WinSock specification. 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.