not binding to nis server

[Ravi_8]

Hi all
I have L-2000 server which is on DHCP (9.184.196.112) and my nis server is on static ip(9.184.216.131) when i tried to make client to nis server it gives an error"The process /sbin/init.d/nis.client start failed. before you can enable client, it has to be bound to a server" .anybody has solution please respond.

TIA
ravi

[A. Clay Stephenson]

Hi Ravi,

It's not possible from the data that you have supplied to determine if these two hosts are on the same subnet. If not, you will need to do a ypset command on the client to identify the NIS server.

Clay

[Pedro Sousa]

I don't know if you've already tried this, but check if the client is bound to the server you want with "ypwhich -m".
If not, try to set the server with "ypset "

good luck.

[Ravi_8]

Hi, clay
L-1000 server and nis server are on different subnet(hp server is on DHCP nis server is on static ip) when i issued the command #ypset -V1 -h 9.184.196.112 -d domain_name nis_server . it gives me the error"sorry, ypbind on host 9.184.196.112 has rejeted your request"

[Sachin Patel]

Hi Ravi

set your domainname by using
#domainname name_of_your_nisdomain
then run ypset without -h and -d
#ypset -V1 9.184.216.131

Sachin

[SPO Distributed Svcs]

Hi Ravi,

Just noticed your NIS issue, and have a suggestion. Since your L is on a different subnet than the NIS Master, I would suggest that you configure the L as BOTH a Slave Server and a Client. That way, you will not have to worry about binding the client outside of its subnet with "ypset". Configure the Slave on the L class either by editing the /etc/rc.config.d/ files or thru SAM. (SAM will also automatically start the processes). Then, using SAM, on the NIS Master, edit the list of Slave Servers to include the new Slave. Once the edit/update process is complete on the Master server, use the command "/var/yp/yppush ypservers" to repush new copies of all the maps to all the slaves including the newly configured L class.
By doing this, you will eliminate the need to force the client onto a slave outside its subnet, and you will have a more secure NIS environment as ypbind can run without ypsetme

[W Sanders_1]

Ravi's suggestion is a good one if you don't configure too many hosts as slaves. "-ypset" is terribly insecure - "-ypsetme" is better.

I havea similar problem with a 9000 running 11.00 that drops its yp binding everytime there is a glitch in the yp server or the network tat causes it to miss a YP RPC call. Ypbind stays up but is loses its binding and never rebinds.

If this happens again I might write a little daemon that runs every minute and checks that yp is bound, and re-runs ypset if the binding is lost.

I am pretty sure that ypset will allow the lost binding to be recovered without running /sbin/rc2.d/S420nis.client {stop|start}