topic Re: NIS user cannot log in in Operating System - HP-UX

NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 04:13:58 GMT

Hi everybody.

I've just rebuilt a workstation following a power surge. Everything looks fine until a user tries to log in over the network: error message "login incorrect".

I've looked through numerous threads to see if I can find anything similar, but nothing seems to help. Any suggestions appreciated.

Mark Syder (like the drink but spelt different)

Re: NIS user cannot log in

Sivakumar TS — Thu, 19 Jan 2006 04:21:05 GMT

Dear

login as root (local user) and check if the connectivity is OK.

try

#ypwhich

in the client and confirm the NIS servers connectivity.

With Regards,

Siva.

Re: NIS user cannot log in

Devender Khatana — Thu, 19 Jan 2006 04:23:35 GMT

Hi,

Is it the NIS user which is trying to login or you have not yet put it into NIS?

Is /etc/resolv.conf set properly to look for proper entry? and can your workstation see the NIS server?

HTH,
Devender

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 04:23:41 GMT

Thanks Siva.

Output of ypwhich is identical to a working workstation.

Mark

Re: NIS user cannot log in

Peter Godron — Thu, 19 Jan 2006 04:23:47 GMT

Mark,
have you tried:
1. Login with root, then su - to the user
2. check the nsswitch.conf for passwd
3. is this a trusted system?
4. Has the password aged out?

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 04:35:07 GMT

Devender:

Workstation can ping NIS server.

The only difference between resolv.conf on this workstation and a working one was that the newly rebuilt one had a comment against the NIS server. I have removed the comment in case it was causing problems. Does anything need to be restarted?

Mark

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 04:39:17 GMT

Peter:

1. su indicates "Unknown id".
2. nsswitch.conf has files first then NIS. Working WS is the other way round. (I would have thought files first was logical.)
3. No.
4. I reset the password in case he had forgotten it.

Mark

Re: NIS user cannot log in

RAC_1 — Thu, 19 Jan 2006 04:44:01 GMT

Things to check.
1
nsquery passwd "nis_user" "NIS"
Does it resolve it?? If yes that means client can reach nis server and client is interacting with nis server. Again check if ypbind is running or not.
2
ypwhich -m --> Does it list password map??
3
Cross check nsswitch.conf file.
4
Password file. Do you have "+" (allowed nis user) for that user in password file-/etc/passwd

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 04:46:50 GMT

RAC:

"This name service is currently unavailable", yet ypbind is running.

Mark

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 04:59:28 GMT

Possibly another clue:

I've compared several things on the two workstations in SAM. On the "Network Services" screen I see that NFS is disabled on the faulty workstation but enabled on the working one. I've tried to enable it on the faulty ws but after a lengthy delay with an hourglass it returns to disabled.

Mark

Re: NIS user cannot log in

Steve Steel — Thu, 19 Jan 2006 05:01:18 GMT

Hi

What does

nsquery passwd "nis_user"

Give

nsquery hosts hostname

Would also be interesting

Steve Steel

Re: NIS user cannot log in

RAC_1 — Thu, 19 Jan 2006 05:01:56 GMT

nis has nothing to do with NFS. Did you checked all options I asked to check. If yes, post.
nsquery command should be as follows.

nsquery passwd "user_name" "nis"

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 05:04:19 GMT

RAC:

I've amended nsswitch.conf to reflect the working WS then I reran the nsquery. It now shows the user correctly but I still cannot su to his account.

Mark

Re: NIS user cannot log in

RAC_1 — Thu, 19 Jan 2006 05:05:39 GMT

What is the error message?? also answer all previous questions.

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 05:06:52 GMT

Steve:

nsquery hosts hostname gives a correct entry.

Mark

Re: NIS user cannot log in

Steven E. Protter — Thu, 19 Jan 2006 05:07:00 GMT

Shalom Mark,

su can be blocked by pam configuration. We use it to stop root from doing su - to certain dangerous users.

This can also be used to totally prevent user login.

file should be called #pam_user.conf
or
pam_user.conf

You might find its contents interesting.

SEP

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 05:13:18 GMT

RAC:

Apologies - I thought I had answered your questions. Looking back at my response, I only actually answered the first one.

1. This gives a correct answer
2. Yes
3. I have amended it so it is the same as the working workstation (with the exception of passwd - the working one has NIS first, the faulty one has /etc/passwd then NIS which is, in my opinion, more logical)
4. Yes.

SEP:

Thanks. I've checked the file and compared it with the working WS. It's identical.

Mark

Re: NIS user cannot log in

RAC_1 — Thu, 19 Jan 2006 05:19:22 GMT

Post nsswitch.conf
/sbin/init.d/nis.client stop and start

Re: NIS user cannot log in

MarkSyder — Thu, 19 Jan 2006 05:22:36 GMT

RAC - nsswitch.conf as requested:

hosts: dns [NOTFOUND=continue] nis [NOTFOUND=continue] files
automount: nis [NOTFOUND=return UNAVAIL=continue] files
passwd: files [NOTFOUND=return UNAVAIL=continue] nis
group: files [NOTFOUND=continue UNAVAIL=continue] nis
services: nis [NOTFOUND=continue] files

Mark

Re: NIS user cannot log in

RAC_1 — Thu, 19 Jan 2006 05:34:01 GMT

passwd: files [NOTFOUND=return UNAVAIL=continue] nis

this should be
passwd: files [NOTFOUND=continue UNAVAIL=continue] nis

or simply,

passwd: files nis