NIS accross subnets

[Scott McDade]

Hello:

I have several 11i systems that are using NIS which are all on the same 192.16.131.XX subnet. I have a single master and several clients and everyone plays nicely. I am trying to add another machine to the NIS domain and I am having trouble. The major difference is there are no more IPs available in the 192.16.131.XX subnet so I was issued a 192.16.133.XX IP. All of my NFS mounts work across these 2 subnets it is just I can not get the new machine to find the domain that is on the 192.16.131...Are there any NIS restrictions that limit MASTER/CLIENT activity to a single subnet?

I have included the rc.log files that is created when then ypbind fails on boot.

Thanks in advance for your time.

-Scott

[steven Burgess_2 · Accepted solution]

Hi Scott

If the master is in a different subnet then you will need to define that information in the file:

/etc/rc.config.d/namesvrs

modify:

YPBIND_OPTIONS="-ypset"
YPSET_ADDR=ip_address_of_the_master_server

stop / start the nis client:

/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start


HTH

Steve

[steven Burgess_2]

Also

From your rc.log output it looks as though there is an issue with swagentd , have you added the localhostname to the hosts file ? Can you perform an nslookup on your host ?

It's nice to attempt to eliminate all possible issues

Regards

Steve

[Jeff Schussele]

Hi Scott,

I'm not aware of single subnet restrictions to NIS.

But I note in the swconfig section of the rc.log that this system, iltdc6, cannot resolve itself. First thing to do would be to get it entered into it's own /etc/hosts file or ALL the SD utilities will give you trouble.

Next question would be are there any firewall rules or IP-filtering in the router between these systems? Anything blocking the NIS traffic? Specifically port 111 both TCP & UDP.

Another thing to consider is that NIS, by default, uses broadcasts to locate NIS servers. You may need to manually bind the client to the server using ypset OR alter the netmasks for the network so that the clients in ~.133 can find the server in ~.131

IF a manual bind using ypset works then you can try setting in the /etc/rc.config.d/namesvrs file the following:

YPSET_ADDR=xxx.xxx.xxx.xxx (the IP OR hostname of NIS server
YPBIND_OPTION="-ypset"

This will "force" a binding & not rely on broadcasts.

HTH,
Jeff