yppasswd update not working

I have an NIS server running and the client machine seems to be using it properly.  The client machine can ypcat the host and pasword files of the NIS server with no problems.  However, yppasswd doesn't see to be working properly. I create a user on the new NIS server, copy the contents of /etc/passwd into my /var/yp/etc/passwd file and then run Make. Everything seems to work fine. I then run yppasswd for the user and it seems to work fine and tells me that the NIS information for this user has changed, however it doesn't. the user cannot use it's newly created NIS password on the client machine, it still uses the original password that was copied from /etc/passwd.

Am I missing a step? Let me know if you can help. ypserv, ypbind (master and slave) and rpc.yppasswdd are running on the server.  THanks in advance.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It sounds like pwupdate isn't being triggered from rpc.yppasswdd or it's not running properly. You need to look at the man pages for rpc.yppasswd and pwudate and compare what they do by default with what your system & NIS configuration looks like. If your configuration needs specific (non-default) options to rpc.yppasswdd, you'll want to modify the init script the starts the daemon at boot time.

Although it doesn't sound like it from the way you've phrased the question, if there's a nis slave server(s) involved and the client has bound to it (check by executing ypwhich on the client) it could be a problem with the maps not being pushed out to the slave server(s). If this is the case you'll look at the man pages for yppush to see how to set it up to push the updates out to the slave server(s).

I realize that this answer might sound a bit vague, but this kind of problem is extremely difficult to diagnose remotely. To properly find and solve the problem usually requires direct access to the systems as there are a number of reasons that the password change could fail.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rvaughn012800Author Commented:
thanks, I'll check out the man pages!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.