You mentioned you're using shadow passwd in your reply to Gilbert in
this thread -- what does that look like in each nsswitch.conf ? I'd
expect it to be "files nis" as well, but it's a good thing to check.
Gilbert's other questions about shadow.byname et al NIS maps are also
good to check. You c
The nsswitch, ypwich and ypmatch lines match 1:1, There are only file and
nis for the passwd entry on this list. Compat or nis+ isn¹t there.
Bill
On 8/1/14, 16:02 MDT, "Steve Rikli" wrote:
>If you believe you have the configs straight at this point, as initial
>troubleshooting steps e.g. I w
Yes, they are both using shadow passwords. I am tempted to just let this
hang for two weeks until I get to the NIS machine and then do it from
scratch. If I just follow basic “muscle memory” on this I am a hoping
that if I "dance with you brung you” this may work? Is a SL to SL NIS
implementatio
Do you have shadow passwords? Is there a difference in the way Mandriva
handled those than how SL does? Are you generating a shadow.byname map,
a passwd.adjunct.byname map, or both?
The NIS code has some odd tweaks in it to implement shadow password
support in ways that are backward-compatib
If you believe you have the configs straight at this point, as initial
troubleshooting steps e.g. I would compare the outputs of these commands
on the working and non-working NIS client systems:
grep ^passwd: /etc/nsswitch.conf
ypwhich
ypmatch NISuser passwd
Your logs indicate password f
I am using a login via ssh
Here is the secure log material for my test USR
Aug 1 21:26:20 unix_chkpwd[6558]: password check failed for user
()
Aug 1 21:26:20 sshd[6556]: pam_unix(sshd:auth): authentication
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=
user=jtorres
Aug 1 21:26:22 sshd[
What login method is failing? Login from console? ssh? other?
does /var/log/secure give you anything as far as error messages? It
should. Is kerberos involved here or do you have hashed
passwords in the NIS map?
Steve Timm
On Fri, 1 Aug 2014, Capehart, William J wrote:
Steve:
Normally
Steve:
Normally I do all the pieces normally but I followed your guidance:
authconfig --enablenis ‹nisserver=(server.name.goes.here)
‹nisdomain=(mydomain) --update
As root, id on one of my test accounts worked.
As root, su on the same test account worked.
³nis² has indeed been through the /et
did you go into the system setup utility and enable NIS authentication?
(or use authconfig from the command line). That's the best way
to ensure that PAM is configured correctly to use NIS and that's likely
the problem.
(does "id" on a yp user name work?)
(does "su" to a yp user name work?)
do
We are in the process of migrating to SL 6.5 from Mandriva and things have been
manageable until (of course) today.
The NIS server is still under Mandriva (yp-serve is 2.22, ypbind is 1.29.91)
On the client to be in SL 6.5 the ypbind is 1.20.4.
NIS works on the fellow Mandriva machine clients b
10 matches
Mail list logo
