low response when try to login server.

[leereg_6]

Gurus,

When I try to login another server in my office, it took about 30 seconds or more. Several servers showed this low speed response. Does this caused by network speed or system itself, need I reboot servers after a certain time?

Thanks in advance!

[Christian Gebhardt]

Hi

We need more information to solve your problem:
- Are the server busy ? (check it with command "top"
- What LAN do you have ? (10MBit to GBit)
- There is no need to reboot servers if applications are written well, what applications are the server running ?

Chris

[John Palmer]

Hi,

This normally means that your DNS server is not responding. Check /etc/resolv.conf.

Regards,
John

[Bill McNAMARA_1]

I'd check the syslog too.
Check lanadmin stats for protocol errors.
nettladm offers a gui to check and trace lan problems..

Another suspect would be NFS mounted homes...

test if it happens for root or just for normal users.

Later,
Bill

[Leif Halvarsson_2 · Accepted solution]

Hi
This seems to be some kind of name resolution problem (NIS or DNS).
When I had some problems with our NIS server I get exact this behaviour.

[Rita C Workman]

I used to be able to pull up on doc on this (but alas they have removed it...).

What the others have stated is what the document mentioned.

When you try to telnet/login the receiving server will try to resolve who is making the connection first....so it will try resolv. It uses the ~nsswitch.conf file for the order of how to proceed. So it may first go to your hostfile, if it can't resolve the ip your coming from, then it goes to next method, DNS and so forth. It will after about 100 seconds give you the login prompt.

You can speed up the connection by either adding the IP entries to your hostfile or you can resolve it using entries in DNS named.boot...

Just a thought,
Rita

[Bill Hassell]

As mentioned, long delays in getting a login are caused by authentication of your incoming IP address with a valid hostname. The rules are:

- No /etc/resolv.conf, then the IP must be listed in /etc/hosts

- /etc/resolv.conf can contain 1 to 3 IP addresses for DNS servers. More than 3 are silently ignored. If /etc/nsswitch.conf does NOT exist, then /etc/hosts is sliently ignored.

- /etc/nsswitch.conf (see man switch) controls the order and action for resolving names. If DNS is first, then the server must respond or timeout (timeout = apx. 30 secs).

If the first server responds but does not know the IP address, then nsswitch.conf controls the next action. If the first server is dead (does not respond), it takes 30 seconds to try the second and 30 more to try the third (ie, about 100 seconds).

So the issue is not with the network, it is with validation by your DNS server. If you do not have a stable and secure DNS server, don't use it for production work. Use /etc/hosts and remove /etc/resolv.conf so you'll hacve dependable logins.

[leereg_6]

Thanks for all your reply.
My network is 10 Base and from the output of the top command, it appears that there is some problem with my NFS.
How to check it and get rid of the problem?


Thanks a lot!



2.3 04:18:31 0.2 5960 0 20 Oct_11 root 261 /usr/lib/autofs/automd
0.6 02:36:36 0.0 0 60 SY Oct_11 root 3 fsflush
0.3 11:53 0.1 3208 58 20 Oct_11 root 144 /usr/lib/picl/picld
0.1 11:17 0.3 12640 49 20 Oct_11 root 491 /opt/Vete/deg/bie
0.0 5:24 0.2 6632 59 20 Oct_14 some 220 Xvnc

[leereg_6]

When I try to login that server(It serves as a homedir server and configured as a NFS server), it took me more than 20 seconds to wait the passwd requirement prompt after provide my username(normal user). And it took me more that 10 seconds to wait until it get ready after provide my passwd.

Did it caused by NFS or something else, if so, how to prove the root cause and shoot the trouble?


Thanks a lot!

[leereg_6]

The problem is still there.
I hope to get help from all of you. I will give points to those who give me help at any level.


Thanks!

[leereg_6]

When I try to telnet or rlogin to the target IP address, there was no problem. But the problem repeated when I try with it's hostname, did it caused by NIS or DNS, how to resolve it?

[Sanjeev Kohli_1]

Rick ,

Can u check ur Network card if it has any problems , U can check this by lanadmin command .
It will give u a menu where u have to select
LAN - PPA (0 or 1 depending on which car u have configured) - Display
From this u will come to know whether ur card is having any collisions or errors .
As ur card is 10Mbs it might be on half duplex mode , if it is then u change it to FUll duplex if your card & the switch supports .

Check the /etc/nsswitch.conf file , change the sequence of checking the server from DNS and NIS first to FILES then DNS and then NIS .

Sanjeev

[John Bolene]

I would also point to DNS as the problem.

When DNS works, it is a blessing, when it does not, it is a curse.

Normal DNS timeouts are set at 40 seconds.

Sounds like DNS cannot resolve your terminal IP or name.