% /usr/sbin/ping bee bee is alive
If the command reports that the server is alive, remotely check the NFS server. See How to Check the NFS Server Remotely.
If the server is not reachable from the client, ensure that the local name service is running.
For NIS+ clients, type the following:
% /usr/lib/nis/nisping -u Last updates for directory eng.acme.com. : Master server is eng-master.acme.com. Last update occurred at Mon Jun 5 11:16:10 1995 Replica server is eng1-replica-58.acme.com. Last Update seen was Mon Jun 5 11:16:10 1995
If the name service is running, ensure that the client has received the correct host information by typing the following:
% /usr/bin/getent hosts bee 18.104.22.168 bee.eng.acme.com
If the host information is correct, but the server is not reachable from the client, run the ping command from another client.
If the command run from a second client fails, see How to Verify the NFS Service on the Server.
If the server is reachable from the second client, use ping to check connectivity of the first client to other systems on the local net.
If this command fails, check the networking software configuration on the client, for example, /etc/netmasks and /etc/nsswitch.conf.
(Optional) Check the output of the rpcinfo command.
If the rpcinfo command does not display program 100003 version 4 ready and waiting, then NFS version 4 is not enabled on the server. See Table 5–3 for information about enabling NFS version 4.
If the software is correct, check the networking hardware.
Try to move the client onto a second net drop.