On Fri, 2005-09-16 at 13:40 -0700, Brian D. McGrew wrote: > >From a command line do a 'ping <server_name> and see if that's > successful. I just dealt with this early today where I was getting a > server down. The server was up, DNS has the correct info and so did NIS > hosts but my _local_ hosts file had the wrong IP and therefore it was > unreachable. > > If you get a response from the server ping, login to the server, do a > 'ps -aux | grep nfs' and make sure that NFS is really running. Also, at > a command line on the server you can do an 'exportfs' and it will show > you what filesystems are exporting. > > If all that looks good, try putting > > /u01 *(sync) > > In your /etc/exports file and restart NFS just to see if it's an > security issue hanging you up. You can also try '/usr/sbin/rpcinfo -p <server>' on the client machine to see what RPC services (if any) can be reached. You should see nfs, nlockmgr, and mountd show up. If you run it against the client hostname, you should see at least nlockmgr. -- prothonotar at tarnation dot dyndns dot org
