Network Information Service (NIS) B.11.31.04 Administrator's Guide

6 Troubleshooting NIS
This chapter discusses the following error messages and error conditions that you may
encounter with suggested solutions:
• “The NIS Server does not Respond” (page 59)
• “User Cannot Log In” (page 60)
• “Unknown Host” (page 61)
• “An NIS Client Cannot Bind to a Server” (page 62)
• “NIS Returns Incorrect Information” (page 62)
The NIS Server does not Respond
If the message “NIS Server Not Responding” is displayed, complete the following
steps:
1. Verify that the NIS server is up and is reachable on the network:
# /usr/sbin/ping
If the ping command fails, either the server is down or the network has a problem.
To resolve the server issue, reboot the server, or wait for it to start.
To troubleshoot network issues, see Installing and Administering LAN/9000 Software”
available at http://docs.hp.com.
NOTE: If the NIS client hangs during boot because the client is unable to bind
to an NIS server you may need to temporarily disable NIS client binding by booting
the client in single-user mode and setting the NIS_CLIENT variable equal to 0 in
the /etc/rc.config.d/namesvrs file. When the root cause of the NIS binding
problem is resolved, you can change the NIS_CLIENT variable back to 1.
To boot your NIS client without waiting for the server to come up, set the
NIS_CLIENT variable to 0 in the /etc/rc.config.d/namsvrs file and then
boot your client.
2. Run the ps -ef command on the NIS server to check whether ypserv is running.
If it is not, complete the following steps to start ypserv:
a. In the /etc/rc.config.d/namesvrs file on the NIS master server, ensure
that the following variables are set:
NIS_MASTER_SERVER=1
b. Start the NIS server:
# /sbin/init.d/nis.server start
The NIS Server does not Respond 59