NFS-client discovers share, but mount fails.

The server is running Leap 42.3. I have the NFS share configured.


$ cat /etc/exports
/mnt/nasstorage 201.7.5.0/24(rw,no_root_squash,no_subtree_check)

$ showmount -e       
Export list for nas:
/mnt/nasstorage *

The yast2 nfs-client set-up on my laptop (Leap 42.3) can find the server and the shared directory, but the mount fails:


sudo mount -v -t nfs datahub:/mnt/nasstorage /mnt/nasstorage/
mount.nfs: timeout set for Tue Feb 13 14:20:16 2018
mount.nfs: trying text-based options 'vers=4,addr=201.7.5.250,clientaddr=201.7.5.122'
mount.nfs: mount(2): Connection timed out
mount.nfs: Connection timed out

When I try with option vers=3

sudo mount -v -t nfs -o vers=3 datahub:/mnt/nasstorage /mnt/nasstorage/  
[sudo] password for root:  
mount.nfs: timeout set for Tue Feb 13 14:44:21 2018
mount.nfs: trying text-based options 'vers=3,addr=201.7.5.250'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported

I’ve tried to mount with the firewall on both sides turned off, but that did not have the expected results.

Do you have the rpcbind service running? (Assuming NFS ver 3)

sudo systemctl status rpcbind

Just in case the following is helpful to you for review…
https://www.unixmen.com/setup-nfs-server-on-opensuse-42-1/

What does the following report?

/sbin/rpcinfo -p 201.7.5.250

Given that, the NFS client is a Laptop – mobile – not always near the NFS server – I recommend that auto-mount NFS be used: <https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.autofs.html#sec.autofs.nfs>.

Thanks for the replies.

This issue can be closed.

I had more issues on the server and did a complete fresh install. I re-created the NFS shares and have successfully mounted these in my client.