NIS domain not bound

[Angie_1]

I had a problem with NIS today.
I rebooted the NIS master and the slave is set up of course to take over for the clients.
For some reason the client, even after the master was back up, had the message of "NIS domain not bound."
I even logged into that client and did the ypwhich and saw that for myself.
All I did to resolve was stop and restart nis.client. I shouldn't have to do this. Why is this happening? In the namesvrs file I do have YPBIND_OPTIONS=-ypset. Again all worked fine on the client once I stopped and restarted nis.client. Advice please.

Thx..Angie

[S.K. Chan]

It does takes a while (sometimes up to a minute) for the client to "re-bind" to another server (slave). How long did you wait before you restart nis.client ? Now your slave and client, are they on the same subnet because if they are you shouldn't need "-ypset" option. If they are not on the same subnet, did you have YPSET_ADDR setup in namesvrs to point to the hostname or IP address of the slave ? Did you double check if ypbind process is running on the client and ypserv running on the slave when this happened ?

[Judy Traynor · Accepted solution]

Check the default router on the nis client.
netstat -nr
verify the one used as the default, is indeed the default listed by netstat -nr.

[Angie_1]

THANK YOU!! The default route was completely wrong.

Thx all again for replying.
Angie