ypbind[int]: NIS server not responding for domain "string"; still trying

Cause

This means that the NIS client daemon ypbind(1M) cannot communicate with an NIS server for the specified domain. This message appears when a workstation running the NIS naming service has become disconnected from the network, or when NIS servers are down or extremely slow to respond.

Action

If other NIS clients are behaving normally, check the Ethernet cabling on the workstation that is getting this message. On SPARC machines, disconnected network cabling also produces a series of "no carrier" messages. On x86 machines, the above message might be your only indication that network cabling is disconnected.

If many NIS clients on the network are giving this message, go to the NIS server in question and reboot or repair as necessary. To locate the NIS server for a domain, run the ypwhich(1) command. When the server machine comes back in operation, NIS clients give an "NIS server for domain OK" message.

See Also

For more information about ypbind(1M), see the section on administering secure NFS in the NFS Administration Guide.