Error: "Error 10048: Unable to bind socket to port 67..." when starting the PXE Server
5 stars based on
The errors are sorted in alphabetical order. Some error codes that are defined in Winsock2. They are not included in the list. Returned when bind socket error 10048 system call that should never fail does fail. Can indicate a service provider implementation error.
An attempt was made to access a socket in a way forbidden by its access permissions. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof sockaddr. Some invalid argument was supplied for example, specifying an bind socket error 10048 level to the setsockopt function.
In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening. Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.
This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation bind socket error 10048 be retried later. Operation now in progress. A blocking operation is currently executing.
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 bind socket error 10048 or completed. Socket operation on nonsocket. An operation was attempted on something that is not a socket. A required address bind socket error 10048 omitted from an operation on a socket.
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. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
The requested protocol has not been configured into the system, or no implementation for it exists. Socket type not supported. The support for bind socket error 10048 specified socket type does not exist in this address family. 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 bind socket error 10048 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. 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 overthe network interface, or the local network itself.
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, bind socket error 10048 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 bind socket error 10048 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.
A connection attempt failed bind socket error 10048 the connected party did bind socket error 10048 properly respond after a period of time, or the bind socket error 10048 connection failed because the connected host has failed to respond. 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. 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. 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. Network subsystem is unavailable. 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.
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 bind socket error 10048 in the path is appropriate for the network subsystem currently loaded.
The Windows Sockets implementation documentation to be bind socket error 10048 all necessary components are currently installed and configured correctly. Bind socket error 10048 current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application.
Successful WSAStartup not yet performed. The application may be accessing a socket that the current active task does not own that is, trying to share a socket between tasksor WSACleanup has been called too many times. Graceful shutdown in progress. Class type not found. The specified class was not found. No such host is known. The name is not an official host name 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 that the specified name could bind socket error 10048 be found in the relevant database.
Nonauthoritative host not found. This is usually a temporary error during host name 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. This is a nonrecoverable error. This indicates that some sort of nonrecoverable error occurred during a database lookup.
Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable. Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid.
One or more parameters are invalid. An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters.