login prompt comes very later when doing telnet

[senthil_3]

Hi,

the problem is when i do the telnet to HP ux the telnet session gets connected and to bring the login prompt it takes much time. there is no effect after loging on..

[steven Burgess_2 · Accepted solution]

Senthil

Looks as though the box is having trouble resolving the host you are logging on from, or is set up to resolve to dns first

When you log onto the server , check your /etc/resolv.conf file

The quickest resolution method is to resolve internally first via the host file, then if the server name is not found consult dns

The servers resolv file should look something like this

hosts: files [NOTFOUND=continue] dns

HTH

Steve

[Steven Sim Kok Leong]

Hi,

Check the name resolution on your destination server.

1) Check /etc/resolv.conf

Verify that the nameservers IP addresses you specify in /etc/resolv.conf is correct e.g.:

nameserver 1.2.3.4
nameserver 5.6.7.8

2) Check /etc/nsswitch.conf

Check that hostnames are resolved in the correct name order:

hosts: files [NOTFOUND=continue] dns

3) Perform a nslookup test from the server end:

# nslookup telnet_client_IP

Hope this helps. Regards.

Steven Sim Kok Leong

[V. V. Ravi Kumar_1]

hi,

check
nestat -a
and
netstat -an
output.
if netstat -an is taking long time then it is the problem with the name resolution. check any dns entries. then also check any nis daemon like ypbind is running. just kill it if ur server is not an nis server.

regds

[steven Burgess_2]

Senthil

Whoops. Sorry your /etc/nsswitch should look like

hosts: files [NOTFOUND=continue] dns

Wrong file

Steven, thanks for the reminder

Steve

[Ramesh Donti]

Hi Senthil,
Say...you are telnetting from a PC to the server then
when you tried connecting through telnet, the server gets the IP address of the client and then the server does reverse nslookup using DNS servers in /etc/resolv.conf entries.

You may find that, if your PC is in your DNS and can be reverse nslooked-up then you will get telnet prompt very much immediately.
To quickly check, whether you have problem with your DNS resolution or not, try using
netstat -a & arp -a.
If it takes very long time to return back the prompt, then you have problem with your DNS resolution.
Try switching DNS servers in /etc/resolv.conf