Telnet server delayed response

[Paul R. Dittrich]

We have a brand-new 5400 running 11.11, fresh out of the box with just enough configuration done to get it up on our network.
After a reboot, the telnet server does not accept connect requests. A telnet to the system gets only as far as:
"Trying....
Connected to xxx.xxx.xxx.xxx
Escape character is ..."

The system console is operating normally and outbound telnet from the console is fine too.

The funny part is if we wait ~15-20 minutes, the telnet server starts responding normally and continues normally until the next reboot.
(I know, I know, don't reboot - ever)

What is going on and how to cure it?

Paul

[Sanjay_6]

Hi,

Check your port configuration on the switch to which this system is connected.

Hope this helps.

Regds

[Paul R. Dittrich]

Sanjay, the system is connected to a Cisco Catalyst 100base-TX port that is configured identically to all the other HP servers.

Can you expand on your answer please.

Paul

[Rita C Workman]

Since you said your set up only with bare minimum...

Telnet sessions can have delayed connection time (usually about 100 seconds) to get a login because even a telnet will do a small amount of resolving for the incoming device IP.
Your ~/nsswitch.conf may say hosts then DNS -
If it can't resolve it from either the /etc/hosts or the named.boot file than after the delay it will return with a login prompt.
One way to correct is to add entries in either your hosts file or named.boot.

Just a thought,
Rita

[someone_4 · Accepted solution]

hi there ..
there are many links on the forum that point that a slow telnet is due to some kind of name look up problem. Check /etc/hosts resolv.conf
nsswitch.conf for any clues at to a dns or name look up issue. Here is one post that talks about this. You can do a search for slow telnet and more will come up.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xcfb6119c3420d411b66300108302854d,00.html

Richard

[Ron Kinner]

I assume he means check that the switch and hp box are both set for 100 FD but I don't see how that could cause your problem. Since it does tell you that it connected it must have gotten through to the telnet server which implies that you have the correct speed tho doesn't say anything about the duplex setting.

The next step is presumably for telnet to call the login routine. Don't know why that would take 15 minutes to set up. I'm beginning to suspect you may have an address duplication or a name/address conflict and at first you go to the wrong address then after it's been up for a while the DNS realizes the correct address and sends you there. Try pinging the ip address when the new server is down (or disconnected from the network) to make sure someone else doesn't have the same IP address. Then do a nslookup on the name and see what you get. Does it change after the server has been up for 15 minutes?

Finally, right after it boots can you get on the server and try to telnet to itself using 127.0.0.1? That should rule out any network problems.

Ron