Re: NFS trouble
On Mon, Feb 27, 2012 at 9:29 AM, Raffaele Morelli
> 2012/2/27 Tom H <firstname.lastname@example.org>
>> On Mon, Feb 27, 2012 at 5:45 AM, Raffaele Morelli
>> <email@example.com> wrote:
>> > I am setting up (tryin at least) a nfs mount on a remote machine,
>> > there's a
>> > firewall in between so I asked the net administrator to open ports 111
>> > and
>> > 2049 on the server.
>> > /etc/exports on the server is
>> > /home/username/ CLIENT_IP(ro,sync)
>> > mount command is
>> > mount -v -t nfs REMOTE_IP:/home/username/ /local/mount/point
>> > I got this error:
>> > mount.nfs: timeout set for Mon Feb 27 11:28:00 2012
>> > mount.nfs: trying text-based options 'vers=4,addr=REMOTE_IP,
>> > clientaddr=CLIENT_IP'
>> > mount.nfs: mount(2): No such file or directory
>> > mount.nfs: trying text-based options 'addr=remote_ip_addr'
>> > mount.nfs: prog 100003, trying vers=3, prot=6
>> > mount.nfs: trying REMOTE_IP prog 100003 vers 3 prot TCP port 2049
>> > mount.nfs: prog 100005, trying vers=3, prot=17
>> > mount.nfs: trying REMOTE_IP prog 100005 vers 3 prot UDP port 34449
>> > mount.nfs: portmap query retrying: RPC: Timed out
>> > mount.nfs: prog 100005, trying vers=3, prot=6
>> > mount.nfs: trying REMOTE_IP prog 100005 vers 3 prot TCP port 58566
>> > showmount -e REMOTE_IP fails with
>> > rpc mount export: RPC: Timed out
>> > - server is running debian squeeze with nfs-kernel-server from wheezy
>> > - client is running debian wheezy
>> > any idea?
>> (untested on wheezy but ok on squeeze)
>> You have to use static ports for statd, mountd, and lockd if you're
>> not using nfsv4. (You don't have to use the same static assignments
>> used below.)
>> - Set
>> STATDOPTS="--port 4003 --outgoing-port 4004"
>> in "/etc/default/nfs-common"
>> - Set
>> RPCMOUNTDOPTS="-p 4002"
>> in "/etc/default/nfs-kernel-server"
>> - Set
>> options lockd nlm_udpport=4001 nlm_tcpport=4001
>> in "/etc/modprobe.d/lockd.conf"
>> - Open the relevant ports with iptables
> Ok, so I guess I should ask my net admin to open all relevant ports for
> mountd, nlockmgr and status as showed in `rpcinfo -p` OR whatever port I
> would like to use for STATDOPTS, RPCMOUNTDOPTS and lockd.
> Is it right?
Yes, but you have to fix the port numbers by editing the files above
because they'll be variable otherwise.