FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 09-25-2012, 06:51 AM
Aryan Ameri
 
Default Trouble Mounting NFS Share

Hi all,

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
'vers=4,addr=10.1.1.100,clientaddr=10.1.1.166'
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.

Here is the output for rpcinfo on the server:

sudo rpcinfo -p 10.1.1.100
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 7 111 portmapper
100000 3 7 111 portmapper
100000 2 7 111 portmapper
100003 2 udp 2049 nfs
100005 1 udp 959 mountd
100003 3 udp 2049 nfs
100005 3 udp 959 mountd
100024 1 udp 723 status
100005 1 tcp 959 mountd
100024 1 tcp 1015 status
100005 3 tcp 959 mountd
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 0 udp 989 nlockmgr
100021 0 tcp 775 nlockmgr
100021 1 udp 989 nlockmgr
100021 1 tcp 775 nlockmgr
100021 3 udp 989 nlockmgr
100021 3 tcp 775 nlockmgr
100021 4 udp 989 nlockmgr
100021 4 tcp 775 nlockmgr

As you can see, mountd is running and nfs is available on port 2049
udp and tcp which is what my client tries to use.

I have also disabled the ufw firewall on my Ubuntu 12.04 machine to
make sure that that's not preventing the connection.

If anyone can think of something, that would be great. I have a few
very important documents on this NAS which I need to access tonight so
any help is greatly appreciated.

Cheers

--
Aryan Ameri

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 

Thread Tools




All times are GMT. The time now is 10:42 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org