Note that support for both the UDP and the MOUNT protocols is not necessary if you are using an NFS Version 4 server.
$ rpcinfo -s server-name|egrep 'nfs|mountd'
$ rpcinfo -s bee|egrep 'nfs|mountd' 100003 3,2 tcp,udp,tcp6,upd6 nfs superuser 100005 3,2,1 ticots,ticotsord,tcp,tcp6,ticlts,udp,upd6 mountd superuser
If the daemons have not been started, restart the NFS service. For more information, see How to Restart NFS Service.
$ /usr/bin/rpcinfo -u bee nfs program 100003 Version 2 ready and waiting program 100003 Version 3 ready and waiting
If the server is running, the rpcinfo command lists program and version numbers that are associated with the UDP protocol. You can use the –t option with the rpcinfo command to check the TCP connection. If the rpcinfo command fails, check whether the NFS service is enabled on the server. For more information, see How to Verify the NFS Service on the Server.
$ /usr/bin/rpcinfo -u bee mountd program 100005 Version 1 ready and waiting program 100005 Version 2 ready and waiting program 100005 Version 3 ready and waiting
If the server is running, the rpcinfo command lists program and version numbers that are associated with the UDP protocol. Using the –t option tests the TCP connection. Check whether the nfsd and mountd daemon are running.
$ cd /net/eng
If this command fails, then as the root user on the client, restart the autofs service.
$ svcadm restart system/filesystem/autofs
$ /usr/sbin/showmount -e bee /usr/src eng /export/share/man (everyone)
Check the entry on the server and the local mount entry for errors. Also, check the namespace. In this example, if the first client is not in the eng netgroup, that client cannot mount the /usr/src file system.
Check all entries that include mounting information in all the local files. The list includes the /etc/vfstab file and all the /etc/auto_* files.