Discussion Locked

Telnet Latency

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a small network with several flavors of UNIX (AIX, HP, SCO) and a small NT 4.0 domain. Physical network is ethernet and hubs. A couple of weeks ago we started having problems with telneting to the UNIX hosts. When we try to connect, it takes1 to 2 minutes before we get a login prompt. Once we get the login prompt it works fine from there.

It does not matter which client or which UNIX box we try. It is the same using Windows Hyper -terminal or WRQ Reflections.
It does not matter ifwe use host names or IP addresses. There is no trouble pinging the boxes.
Does anyone have any ideas, or can you point me to some tools or troubleshooting resources for telnet?
Thanks!

5 replies

by achuprinin

It looks like network problem.
(I think you'd checked the load of your UNIX boxes and it normal).
To be sure about it try enter to any box and and call telnet to itself:
telnet localhost
If there will be delay that means that the problem inside UNIX box if there won't be delay then I'm right and there are some problems with network.

by bblock

DNS / hosts file. Your host is trying to resolve the name of the client machine, given its ip address. Whether you're using DNS or just an /etc/hosts file, make sure your host can resolve names and addresses of client machines. I bet you just switched your resolver from a hosts file to DNS when the problem appeared, and your name server doesn't have client entries. That's how it bit me.

by ratherbfishing

Yes, it was a DNS problem. Our DNS server was changed (new IP address and name) and it was not updated in the resolve.conf files. Apparently when you Telent, even using an IP address instead of a name, it attempts to do a reverse look up for the host name. Now it works fine. Although we do not use client entries in DNS.

This discussion is closed to new replies.