NFS connection timed out

English Network/Internet
1

Alright, so I have an NFS server set up on OpenSUSE Tumbleweed (linux-g0p3, 192.168.10.62). When trying to mount the nfs export on the client (debian wheezy, alise, 192.168.10.70), it looks like this:

francis@alise:~$ sudo mount -v -t nfs 192.168.10.62:/home/francis/Downloads /mnt
mount.nfs: timeout set for Sun Sep 15 14:05:39 2013
mount.nfs: trying text-based options 'vers=4,addr=192.168.10.62,clientaddr=192.168.10.70'
mount.nfs: mount(2): Connection timed out
mount.nfs: Connection timed out

Some info. On the server I have the following /etc/exports

/home/francis/Downloads         192.168.10.*(fsid=0,crossmnt,ro,no_root_squash,sync,no_subtree_check,insecure)

Running showmount -e localhost

Export list for localhost:
/home/francis/Downloads 192.168.10.*

Running rpcinfo -p:


  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
    100005    1   udp  52406  mountd
    100005    1   tcp  33545  mountd
    100005    2   udp  47682  mountd
    100005    2   tcp  50326  mountd
    100005    3   udp  48056  mountd
    100005    3   tcp  34734  mountd
    100024    1   udp  43103  status
    100024    1   tcp  54034  status
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049  nfs_acl
    100227    3   tcp   2049  nfs_acl
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049  nfs_acl
    100227    3   udp   2049  nfs_acl
    100021    1   udp  57965  nlockmgr
    100021    3   udp  57965  nlockmgr
    100021    4   udp  57965  nlockmgr
    100021    1   tcp  45237  nlockmgr
    100021    3   tcp  45237  nlockmgr
    100021    4   tcp  45237  nlockmgr

Any help ?

2

Ok, sorry for double posting, but I figured some stuff out. In YaST NFS Server, I unchecked NFSv4. Now I get:

mount.nfs: timeout set for Sun Sep 15 15:22:53 2013
mount.nfs: trying text-based options 'vers=4,addr=192.168.10.62,clientaddr=192.168.10.70'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.10.62'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.10.62 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.10.62 prog 100005 vers 3 prot UDP port 59019

So it works on NFSv3. This does raise some questions:

Do I need or want NFSv4? This is rather simple setup where I want to access music on my pc from a living room media server. If I do, how do I get it working?

Why does it work over UDP but not TCP?

3

Disregard the above post.

I’m sorry for spamming, but I figured it out. What made it work was not disabling nfsv4, but rather enabling “Open ports in firewall”. Bleh, I didn’t even know I had a firewall running. Works now with nfsv4 and all.

4

On 2013-09-15 21:26, auxym wrote:
>
> Ok, sorry for double posting, but I figured some stuff out. In YaST NFS
> Server, I unchecked NFSv4. Now I get:
>
>
> Code:
> --------------------
> mount.nfs: timeout set for Sun Sep 15 15:22:53 2013
> mount.nfs: trying text-based options ‘vers=4,addr=192.168.10.62,clientaddr=192.168.10.70’
> mount.nfs: mount(2): Protocol not supported
> mount.nfs: trying text-based options ‘addr=192.168.10.62’
> mount.nfs: prog 100003, trying vers=3, prot=6
> mount.nfs: trying 192.168.10.62 prog 100003 vers 3 prot TCP port 2049
> mount.nfs: prog 100005, trying vers=3, prot=17
> mount.nfs: trying 192.168.10.62 prog 100005 vers 3 prot UDP port 59019
>
> --------------------

Notice that it fails on TCP and then tries UDP, which apparently works.
NFS v4 only allows TCP, so it fails.

> Why does it work over UDP but not TCP?

Ah, you noticed. Well, many reasons possible. The first one to look at
is the firewall. Try without firewall on both machines first.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

5

On 2013-09-15 21:56, auxym wrote:
>
> Disregard the above post.
>
> I’m sorry for spamming, but I figured it out. What made it work was not
> disabling nfsv4, but rather enabling “Open ports in firewall”. Bleh, I
> didn’t even know I had a firewall running. Works now with nfsv4 and all.

Are you interested in configuring the firewall?

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)