Well, The actual Winsock error is error 11004. This is determined by converting the last four numbers of the Hexidecimal error to decimal (that's what this part means: where the actual API error value is the error code masked with 0xFFFF.)
So basically you convert the Hex 2afc to decimal and that is 11004.
The actual Winsock error description for that is:
WSANO_DATA (11004) Valid name, no data record of requested type
Berkeley description: The requested name is valid, but does not have an Internet IP address at the name server. This is not a temporary error. This means another type of request to the name server will result in an answer.
WinSock description: Same as Berkeley for host resolution. For protocol and services resolution, the name or number was not found in the respective database.
User suggestions: see WSAHOST_NOT_FOUND for details.
WSAHOST_NOT_FOUND - error 11001 gives more details:
WSAHOST_NOT_FOUND (11001) Host not found
Berkeley description: No such host is known. The name you have used is not an official hostname or alias. This is not a soft error, another type of name server request may be successful.
WinSock description: Same as Berkeley. Any of the WinSock name resolution functions can fail with this error. The WinSock API does not provide any way to select specific name resolution protocols, server address, or record type.
TCP/IP scenario: Most WinSock implementations use domain name system (DNS) protocol for hostname to address resolution, although a few use Network Information System (NIS). Assuming you have a name server configured instead of or as well as a host table, a hostname resolution request causes a WinSock DLL to send a DNS "A" record query (address query) to the configured DNS query. If you have more than one server configured, the hostname query fails only after the WinSock DLL has queried all servers.
User suggestions: Check that you have a name server(s) and/or host table configured. If you are using a name server(s), check whether the server host(s) are up (e.g. try to ping the server(s)). You could also try to resolve another hostname you know should work, to check that the name resolution server application is running.
If you are using a host table exclusively, you'll need to update it to add the destination hostname and address.
Essentially, what this is saying is that it can't find the server that you're trying to find may be unavailable or is not configured properly. Double check your configuration instructions for setting this up and make sure you have everything configured to the instructions. In essence the problem is that it is not resolving the server name that you are looking for. It may be something as simple as an error in your setup configuration or may be something more complicated. Check your configuration first and we'll go from there.
"There's no place like 127.0.0.1 except for ::1."
Alexandria Networks. Leader in IT consulting for associations/non-profits, and small to medium sized businesses around the northern Virginia and Washington D.C. metro area.