On this machine what does the /etc/nsswitch.conf say? Can you attach it to a post.
One the linux machine from the text terminal, login as the user, is there any error messages?
I had trouble with NIS on linux when it was served from a FreeBSD box, specifically because the linux boxes were setup to use shadow passwords and the FreeBSD box was not exporting a shadow map in addition to the regular passwd map. Another problem I ran into with this is that your linux machine will not look for the shadow map at all unless there is an 'x' in the passwd map, anything else will make the client assume that the character is the hashed passwd.
Things you may need to do on your client depending on the OS and whatnot:
- edit the nsswitch.conf so that the client looks to nis first for passwd, hosts, automount, shadow, etc
- Move your /etc/auto.* files to /etc/auto.*.old so that they do now override your NIS files ( can also be accomplished with nsswitch.conf )
- I had to add +:::::: to /etc/passwd and +::: to /etc/group for a few older slackware boxes I have kept around for testing, you may have to do the same
- Make sure that the client machine can nfs mount the directory with the options found in the nis auto.master
- Make sure that the user is in the nis passwd file, ie ypcat passwd|grep user
- do the same for the shadow map
- Make sure the user can change their password, the error can give you clues as to whats wrong.
Here are some more problems I had when I had to set this up:
- I forgot to add the client machine into the netgroup that was allowed to mount the nfs drive
- Automount would not mount over a directory that had anything in it
- The rsize, wsize had to be increased, this was just for performance though
- I had to change from soft mounts to hard mounts after reading the NFS faq
I hope that helps,
Dave
Clothes make the man, Naked people have little to no effect on society
