Operation already in progress. An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request WSAAsyncGetXbyY that has already been canceled or completed. Socket operation on nonsocket. An operation was attempted on something that is not a socket. Destination address required. A required address was omitted from an operation on a socket.
Message too long. 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 datagram itself. Protocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested.
Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call. Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. Socket type not supported. The support for the specified socket type does not exist in this address family. Operation not supported. The attempted operation is not supported for the type of object referenced.
Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.
Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. Address family not supported by protocol family. An address incompatible with the requested protocol was used. This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto.
Address already in use. Client applications usually need not call bind at all— connect chooses an unused port automatically. Cannot assign requested address. The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer.
Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system that is, the protocol stack that the Windows Sockets DLL runs over , the network interface, or the local network itself. 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.
Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. Software caused connection abort. An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
Connection reset by peer. An existing connection was forcibly closed by the remote host. 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. 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. Socket is already connected.
A connect request was made on an already-connected socket. 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.
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 have been discontinued. Too many references. Too many references to some kernel object. 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.
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.
Cannot translate name. Cannot translate a name. Name too long. A name component or a name was too long. Host is down. A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. No route to host.
A socket operation was attempted to an unreachable host. Directory not empty. Cannot remove a directory that is not empty. Too many processes. A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached. User quota exceeded. Ran out of user quota. Disk quota exceeded. General discussion.
I am try to ping the another ip adrss but error message come out is ' unable to initialize window socket interface errorcode 0. Share Flag. All Comments. Collapse -. Hope this helps :- 0 Votes. The question was auto-closed by TechRepublic 0 Votes.
This question was auto closed due to inactivity 0 Votes. Back to Desktop Forum. Start or search. The following link has some tools Continued is still there. Click "Have Disk However i again it said it could not locate the domain or a domain controller. Member Login Remember to create new shell entries for those two keys. Register ipmontr.
Want to reply to this thread or ask your own question? Run "winmsd" and confirm the deletion, click Yes.
0コメント