topic Re: delayed login on a L2000 in Operating System - Linux

delayed login on a L2000

Paul Romanek — Mon, 06 Aug 2001 20:27:13 GMT

I have L2000 server running hpux 11.0, When I added a nameserver to the resolv.conf I started experiencing delayed logins on my server from our remote sites. This happens intermittently, mostly on the first login. We are using kermit95 to telnet to the server but i do not think it is the problem. I have also edited nsswitch.conf and removed the nis lookup but still no go. I could use any idea's you may have to help resolve this problem.

Thanks,

Paul Romanek

Re: delayed login on a L2000

John Love_3 — Mon, 06 Aug 2001 21:10:22 GMT

Paul,
The problem is Host lookup. When you telnet to the machine, it tries to resolve your host name. It first tries files, then DNS and NIS if you have it setup that way in the nsswitch.conf file.
You can do 2 things.
1. remove DNS from the "hosts" line in the nsswitch.conf file. The problem with this is that if you're using it for e-mail and other internet stuff, it won't work properly, because it will not use DNS to lookup hostnames.
example:
hosts: files [NOTFOUND=return]# dns nisplus nis
This will check the /etc/hosts file and then quit trying to resolve the hostname. It works.

2. Edit the /etc/hosts file to include all the machines that need to connect to this server.
This may not be entirely practical, but it could be the easiest. Depending on how many workstations are going to connect and if you are using DHCP.

Hope this helps.

John

Re: delayed login on a L2000

Angus Crome — Tue, 07 Aug 2001 18:43:34 GMT

You might also try running a traceroute to the IP address of one of those workstations and also to the DNS name. See if the times or route paths differ. If they do, then your DNS server is either slow to respond or is causing a different route path to be followed.

Re: delayed login on a L2000

Sridhar Bhaskarla — Thu, 16 Aug 2001 21:09:18 GMT

1. Try reverse lookup on the remote servers to see if there is any delay.
2. On the server try both nslookup and lookups on the remote servers
2. Check your name server to see if itself is able to resolve the remote systems.

A pure DNS problem.

-Sri