NIS on SunOS 4.1.3

When creating a new account, after running make on /var/yp on NIS server, the new id appears in passwd, group, aliases maps. When you try to login as new user, or su, you get "unknown login". When changing existing users passwords, ypasswd indicats NIS change on correct server. However, only the old password works. Another ypserver on the sub-net had been disabled a few weeks ago (friendly but renegade). Ypwhich on the clients and NIS server yields correct server name. HELP!
homeparkAsked:
Who is Participating?
 
ahoffmannConnect With a Mentor Commented:
My experiences with the roots of NIS (SunOS 4.x) are a few years ago. But I remeber that there was also a file /etc/publickey (to be modified with newkey, chkey, etc.); if this file is used, it must also be propagated by yp. I'm not shure about what file will be changed by yppasswd: passwd and/or publickey.
0
 
ahoffmannCommented:
Does your NIS server use the files (passwd, group, aliases) from /etc, or does it have it private ones in /var/yp?
Have your client enabled NIS in /etc/{passwd,group}?
I think it must be
+::0:0:::
in passwd
and
+:
in group


0
 
homeparkAuthor Commented:
In answer to your questions:
Map files are in /var/yp/domainname on NIS server. Clients have NIS enabled as you indicated with no entries duplicated on maps. Clients running ypbind. Ypcat of passwd, aliases, and group, from clients show new account key and values.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
df020797Commented:
yp dont update in "real time" You have to wait a bit... even if you run a make in /var/yp. FOr instant update simply kill the ypserv daemon and restart it.

0
 
ahoffmannCommented:
df, I remember that my SunOS 4.0.x manual also suggest to kill and restart ypbind and/or ypserv if somthing goes wrong.

Be lucky, M$'s NT must be rebooted always ever :-)
0
 
homeparkAuthor Commented:
We are on the right track. YP appears to cache the old info for some x time. However, this is a new behavior.
0
 
pxhCommented:
Does your server run the yppasswd daemon, i.e.
/usr/etc/rpc.yppasswdd  (with the appropriate parameters).

I think without that daemon, NIS will not be notified about password changes.

Peter

0
 
homeparkAuthor Commented:
Yes, yppasswdd is running. I did find that by stopping and restarting the ypserver did move things along. Had to do it twice, once to setup the account, and a second time to add the password. However, this behavior of 'cache-ing" the old info is relatively new. Hence the mystery
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.