Solaris NIS client...

[dave t]

I'm not sure what you mean by granting root access. As soon as all of my 
servers are authenticated to the master server I'm able to see the encrypted 
passwords when i perform a 'niscat passwd.org_dir'. From what I understand, 
this is how it usually works. Even after building a new nis+ server; adding 
a server/user credential; and performing a keylogin -r on the client, I can 
always see encrypted passwords as root on a niscat passwd.org_org.

This has always been the case for me but then again I'm quite new to nis+

dave

>From: Darrel Hankerson <hankedr at dms.auburn.edu>
>To: "dave t" <d_dave at hotmail.com>
>CC: linux-nisplus at lists.samba.org
>Subject: Re: Solaris NIS client...
>Date: 24 Aug 2005 16:42:28 -0500
>
>"dave t" <d_dave at hotmail.com> writes:
>
>    Bascially whats happening is that my linux nis+ client is
>    failing to authenticate w/ the nis+ server. The request is never
>    answered on the nis+ server port. You can determine if you linux
>    authenticates if after you perform a  keylogin -r as root, you should
>    be able to see the encrypted passwords when you do a 'niscat
>    passwd.org_dir'.
>
>There should be compelling reasons to grant root access to the NIS+
>client.
>
>    I've rebuilt a test nis+ server using the tables (groups, passwd,
>    shadow) from the original nis+ server; ran the nisserver command, then
>    nispopluate using tables from the original server; then nisaddcred for
>    the linux client. I pointed the linux nis+ client to the new server
>    and it worked just fine. So I've narrowed it down to a server
>    configuration error, but I'm not sure how to fix it.
>
>Have you granted root access to the encoded passwords to the client?
>The recommendation is to avoid granting such access, but if you
>insist, then the place to start is "niscat -o" and also list the
>contents of the admin group.
>
>--
>--Darrel Hankerson hankedr at auburn.edu