topic Re: delayed logins in Operating System - HP-UX

delayed logins

Paul Romanek — Mon, 06 Aug 2001 20:29:50 GMT

I have L2000 server running hpux 11.0, When I added a nameserver to the resolv.conf I started experiencing delayed logins (up to 1 1/2 minutes) 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 logins

linuxfan — Mon, 06 Aug 2001 20:38:57 GMT

Hi Paul,

Is this machine an NIS client? Are the users defined locally (local /etc/passwd ??) Did you notice this delay after adding nameserver in the resolv.conf ? (Is the nameserver you added to the resolv.conf, a new nameserver?
If this is not the only nameserver, did you try reshuffling (change the order of) the nameservers in the resolv.conf

-Regards
I am RU

Re: delayed logins

Paul Romanek — Mon, 06 Aug 2001 20:49:53 GMT

It is not a nis client, the users are defined localy and the name server is not new, I have not shuffed the order in nsswitch.conf but i have deleted the entry there for nis lookup.

Re: delayed logins

Patrick Wallek — Mon, 06 Aug 2001 21:08:37 GMT

Your problem is probably related to the new name server. Try this:

1) Go into nslookup
2) Set the server to the new name server you added
3) Try looking up your L2000 via both hostname and IP address. You should get a response from both. My guess is you won't get a response, or will get a delayed response from one or the other. This is probably your problem.

You will need to fix this on your name server. Do that and your problems should go away.

Re: delayed logins

linuxfan — Mon, 06 Aug 2001 21:20:47 GMT

Hi Paul,

This may not be directly related to your problem, but identifies some of the problems you may be seeing and explains a little more as to why you may be seeing the problem. In all probability, it is an issue with your new name server.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x1d940559ff7cd4118fef0090279cd0f9,00.html

Here's another link where the user thought they weren't running NIS, but well such is life ;)
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x6cbd6af52b04d5118fef0090279cd0f9,00.html

-HTH
I am Ru

Re: delayed logins

James R. Ferguson — Mon, 06 Aug 2001 21:44:12 GMT

Hi Paul:

This may be a delay due to "reverse name lookup". One way to verify this is to connect via IPAddress vs. via hostname.

Making sure that your device's name is represented in the DNS tables of the DNS server will eliminate the (timeout) delay if reverse name lookup is, in fact, causing the delay.

Another work-around is to declare your clents in /etc/hosts -- even as bogus hostnames.

In either case, it is wise to make sure /etc/nsswitch.conf contains a line that looks like this (in the absence of NIS):

hosts: files [NOTFOUND=CONTINUE] dns

Regards!

...JRF...

Re: delayed logins

Sundar_7 — Wed, 08 Aug 2001 14:56:07 GMT

Hi,

Please see if the nameservers listed

in /etc/resolv.conf are working fine..

Becoz whenever a client is intiating a telnet

connection...the server is going to check

that clients IP address..

So it has to resolv it..

and if the first name server listed in

/etc/resolv.conf is not working or if cannot

resolv the Name-to-ip or ip-to-name then

U will get a delayed login as the first name

server has to time out then only system

will go for next name server..

SO what I will suggest U is that

U check out whether all the servers in

/etc/resolv.conf is working or just

rearrange the order and try

Sundar

Re: delayed logins

Dan Rosen — Wed, 08 Aug 2001 15:27:27 GMT

James is correct, it is a reverse DNS problem. We experience that as well. Two solutions

1.) Quick and Dirty - add the IP address that is having trouble to your /etc/hosts file. All problems go away.

2.) The right way - if there a lot of machines that are at the remote site, then the better answer is to run a local DNS server that will be able to resolve the IP addresses.