Home > Socket Error > Winsock Returned Error Code 10048

Winsock Returned Error Code 10048

Contents

This is one of the most frequent errors and one of the best to encounter, since it's one of the least ambiguous. WSA_QOS_POLICY_FAILURE 11011 QoS policy failure. Generically, the error means the network system has run out of socket handles. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM. Source

WSAEPROCLIM 10067 Too many processes. WSAESOCKTNOSUPPORT 10044 Socket type not supported. WSA_OPERATION_ABORTED 995 Overlapped operation aborted. WSAEHOSTUNREACH 10065 No route to host.

Socket Error 10054

This error apparently also takes the place of WSAEPFNOSUPPORT (which means "protocol family not supported"), since that error is not listed for socket() in the v1.1 WinSock specification. WSAHOST_NOT_FOUND 11001 Host not found. An invalid policy object was found in the QoS provider-specific buffer.

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 It is a non-fatal error, and the operation should be retried later. but it gives 10038 error at sendto() Hot Network Questions `patch:instead` removes an element with no attributes Sum other numbers A firm farewell - Rest in piece Client requesting admin work Socket Error 11004 Berkeley description: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket) no address was supplied.

Thirteen errors have "" next to the list of WinSock functions that can produce them. Socket Error Codes Linux Normally, this indicates that the TCP/IP protocol is unavailable, or the desired port number for the socket is already in-use. Alternately, you could call getprotobyname() or WSAAsyncGetProtoByName() to get the appropriate protocol value from the network system. In most cases, the default Winsock that comes with your OS is appropriate.

An application used a Windows Sockets function which directly maps to a Windows function. Winsock Error 10054 Fix WinSock description: Same as Berkeley. WinSock functions: the list of functions that explicitly list this error in the v1.1 Windows Sockets specification. Copyright © 1996-2016 Alt-N Technologies.

Socket Error Codes Linux

all other functions: retry the operation again later since it cannot be satisfied at this time. WSAEUSERS 10068 User quota exceeded. Socket Error 10054 WSAENETDOWN (10050) Network is down A socket operation encountered a dead network. Socket Error 10053 An example is using a broadcast address for "sendto" without broadcast permission being set using setsockopt(SO_BROADCAST).WSAEADDRINUSE (10048)Address already in use.Only one usage of each socket address (protocol/IP address/port) is normally permitted.

If it doesn't respond, it might be off-line or there may be a network problem along the way. this contact form You cannot use more than one WinSock implementation simultaneously. a "high-level" protocol). WSAETIMEDOUT 10060 Connection timed out. Socket Error 10054 Connection Reset By Peer

Berkeley description: The protocol has not been configured into the system, or no implementation for it exists. 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(), Some WinSock implementation use these errors inappropriately, but they have a particular meaning. have a peek here If so, is there an older DLL in a directory in the path ahead of the directory containing the newer DLL?

WSA_QOS_ESHAPERATEOBJ 11030 Invalid QoS shaping rate object. Winsock Error 10061 Can you ping that hostname? in the v1.1 WinSock specification.

WSAEPFNOSUPPORT 10046 Protocol family not supported.

A socket operation failed because the destination host is down. This error occurs when the sin_port value is zero in a sockaddr_in structure for connect() or sendto(). Users should check: That the appropriate Windows Sockets DLL file is in the current path. Socket Error 10061 Connection Refused Additional functions: With a datagram socket: send() or sendto(), or FD_READ.

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(), User suggestions: There are a number of things to check, that might help to identify why the failure occurred. How to use sort on an awk print command? Check This Out 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.

TCP/IP scenario: Calling shutdown() with how=1 or how=2 sends a TCP FIN packet to the remote address, which literally means "I'm done sending." If the local host sent any more data Ping the remote host you were connected to. Berkeley description: An attempt was made to access an open file (on an NFS filesystem) which is now unavailable as referenced by the file descriptor. However, they don't need to set the WinSock error value, because there's only one reason for their failure: the input parameter was invalid.

Specifically, these error-less functions are the byte order functions ( htonl(), htons(), ntohl(), and ntohs()), the address manipulation functions (inet_addr(), and inet_ntoa), WSAGetLastError() and WSAIsBlocking(). WSA_QOS_RESERVED_PETYPE 11031 Reserved policy QoS element type. Any of the Winsock name resolution functions can fail with this error. WinSock functions: socket() See also: WSAEPROTOTYPE, WSAEPROTONOSUPPORT WSAESTALE (10070) Stale NFS file handle.

It also occurs with functions that take a socket handle and a sockaddr structure as input parameters. A ring in which the two operations are equal is {0} Given that ice is less dense than water, why doesn't it sit completely atop water (rather than slightly submerged)? A socket operation was attempted to an unreachable network. On the server end, you could use a network system utility similar to BSD's "netstat -a" command to check that your server is running, and listening on the right port number.

WinSock description: Almost same as Berkeley. However, some WinSocks fail with WSAEINVAL you call connect() a second time (or subsequent) on a non-blocking socket. If a Winsock implementation has an upper limit to the number of simultaneous tasks it can handle, an application's initial call to WSAStartup could fail with this error.WSAEUSERS (10068) Too many By calling shutdown() you do a partial close of a socket, which means you have discontinued sending.

The name is not an official host name or alias, or it cannot be found in the database(s) being queried. There are no QoS senders. before calling connect() or accept()). An asynchronous signal (such as SIGINT or SIGQUIT) was caught by the process during the execution of an interruptible function.

WinSock description: a quick comparison to the Berkeley counterpart, and a long description of WinSock error.

Follow us