Solaris NIS client...
gsmuthu at beceem.com
Fri Aug 26 06:10:47 GMT 2005
Not all the users have passwords more than 8 characters.
From: Peter Bunclark [mailto:psb at ast.cam.ac.uk]
Sent: Friday, August 26, 2005 2:08 AM
To: G.Saravana Muthu
Cc: Darrel Hankerson; dave t; linux-nisplus at lists.samba.org
Subject: RE: Solaris NIS client...
passwords > 8 ?
On Fri, 26 Aug 2005, G.Saravana Muthu wrote:
> I have NIS server running in Redhat (RHEL release 3) and configured
> Solaris 7 as NIS client. From Solaris NIS client, some of the users
> could login to the NIS server but others are not able to login.
> As a root user from Solaris I could do su - to any user and it mounts
> the home directory too. Any idea why some users are not able to login,
> even though everyone has same permissions.
> GS Muthu.
> -----Original Message-----
> From: linux-nisplus-bounces+gsmuthu=beceem.com at lists.samba.org
> [mailto:linux-nisplus-bounces+gsmuthu=beceem.com at lists.samba.org] On
> Behalf Of Darrel Hankerson
> Sent: Thursday, August 25, 2005 3:12 AM
> To: dave t
> Cc: linux-nisplus at lists.samba.org
> Subject: Re: Solaris NIS client...
> "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
> be able to see the encrypted passwords when you do a 'niscat
> There should be compelling reasons to grant root access to the NIS+
> I've rebuilt a test nis+ server using the tables (groups, passwd,
> shadow) from the original nis+ server; ran the nisserver command,
> nispopluate using tables from the original server; then nisaddcred
> 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
More information about the linux-nisplus