NIS Gooroo Advise Needed!
NIS was working fine until I upgraded from Testing to Unstable. I've
carefully worked my way through the Debian NIS-Howto and the more generic
LDP NIS-Howto (Thorsten Kukuk). I'm using shadowed passwords. The user
/home directories are NFS mounted from the server to the client. Here's
what I'm seeing:
1. On the server:
a. rpcinfo reports as predicted in the Howto (Kukuk).
b. user account logins on the server work.
2. On the client:
a. rpcinfo reports as predicted in the Howto (Kukuk).
b. user accounts on the server can be viewed via:
1) ypcat
2) ypmatch
3) getent
4) getwpnam (program listed in Kukuk Howto)
c. user logins fail "Login incorrect"
d. user group ids listed in /home match gids via NIS.
Pam is "on" for both server and client. I tried turning pam off: User
logins still fail.
I checked to see that data fields match character for character between
what the client sees in "passwd" and "shadow.byname", and what is actually
in the corresponding files on the server. Everything is correctly
propagating from the server to the client.
This leaves me thinking that there is something not "right" with the
client. Local users login just fine, but remote users don't even though
their info seems to be all there via NIS.
Any ideas on where to go from here would be most useful.
Dave
/etc/nsswitch.conf file:
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat
group: compat
shadow: compat
netgroup: nis
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
|
Similar Threads
Linear Mode
