I have a trusty old FreeNAS box on my home network (running FreeBSD
7.x) which has been working reliably for over 3 years. I've generally
only provided NFS as all machines in the house are *nix which support
NFS (and I've always had problems with Samba).
Yesterday my modem/router stopped working which is also the default
gateway and the DNS provider on my network. From what I know, this
should not pose a problem in me accessing my NAS, as it and the
clients are both on the same LAN and they are connected through a
separate switch (not the failed router). The switch is working just
fine, and I can ping the NAS box and even access its web interface
from my browser, but suddenly I can not mount its NFS share anymore. I
am totally at a loss as to why taking the router out of my network has
resulted in me not being able to mount the NFS share.
FYI, I'll provide some output from commands that I have entered to
solve this problem in case someone more knowledgeable can help with
this. The IP address of the FreeNAS box is 10.1.1.100.
sudo mount -t nfs -v 10.1.1.100:/mnt/nas /mnt/FreeNAS
mount.nfs: timeout set for Mon Sep 24 21:53:53 2012
mount.nfs: trying text-based options
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.1.1.100'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.1.1.100 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.1.1.100 prog 100005 vers 3 prot UDP port 959
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 10.1.1.100 prog 100005 vers 3 prot TCP port 959
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: mount to NFS server '10.1.1.100:/mnt/nas' failed: timed
out, giving up
I have also tried passing the proto=tcp option to mount to force it to
use TCP but that makes no difference.