TS client trouble with registration

[56th_Badger]

Hello,
I am using TS for our squadron communications. I have one member who has trouble getting registered. Once regestered he can not connect through anything other than quick connect. Everything is set up ok on the server ( all other members work fine). He has received two error messages repeatedly: Socket error 11001, And, Host not found when connecting through the connect procedure.
We can get him registered just fine. But, When he tries to use the connect option( instead of quick connect) He expereinces these errors.
I am stumped. Any help would be greatly appreciated.
Thankyou.
Oh P.S. He has no internet protection( firewall, ect..) when trying this. And he uses Windows 2000 for a operating system.

[SatanClaus]

can he login as anonymous user via the connection / connect dialogue?

[56th_Badger]

rgr, he cannot join in connection/ connect using anonymous option, He receives the same errors. Badger out.

[56th_Badger]

Hello,
I am using TS for our squadron communications. I have one member who has trouble getting registered. Once regestered he can not connect through anything other than quick connect. Everything is set up ok on the server ( all other members work fine). He has received two error messages repeatedly: Socket error 11001, And, Host not found when connecting through the connect procedure.
We can get him registered just fine. But, When he tries to use the connect option( instead of quick connect) He expereinces these errors.
I am stumped. Any help would be greatly appreciated.
Thankyou.
Oh P.S. He has no internet protection( firewall, ect..) when trying this. And he uses Windows 2000 for a operating system.


Last edited by 56th_Badger on 27-12-2003 at 03:47

[Dummer Sack]

What this basically means is that he typed in the worng name or IP or uses a wrong format. The legal formats are:
IP, IP:PORT, DNSNAME, DNSNAME:PORT.

Error Description:

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.

Developer suggestions: for protocols and services consider using a hard-coded value for the protocol number or service port number in case your resolution attempt fails, and you can have your cake and eat it too.

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. The missing functions are getprotobyname(), getprotobynumber(), getservbyname(), and getservbyport().

See also: WSANO_DATA, WSANO_RECOVERY, WSATRY_AGAIN