How to Check Connectivity on an NFS Client

1. On the client, check that the NFS server is reachable.

   # /usr/sbin/ping bee
   bee is alive

   If the command reports that the server is alive, remotely check the NFS server. For information about remotely checking the NFS server, see How to Check the NFS Server Remotely.

2. If the server is not reachable from the client, ensure that the local name service is running on the client.

   For example:

   • If you are using the NIS name service, verify that the ypbind daemon is running. For more information, see ypbind Not Running on Client in Working With Oracle Solaris 11.4 Directory and Naming Services: DNS and NIS.

   • If you are using the LDAP name service, verify that the ldap_cachemgr daemon is running. For more information, see Monitoring LDAP Client Status in Working With Oracle Solaris 11.4 Directory and Naming Services: LDAP.

3. If the name service is running, ensure that the client has received the correct host information.

   # /usr/bin/getent hosts system

   For example:

   # /usr/bin/getent hosts bee
   192.0.2.0	bee.eng.example.com

4. 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, check whether the NFS service is enabled on the server. For more information, see How to Verify the NFS Service on the Server.

5. If the server is reachable from the second client, use ping to check connectivity of the first client to other systems on the local network.

   If the ping command fails, check the networking software configuration on the client, for example, the/etc/netmasks file and the property information associated with the svc:/system/name-service/switch service.

6. 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. For information about enabling NFS Version 4, see Setting Up the NFS Service.

7. If the software is correct, check the networking hardware.

   Try to move the client to a different physical network connection.