Operating System - HP-UX
1748268 Members
3613 Online
108760 Solutions
New Discussion юеВ

Re: NIS is dropping since server move.

 
SOLVED
Go to solution
D. Jackson_1
Honored Contributor

NIS is dropping since server move.

We recently moved 3 servers to a different subnet, the master NIS server is on the old subnet and will be moved in a few weeks. Since the move we have lost NIS connection to the 3 servers several times. Is there a fix for this??


Thanks
5 REPLIES 5
Anthony Goonetilleke
Esteemed Contributor

Re: NIS is dropping since server move.

I presume you have done this

Perform the following steps to bind the client to the server:
1. Insert the following two lines in the appropriate section of the
'/etc/netnfsrc' file:
Note: Insert the lines between what is currently lines 248 and 249.
if [ $NIS_CLIENT -ne 0 -a -f /etc/ypbind ] ; then
/etc/ypbind -ypset && echo "\t/etc/ypbind"
sleep 5 >>add this line
/usr/etc/yp/ypset ip_addr_of_master >>add this line
set_return 2. Re-start NIS: /etc/netnfsrc
Minimum effort maximum output!
D. Jackson_1
Honored Contributor

Re: NIS is dropping since server move.

I don't have an /etc/netnfsrc file???
Patrick Wallek
Honored Contributor

Re: NIS is dropping since server move.

Maybe he means /etc/netrc ? I'm not sure that would work either though.

Try looking in /sbin/init.d/nis.client or /sbin/init.d/nis.server and see if that helps.

I assume you changed the ypservers map to reflect the new subnet that you servers are on? You also changed the IP addresses within the hosts NIS map, and DNS?
Berlene Herren
Honored Contributor
Solution

Re: NIS is dropping since server move.

- Every IP subnet needs an NIS server because NIS clients use IP broadcasts (which are not generally forwarded by IP routers).


If the NIS client and server are on the same IP subnet:

1) The subnet masks for the NIS client and server must be the same. You can verify this with:

/etc/ifconfig lan0

2) Try to ypset NIS client manually to the server with the following command:

/usr/etc/yp/ypset (ip_address_of_NIS_server)
(Use the IP address since the client doesn't have the hostname yet.)

3) Check to see if the client is bound to the NIS server with the following command:

ypwhich

The NIS server name will print if bound.

- If the NIS client and server are on different subnets:

1) You must ypset the NIS client manually to the server with the following command:

/usr/etc/yp/ypset (ip_address_of_NIS_server)

2) Check to see if the client is bound to the NIS server with the following command:

ypwhich

The NIS server name will print if bound.

3) Add a slave to the subnet.

- If you still cannot bind to the NIS server:

1) Verify that the server does serve the domainname expected by the client. On the NIS server, issue the following command:

ls /usr/etc/yp | grep (domain_name)

2) Verify the server keeps the NIS database files in the /usr/etc/yp/(name_of_NIS_domain) directory.

3) Also verify again that ypserv is running on the NIS server with the following command:

ps -ef | grep ypserv




Berlene

http://www.mindspring.com/~bkherren/dobes/index.htm
D. Jackson_1
Honored Contributor

Re: NIS is dropping since server move.

We have done all of these steps, but NIS still drops. It is now happening on servers that have not moved yet. At least one server every day since the first move has dropped off of NIS. We have to keep setting it back. Is there a permanent fix.?.?.

Thanks