Use the information below to fix errors in the configuration of the NIS+ name service that prevent the client from accessing a server during boot.
Problem
No name service is configured for the client in the dhcptab table.
Verification: Log in to the server and type the command:
dhtadm -P | grep ip_address |
Check for entries such as NISdmain, DNSdmain, and NISservs. Make sure the addresses entered for them are correct. For example:
# dhtadm -P | grep 129.148.3.129.148.3.m:Subnet=255.255.255.0:Router=129.148.3.11: Broadcast=129.148.3.255:NISdmain="island.ocean":NISservs=129.148.3.3: |
The line above actually appears on one line, instead of being broken into two.
Solution: Use dhtadm to change any incorrect addresses.
Problem
You are using NIS+ and the server is not running in NIS+ compatibility mode. NIS+ tables do not have read rights for the Nobody category, so NIS clients cannot access the information stored there.
Verification: Run the command:
nisls -l org_dir |
Check whether the Y option is set for the rpc.nisd daemon. For example:
ps -deaf | grep nis |
Solution:
Problem
An incorrect default router prevents the client from reaching a server on another network.
Verification: Make sure the router symbol definition in the dhcptab table is actually a router.
Solution: Use dhtadm to correct the route symbol in the table.
Problem
You are running NIS+ but DNS forwarding is not turned on for NIS clients.
Verification: Use the command:
ps -ef | grep rpc.nisd |
A -B option means that NIS is running with DNS forwarding turned on. For example:
/usr/sbin/rpc.nisd -B |
Solution: Start the NIS+ server in NIS compatibility mode with DNS forwarding enabled. For example:
/usr/sbin/rpc.nisd -YB |