TELNET LOGIN

[KUMAR_13]

Dear ,
I am facing a problem in Telnet, The server is taking 1 min to display prompt on screen during telnet.
i.e. When i do remote login through telnet command to my server (telnet IPADDRESS), it takes 1 min to display login prompt.
waiting for reply.
Thanking you
Kumar gaurav

[renarios]

Hi Kumar,

First you have to find some causes on your server.
Is your server taking heavy load (top, glance)? Is there a network issue?
Most answers are found in the logfiles. What does your syslog say?

Cheers,

Renarios

[Bill Hassell]

This is a fairly common problem when you have DNS problems. To fix the problem, edit /etc/nsswitch.conf to change the hosts: line. Change it to:

hosts: files [NOTFOUND=continue UNAVAIL=continue] dns [NOTFOUND=return UNAVAIL=continue TRYAGAIN=return]

Now edit your /etc/hosts file and add the IP address of the client that is trying to login. The name isn't important, just add the IP address and a temporary name to the hosts file. This should provide immediate login.

The 1 minute delay is due to a 20 second timeout for each entry in the DNS file /etc/resolv.conf. The DNS servers listed there are no longer reachable or have stopped responding. Or the DNS servers don't know their own name (a security error). Use nslookup to troubleshoot DNS by specifying the DNS server on the command line as in:

nslookup hp.com 12.34.56.78

where 12.34.56.78 is the IP address of your first DNS server. If it does not respond, you'll have to contact your DNS administrator. It may also be due to a routing error. Try:

traceroute 12.34.56.78

where 12.34.56.78 is the IP address for each DNS server.

[Devesh Pant_1]

I have seen this problem when the default route is not set up properly.
Check your /etc/rc.config.d/netconf file

Thanks
Devesh

[Biswajit Tripathy]

I would go with Bill Hassell's suggestions that this might
be related to DNS.

You could run tcpdump on your telnet client and
that might give you a clue to what is going on.

- Biswajit

[Suraj Singh_1]

Hi Kumar,

Just logon to the server, and give this command:

# nslookup `uname -n`

Analyse the response time this command takes and match with the response "telnet" takes.

The problem is surely due to the name resolution. The server is unable to resolve the name. If your server uses a DNS, then have a look at /etc/resolv.conf and resolve the problem, in it. Also look at /etc/nsswitch.conf file and check the sequence the server checks the services (i.e., files, dns, nis etc...)

Regards

[Michael Warren Ogle]

If the DNS is resolving correctly, you might want to look at the windows firewall. Windows firewall can be configured to ignore the authentication packets rather than to reject them. This causes the HP to retry sending the authentication several time before sending the login prompt.

[Devesh Pant_1]

Kumar,
I have successfully emulated your problem where the dns entries are fine and as a result ping response is okay however, due to wrong default route, it takes a while for telnet to respond back ( almost a minute)
Please let me know if this fixed your issue.
thanks
Devesh