Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sparc NIS client authentication problem

Status
Not open for further replies.

inforeqd

Technical User
Jan 8, 2001
95
US
I have a sparc solaris 8 02/04 nis client that is using
my RHEL 3.0 NIS master. Everythings setup however I cannot
get my users to logon via the CDE logon screen. I get
an incorrect logon error. The NIS master is working since I
can logon from linux workstations within the network.
But thats not the end of the weirdness. I have found that
if I logon (locally) to the sparc server and use yppasswd
for the user and then logout that magically I can now
authenticate. Hmmm. So, I did the same thing from a RHEL
nis client and I was back to the sparc box not allowing me
to logon.

It seems to only allow my users to logon when I set the
password (using yppasswd) from the Solaris box. At that
point both my linux and sparc nis clients/users can
authenticate.

Anyone have any ideas or fixes?

TIA
inforeq
 
Linux and Solaris use different encrypted password formats, perhaps that explains what you're seeing?

Annihilannic.
 
annihilannic,

Thats kind of what i've noticed. But it seems that once I modify the password from the solaris box yppasswd <user>, and then verify it ypcat passwd, it certainly looks like a different "hash". But then when I go and change it again from the linux box it still seems to work. So, it seems like its only that I need to configure the password initially from the solaris client, after that it doesnt matter. Wow, this is confusing.
 
annihilannic, you hit the nail on the head, it just took me a little time to figure out that I had md5 enabled on the linux box, therefore the encrypted passwords were md5 and my solaris box didnt recognize them. thanks for mentioning that it helped out in tracking down this dumb error on my part.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top