Telnet very slow ( 3 to 4 minutes )

[s.kalaivanan]

Hi Experts ,

Telnet to 2X HP-UX server ( both rp440 and rx4640 ) is slow for first Login

Problem :- Past 1 month If I telnet to server from my PC or some other it takes slow for first time after that if i open one more session it is normal for some period of time , but if i exit the session and back login after 30 or 40 minutes again it slow

Below workaround i have done :-

1. checked and matched switch side and server side are same settings ( auto negotiate= on , full duplex and 1 gig LAN )
2. checked /etc/nsswitch.conf , resolv.conf are correct
3. From Unix to Unix Box telnet is Normal
4. We didn't upgrade any patches both server side and switch side
5. I have replaced some other Switch port also
6. users PC and server IP subnet is different
7. I and HP Engg found there is no issue with server ( no error in logs )
8.we have other Sun servers are telnet normal same subnet and connected to this same switch
9.Tried with IP instead of Hostname still same

As per the Network team no problem in switch interface , I'm totally mad what could be the problem ?

Pls help me to resolve this issue ,

Thanks in advance ,
Kalai

[Johnson Punniyalingam]

>>6. users PC and server IP subnet is different<<

can you try adding your server name ip address on your PC as below and check ?

C:\windows\system32\drivers\etc\hosts

[Fabio Ettore]

Hi,

I know my answer is generic but every time I faced this kind of problems it almost always was something with name resolution.
This just is a start point, you can take some troubleshooting steps:

- rename /etc/resolv.conf, edit /etc/nsswitch.conf in order to use only /etc/hosts:

hosts: files

Try the connection again, still slow?
- In any cases what about ssh connections, are they also slow?

>>3. From Unix to Unix Box telnet is Normal
It could also be something with routing to HP-UX systems.

HTH.

Best regards,
Fabio
- what about connections

[Steven Schweda · Accepted solution]

Did you do a Forum search for keywords like,
say,
slow telnet
?

A DNS problem is a common reason for this,
but the "hosts" advice you've gotten here
may not help much.

What, exactly, is the slow part?

[Tingli]

ping the primary DNS server and see whether it works. Sometimes because the primary down, it had to time out before going to the second DNS server.

[Tim Nelson]

repeat.. "What, exactly, is the slow part?"

if it is waiting for the "login:" prompt then it is DNS.

If it is characters echoing slowly, then you have server performance issues..

Please specify..

[s.kalaivanan]

Hi Fabio ,

thanks for your inputs

1.Today i have renamed /etc/resolv.conf file and edited /etc/nsswitch.conf file as { hosts: files } in this condition telnet is very normal working fine ,

2. renamed /etc/resolv.conf and edited /etc/nsswitch.conf file as { hosts: files dns nis } --> in this condition telnet is slow

So suggested problem in DNS side ,

Let me know any other issue ?

Thanks & Regards,
Kalai.

[Asif Sharif]

HI Kalia,

Problem is with DNS only. After renaming if it working that means it is relating to DNS.

Regards,
Asif Sharif

[Johnson Punniyalingam]

Forums user name: s.kalaivanan
Company name:
Country / Region: india
Personal quote:
Certification:
ITRC member since: January 28, 2009
Last contribution date: March 09, 2010
I have assigned points to 0 of 23 responses to my questions.

so far you have assigned "0" points since "2009" . please have habit of assiging points for people who help to resolve your issue.

Take a read of this.

http://forums1.itrc.hp.com/service/forums/helptips.do?#33

it explains how to assign points.

[Johnson Punniyalingam]

>>>>So suggested problem in DNS side ,
Let me know any other issue ?<<<

None other issues, You need to fix the DNS problem. other than that, you have also pointed in the /etc/nsswitch.conf ->{ hosts: files dns nis } alternative to resolve hostnames by using /etc/hosts to resolve , in chase of DNS , failure

Possibilities of DNS failure

Example:-

1) pointing inactive / old DNS server names under the /etc/resolve.conf
2)Network problem or Server problem from DNS Server
3) Firewall problems

[Steven Schweda]

> Did you do a Forum search for keywords like,
> say,
> slow telnet
> ?

If you had, then you might know that the
usual DNS problem is not "to resolve
hostnames", it's a failure to do the
_reverse_ look-up, that is, to get the host
name from its IP address.

The Telnet _server_ tries to get the name
associated with the IP address of an incoming
connection, so it tries to do a reverse
(address-to-name) look-up of the client.
This is usually what is slow.

> 9.Tried with IP instead of Hostname still
> same

And it's why no one cares what you do on the
Telnet client system. The server needs to be
able to do that reverse look-up of the
client's address.

[s.kalaivanan]

Hi All already Saw telnet Forums ,

But This problem little confused ,

today , i have kept /etc/resolv.conf file as it is ( means orginal ) , and only changed /etc/nsswitch.conf file as { hosts: files },

Now also telnet working Normal means without renaming /etc/resolv.conf file ,my question now is this DNS issue or some other ? now lookup only from /etc/hosts okay ...

IF DNS issue what could be the problem ? already other SUN servers are working fine with same setup ,

DNS folks not accepting they are telling other servers are working fine , now what answer to tell them ,where we can focus now ?

Thanks & regards,
Kalai.

[Tingli]

It is hard to understand what you are talking about.

[Steven Schweda]

> IF DNS issue what could be the problem ?

> The Telnet _server_ tries to get the name
> associated with the IP address of an incoming
> connection, so it tries to do a reverse
> (address-to-name) look-up of the client.
> This is usually what is slow.

On the Telnet server (HP-UX) system:

nslookup ip_address_of_Telnet_client

If that works well, then I'd expect the
Telnet server to work well. If it's slow (or
fails), then I'd expect the Telnet server to
be slow to connect.

> already other SUN servers are working fine
> with same setup ,

Perhaps the Sun (Solaris?) Telnet server
doesn't care what the client's name is. The
HP-UX Telnet server seems to care.

> DNS folks not accepting they are telling
> other servers are working fine , now what
> answer to tell them [...]?

If that "nslookup" command behaves badly,
then I'd show then the evidence. (If it
works well, then I'd start looking for some
other problem.)

[Steven Schweda]

> If that "nslookup" command behaves badly,
> then I'd show then the evidence. [...]

If that "nslookup" command behaves badly,
then I'd show them the evidence. [...]

"then", "them", ... Sigh.

[s.kalaivanan]

Hi Steven Schweda,

I'm not getting your point ,

again Explain to you

1. If /etc/nsswitch.conf file as {hosts: files dns nis } --> in this conditiion nslookup / Telnet very slow

2. If I after edited /etc/nsswitch.conf file as { hosts: files } ---> In this conditon telnet working fine, means its not using resolution it using /etc/hosts . Telnet / nslookup getting normal bcoz it uses /etc/hosts so whatever entry in /etc/hosts happening normal nslookup

Thanks & Regards,
Kalai.

[Steven Schweda]

> I'm not getting your point ,

Apparently. Do this:

> On the Telnet server (HP-UX) system:
>
> nslookup ip_address_of_Telnet_client

What happens?

[s.kalaivanan]

Hi Steven Schweda ,

#nslookup --> First time slow ( means same issue like as telnet login )

Pls see my previous question

thanks & Regards,
Kalai.

[Steven Schweda]

> Pls see my previous question

Please see my previous answer.

> DNS folks not accepting they are telling
> other servers are working fine , now what
> answer to tell them ,where we can focus
> now ?

> #nslookup --> First time slow
> ( means same issue like as telnet login )

Ok, you've told me. Now, tell your "DNS
folks". (Then ask them to fix it?)


As usual, showing actual commands with their
actual output can be more helpful than vague
descriptions and interpretations.

[s.kalaivanan]

Thanks Steven Schweda ,

I have already Escalated this to DNS team ,

I will let you know ,

Thanks & Regards,
Kalai.

[Michael Steele_2]

Dude, you need to go back and assign point to every responder, that's 38 total. Check your profile for a count verification.