homepark
asked on
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!
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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 :-)
Be lucky, M$'s NT must be rebooted always ever :-)
ASKER
We are on the right track. YP appears to cache the old info for some x time. However, this is a new behavior.
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
/usr/etc/rpc.yppasswdd (with the appropriate parameters).
I think without that daemon, NIS will not be notified about password changes.
Peter
ASKER
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
Have your client enabled NIS in /etc/{passwd,group}?
I think it must be
+::0:0:::
in passwd
and
+:
in group