If a client is having NFS trouble,
first check that the server is up and running.
From a client, enter:
rpcinfo -p server_name
It should display a list of program, version, protocol, and port numbers similar to:
program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100017 1 tcp 1024 rexd 100005 1 udp 1027 mountd 100003 2 udp 2049 nfs 100024 1 udp 1039 status 100024 1 tcp 1025 status 100021 1 tcp 1026 nlockmgr 100021 1 udp 1051 nlockmgr 100021 2 tcp 1032 nlockmgrThe portmapper, mountd, nfs, and status programs are required, as is nlockmgr if you are using NLM. The rexd program is not required.
This should return:
program 100005 version 1 ready and waitingIf these steps fail, run the rpcinfo -p command on the server's console to verify that the programs listed above are registered.
If the server is functional but a particular client machine cannot reach it, check the network connections between the machines.
If the server and the network are functional, use ps to check the client daemons. Several biod daemons should be running. For example, the command ps -ef should display lines for biod, as well as lockd and statd.