The problem i am having is with changing an NIS password on a few servers. the server sal is the master server. if you are on sal and use the "passwd" command.. it will change your password on the rest of the NIS servers as well.. if you are on sal and use the "yppasswd" command.. u get the following

Error while changing the NIS password.
The NIS password has not been changed on sal

in addition.. what is trying to be achieved is to be able to change the NIS password from a client server.. hal... but.. "passwd" simply looks to local instead of NIS.. and "yppasswd" give the same error as above.

any insight? help please?

If you are going to use yppasswd on the master server then it needs to be a client to itself, so you need to be running ypbind on the master too, so it knows its the NIS server, then yppasswd will work.

You want to be able to change you password from a client using yppasswd so end users are able to change their passwords. Your slave servers probably want to be clients to the master too.

HTH

Jamie...

ypbind is running on both severs.. they are both clients.

when doing ypwhich from sal it returns sal
from hal it returns hal

ypcat ypservers will show both servers.. everything seems to work.. except changing the password

i was having a little fiddle with nis the other day.. don't you need a yppasswd server actually running on the server as well as ypserv? not sure if it was called yppasswd as well or not.... there was ypbind, ypserv, rpc.yprefxdi..ish and another one which was the password daemon no?

yes the yppasswd deamon must be running on the master NIS server.. its /usr/bin/rpc.yppasswdd

it IS running ... yet i still have this problem i cant figure it out.. its got me completely confused

Hi Bubsgt95,

Fellow, I stucked in the same problem. Have you sorted out this issue?
"The NIS password has not been changed on [NIS-MASTER]"

Thanks for any help.
Kind Regards,
Ricardo Olguin

Two years late, but anyway...

Did you check if there's a /etc/sysconfig/yppasswd that needs a bit tweaking?

1 members found this post helpful.