Problem
When I attempt to log in to a particular system via rlogin or
telnet, there is a 75 second or longer delay before a prompt appears.
The prompt is "login:" in the case of telnet, and "Password:" for
rlogin. Cause
The following should be considered regarding this issue:
a) Physical network problem with NiC, cabling, hub/switch or router
b) Default route issues (See 'netstat -rn')
c) Performance on the server itself (See 'sar)
d) Domain Name Services (DNS) issues, see below:There may be a Domain Name Service (DNS) configuration problem on the system to which connection attempts are being made (called the "server" for the rest of this article), resulting in a failure to resolve the hostname (i.e. perform a reverse name lookup) of the system initiating the connection (called the "client").
The exact amount of the delay varies according to local configuration.
The following two cases show possible causes for the reverse lookup failure, but it is likely that other causes exist as well:
- The nameserver entry in /etc/resolv.conf points to a non-existent IP number.
- The nameserver IP number is valid, although the corresponding host is temporarily down.
To confirm a reverse lookup problem, run the following command after logging in to the server (where xxx.xxx.xxx.xxx is the IP number of the client system):
# nslookup xxx.xxx.xxx.xxxIf the problem exists, the following message will appear after a delay. Normally, nslookup will return immediately with the hostname of the client. yyy.yyy.yyy.yyy is the IP number for the nameserver that the server system is attempting to use:
*** Can't find server name for address yyy.yyy.yyy.yyy No response from server *** Default servers are not available
If the server is running OpenServer, a reverse lookup problem can also be confirmed once logged in by running the command who -mx and checking whether an IP number or hostname is shown.
For example, where test.sco.com is the fully qualified domain name for the client, the correct output would look like this:
root ttyp1 May 14 18:55 test.sco.comHowever, if the DNS problem were present, the output would look like this (where xxx.xxx.xxx.xxx is the IP number for the client system):
root ttyp1 May 14 18:55 xxx.xxx.xxx.xxxThe equivalent command for UnixWare is:last -n 1 `tty | sed s-/dev/--`The correct output for this command is:
root _tcp/626 test.sco.com Fri May 18 09:17 still logged inWith the DNS problem present, the output will look like this:
root pts008 xxx.xxx.xxx.xxx Fri May 18 09:39 still logged in Solution
Remove any invalid nameserver entries from /etc/resolv.conf on the server system and ensure that all hosts corresponding to valid nameserver entries are booted and can be reached from this system.
See also
ta112741: "UnixWare 7, It takes a long time to connect to my server using the DNS name."
ta112062: "30 second delay before Password: prompt appears when logging in to SCO OpenServer."
resolver(SFF)