Telnet Conection Slow

[Bruno Vilardo]

Hello All,

I am having a problem with Telnet connection,
It takes up to 5 minutes to prompt the login.
I have checked the traffic and it´s ok, i have checked the inetd and it´s running.TRU64 4.0g
I use TOP and everything is normal in the machine.

Does anyone know what else could i check in order to get this thing fixed?


Thanks a lot B

[Mobeen_1]

Do u think everything is ok on the name resolution aspect?

Do you get normal response time in pinging the host?

Does your nslookup of the host work fine?

rgds
Mobeen

[Mobeen_1]

Bruno,
I suspect that the name resolution could be taking time, since you say that everything looks fine.

Can you edit /etc/hosts file and then make an entry for the host that you are trying to telnet and see if that helps make the telnet fast? If it does work fast after doing this, then i suggest that you talk to your DNS admin

rgds
Mobeen

[Greg Yates]

You might check the route to the target (traceroute) to see if you have a weird (long) route. Do other things look good going to that box (like ftp, ping, etc.)? Once in, does performance seem okay (network-wise)?

Depending on your patch level, you may be experiencing a known issue that's fixed:

"... Depending on which CPU the forking or exitting process is running on, the hang
may cause telnet or ping requests to also hang temporarily."

This was fixed with PK4 and beyond.

Hope this helps.

Greg

[Bruno Vilardo]

Hey Guys,

I telnet from my PC to the Server,
It takes 1 minutes 15 seconds top prompt.
After i login i can work normally.
The problem is only the Telnet connection from the PCS to the Server.
A couple of weeks ago we had changed the DNS IP.
The DNS ip that was set before was the SERVER IP and then we changed to the DNS ip because we had to make sendmail to work.


Maybe that is the problem.
Do think if i changed the DNS ip address at /etc/resolv.conf to the ip that i had before, it will work ?

Thanks
Regards

Bruno

[Bruno Vilardo]

Hey Guys i changed the DNS IP to the SERVER IP i had before and it´s working fine.
But i do need that the resolv.conf points to the DNS IP.
What could i do?



Thanks
Regards

Bru

[Greg Yates]

I'm not 100% sure that I follow you, but I think I see what's going on -- or at least close. :) It sounds like the DNS server's IP address(es) changed. If so, it makes perfect sense that telnet (and ftp, ping and so on) will 'hang' while you timeout trying to resolve the IP address of the target system. You can always verify that this is the problem (this = DNS lookup problems) by telnet'ing to the box using its IP address instead of the name. If that connects immediately, then odds are the timeout is DNS related.

So, if the DNS server(s) have changed, you'll need to update the /etc/resolv.conf file to reflect the new IP addresses for all clients.

Hth.
Greg

[Ralf Puchner]

please use svcsetup to configure how Tru64 will resolve ip/hostnames.

bindsetup is the tool which configures the nameserver on Tru64 side (e.g. client, which dns server etc.)

Be sure the Tru64 system is known within the nameserver (fullqualified/shortname). E.g. activate dns name resolution on PC side (within the network setup) or add an entry in the c:\windows\system32\driver\etc\ files.