NFS connection to NAS failed with protocol error

Budgie2 · May 11, 2023, 4:25pm

I am trying to make an NFS connection to a NAS using yast network services. I believe I have all the permissions enabled and have checked that NFSv4 is also enabled but I am getting an error:

command '/bin/mount -t nfs '192.168.169.131:/New_X3400_Home_Backup'
'/home/alastair/NFS_Link_to_NAS_131'' failed:

stderr:
mount.nfs: Protocol not supported

exit code:
32

Where am I going wrong here please?

malcolmlewis · May 11, 2023, 4:48pm

@Budgie2 Hi, don’t think you need the -t option… Have a read here: https://doc.opensuse.org/documentation/leap/reference/html/book-reference/cha-nfs.html#sec-nfs-configuring-nfs-clients

Budgie2 · May 11, 2023, 5:16pm

Hi Malcolm,
I didn’t put the -t in, it came from the yast installation.
I have been through the system at each end and forced NFSv3 at both ends and this last attempt I didn’t get any error but I still do not have a connection even with firewall disabled.

Here is my /etc/fstab:-

alastair@HP-Z640-1:/etc> cat fstab
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /                       btrfs  defaults                      0  0
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /var                    btrfs  subvol=/@/var                 0  0
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /usr/local              btrfs  subvol=/@/usr/local           0  0
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /tmp                    btrfs  subvol=/@/tmp                 0  0
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /root                   btrfs  subvol=/@/root                0  0
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /opt                    btrfs  subvol=/@/opt                 0  0
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /home                   btrfs  subvol=/@/home                0  0
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=6426a5c3-e7d1-4c54-9c71-45055b9b672d  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=1CE1-6E9C                             /boot/efi               vfat   utf8                          0  2
UUID=b1696969-7ce5-4ed5-b762-fc5df3e35373  swap                    swap   defaults                      0  0
UUID=99e823f1-e3aa-406a-88bc-e37897318ec2  /srv                    xfs    defaults                      0  0
UUID=7bd21373-3218-423e-9d84-86d738ef259d  /test                   xfs    noauto                        0  0
192.168.169.131:/New_X3400_Home_Backup     /home/alastair/NFS_Link_to_NAS_131  nfs    nfsvers=3                     0  0

But I cannot see anything mounted:-

alastair@HP-Z640-1:/> mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=4096k,nr_inodes=1048576,mode=755,inode64)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=13170568k,nr_inodes=819200,mode=755,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,nodev,noexec,relatime,misc)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
/dev/nvme0n1p4 on / type btrfs (rw,relatime,ssd,space_cache,subvolid=256,subvol=/@)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=33824)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p4 on /boot/grub2/i386-pc type btrfs (rw,relatime,ssd,space_cache,subvolid=265,subvol=/@/boot/grub2/i386-pc)
/dev/nvme0n1p4 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,space_cache,subvolid=264,subvol=/@/boot/grub2/x86_64-efi)
/dev/nvme0n1p4 on /home type btrfs (rw,relatime,ssd,space_cache,subvolid=263,subvol=/@/home)
/dev/nvme0n1p4 on /tmp type btrfs (rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/tmp)
/dev/nvme0n1p4 on /root type btrfs (rw,relatime,ssd,space_cache,subvolid=261,subvol=/@/root)
/dev/nvme0n1p4 on /var type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@/var)
/dev/nvme0n1p4 on /usr/local type btrfs (rw,relatime,ssd,space_cache,subvolid=258,subvol=/@/usr/local)
/dev/nvme0n1p4 on /opt type btrfs (rw,relatime,ssd,space_cache,subvolid=262,subvol=/@/opt)
/dev/nvme0n1p2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sdb1 on /srv type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=6585280k,nr_inodes=1646320,mode=700,uid=1000,gid=100,inode64)
appimaged-655-x86_64.AppImage on /tmp/.mount_appimamhB81V type fuse.appimaged-655-x86_64.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
pcloud on /tmp/.mount_pcloudchlzjN type fuse.pcloud (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
KeePassXC-2.7.4-x86_64.AppImage on /tmp/.mount_KeePasPRTF9g type fuse.KeePassXC-2.7.4-x86_64.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
pCloud.fs on /home/alastair/pCloudDrive type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
KeePassXC-2.7.4-x86_64.AppImage on /tmp/.mount_KeePassgGp2E type fuse.KeePassXC-2.7.4-x86_64.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
alastair@HP-Z640-1:/>

Strange because I did not have this problem with a different client on same NAS. Will keep looking but if you have any ideas please let me know.

arvidjaar · May 11, 2023, 5:28pm

Start with running mount with verbose option mount -v ...

dcurtisfra · May 11, 2023, 5:35pm

@Budgie2:

I use the autofs service to NFS mount a NAS box:

In ‘/etc/auto.master’:

/mnt/NAS-001 file:/etc/auto.NAS-001 --timeout=120

In ‘/etc/auto.NAS-001’:

NFS -rw,hard NAS-001.private.domain:/NFS

On the NAS box, the NFS-v2/v3 services and the NFS-v4 service are activated and, there’s a NFS export for the top-level directory ‘/NFS’ – that’s it.

Budgie2 · May 11, 2023, 5:51pm

OK here it is:-

alastair@HP-Z640-1:~> mount -v
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=4096k,nr_inodes=1048576,mode=755,inode64)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=13170568k,nr_inodes=819200,mode=755,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,nodev,noexec,relatime,misc)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
/dev/nvme0n1p4 on / type btrfs (rw,relatime,ssd,space_cache,subvolid=256,subvol=/@)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=33824)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p4 on /boot/grub2/i386-pc type btrfs (rw,relatime,ssd,space_cache,subvolid=265,subvol=/@/boot/grub2/i386-pc)
/dev/nvme0n1p4 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,space_cache,subvolid=264,subvol=/@/boot/grub2/x86_64-efi)
/dev/nvme0n1p4 on /home type btrfs (rw,relatime,ssd,space_cache,subvolid=263,subvol=/@/home)
/dev/nvme0n1p4 on /tmp type btrfs (rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/tmp)
/dev/nvme0n1p4 on /root type btrfs (rw,relatime,ssd,space_cache,subvolid=261,subvol=/@/root)
/dev/nvme0n1p4 on /var type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@/var)
/dev/nvme0n1p4 on /usr/local type btrfs (rw,relatime,ssd,space_cache,subvolid=258,subvol=/@/usr/local)
/dev/nvme0n1p4 on /opt type btrfs (rw,relatime,ssd,space_cache,subvolid=262,subvol=/@/opt)
/dev/nvme0n1p2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sdb1 on /srv type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=6585280k,nr_inodes=1646320,mode=700,uid=1000,gid=100,inode64)
appimaged-655-x86_64.AppImage on /tmp/.mount_appimamhB81V type fuse.appimaged-655-x86_64.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
pcloud on /tmp/.mount_pcloudchlzjN type fuse.pcloud (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
KeePassXC-2.7.4-x86_64.AppImage on /tmp/.mount_KeePasPRTF9g type fuse.KeePassXC-2.7.4-x86_64.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
pCloud.fs on /home/alastair/pCloudDrive type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
KeePassXC-2.7.4-x86_64.AppImage on /tmp/.mount_KeePassgGp2E type fuse.KeePassXC-2.7.4-x86_64.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
alastair@HP-Z640-1:~>

Thanks.
I have also looked at another NFS mount on my system which I do not often use and find it also is not working. This client was served from my office machine so I checked the settings there and the NFS Server on my office machine is working but on this client cannot be seen. Both machines are on the same subnet using static IPs with the same firewall settings. Trouble is I did not notice when this client stopped working. This is probably not relevant here because I can see the NAS system.

arvidjaar · May 11, 2023, 6:39pm

That is not what said. I said to run your mount command with additional verbose option.

Budgie2 · May 11, 2023, 7:18pm

I have never entered a mount command except by using yast so I am not confident I have it right but this is my first attempt with cli:-

alastair@HP-Z640-1:~> sudo mount 192.168.169.131:/New_X3400+Home_Backup /home/alastair/NFS_Link_to_NAS_131/ -v
[sudo] password for root: 
mount.nfs: timeout set for Thu May 11 20:17:41 2023
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.169.131,clientaddr=192.168.169.137'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.1,addr=192.168.169.131,clientaddr=192.168.169.137'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=192.168.169.131,clientaddr=192.168.169.137'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.169.131'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.169.131 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.169.131 prog 100005 vers 3 prot UDP port 30000
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 192.168.169.131:/New_X3400+Home_Backup
alastair@HP-Z640-1:~>

Interesting permission question. Could this be related to not having a local DNS?

arvidjaar · May 12, 2023, 9:22am

The most obvious answer is that server denies access to this client. Check server configuration.

dcurtisfra · May 12, 2023, 9:55am

@Budgie2:

I’m being patient – extremely patient …

An example here with a QNAP NAS with an NFS Server setting which supports NFS V2, V3 and V4:

systemd Journal:

Mai 12 11:39:29 kernel: FS-Cache: Loaded
Mai 12 11:39:29 kernel: FS-Cache: Netfs 'nfs' registered for caching
Mai 12 11:39:29 kernel: Key type dns_resolver registered
Mai 12 11:39:30 kernel: NFS: Registering the id_resolver key type
Mai 12 11:39:30 kernel: Key type id_resolver registered
Mai 12 11:39:30 kernel: Key type id_legacy registered

User CLI command which triggered the Journal entries:

 > cd /mnt/NAS-Bureau-001/NFS/
..NAS-Bureau-001/NFS >

“mount” output for the auto-mounter and the NFS mount:

/etc/auto.NAS-Bureau-001 on /mnt/NAS-Bureau-001 type autofs (rw,relatime,fd=7,pgrp=1788,timeout=120,minproto=5,maxproto=5,indirect,pipe_ino=30180)
NAS-Bureau-001.fritz.box:/NFS on /mnt/NAS-Bureau-001/NFS type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,clientaddr=2001:9e8:34b3:5b00:642:1aff:fe22:7103,local_lock=none,addr=2001:9e8:34b3:5b00:265e:beff:fe02:8d2b)

Shock! Horror! IPv6 addresses in a private IP address space – LAN.

The NFS exports of the NAS box:

 # showmount -e NAS-Bureau-001.fritz.box
Export list for NAS-Bureau-001.fritz.box:
/NFS *.fritz.box
 #

The top-level directory of the NAS box’s NFS export:

..NAS-Bureau-001/NFS> l
insgesamt 32
drwxrwxrwx 5 root     root   4096 11. Okt 2021  ./
drwxr-xr-x 3 root     root      0 12. Mai 11:39 ../
drwxrwx--- 5 bilder01 bilder 4096 11. Okt 2021  bilder01/
drwxrwx--- 4 ???      users  4096  8. Aug 2021  ???/
drwxrwx--- 2 root     root   4096  8. Okt 2021  @Recently-Snapshot/
..NAS-Bureau-001/NFS>

I prefer to make a simple user’s life as simple as possible …

Budgie2 · May 12, 2023, 10:13am

Don,
I saw your earlier post and read up on using auto mount in the link which Malcolm posted earlier. Forgive me for not trying this yet. I appreciate there are many ways to approach this problem but would like to understand what is going wrong with what I had been attempting first. I shall revert to this in due course.

dcurtisfra · May 12, 2023, 10:52am

@Budgie2:

I do admit to being a little bit short and, therefore some tips and tricks for NFS on NAS boxes:

The things are usually (custom) Linux boxes.
And, you can usually setup a SSH session to the user “root” on the NAS box – you may well have to flip some security switches on the box …
I tend to not NFS export the directories used by Windows users – the setup on the NAS box has a user name and password which the access from Windows machines use and, is stored on the Windows clients.
If you look into the NAS box, you’ll see that the UID and GID assigned to the Windows users is usually different to that of the users in the UNIX® / Linux world.
If you have a LDAP service on you LAN then, it may well be much easier to maintain the user’s identifications – assuming that, the NAS box can use LDAP …
I don’t have LDAP currently configured but, may well do that given the NAS access issues …

Manual setup of the NFS directory exported by the NAS box:

Create the directory to be exported via NFS by means of the NAS box’s administration interface – usually a web-browser GUI.
Setup the NFS export by means of the NAS box’s administration – usually a GUI.
Access the NAS box via a SSH connection as “root” to the NAS box.
Set the permissions on the directory exported via NFS to ‘777’ – other:rwx –
Then, “normal” Linux (UNIX®) can access that directory via NFS and, create their own directories on the NAS box with access permissions as they want and/or need.

You can also access the NAS box as the user “root” via SSH and, for each Linux user who shall access the NAS box, create a directory for that Linux user with the appropriate UID and GID values.

I did notice that, my QNAP NAS now has a NFS feature to manage client user’s UID and GID values but, I haven’t yet taken a close look at it …

Budgie2 · May 12, 2023, 10:56am

Hi,
I did of course do this before posting anything here. I had also changed the NAS system from NFSv4 to NFSv2/v3 to keep things simple and on the NAS in the “shared folders permissions” set the specific IP of the client machine but none of this had worked so far.

Don mentioned above in passing his reference to ipv6 which I have enabled on the client in the hope that one day I shall be able to work with ipv6 but all my LAN is ipv4. On the client machine I unchecked the ipv6 box on the network configuration and re-booted and now I have my NFS working with the NAS server.

I have no idea whether my success has been due to the re-boot or my rubbish network configuration but I have half of the problem solved and this thanks to Andrei’s persistence. I note that it was only after I attempted the cli mount that the real problem with permissions was revealed.

The other half is with the NFS connection to my office machine here. I shall keep working and thanks to all.

Budgie2 · May 12, 2023, 1:48pm

First another thank you for the follow up advice re Qnap et al.
Following on from here I do not believe my problem above was anything to do with ipv6 setting but probably due to a missed re-start by gui when a configuration was changed. Another case for using cli I suspect.

I do have a different problem with the second NFS and this time it is because the server system is not even seen by the client. By stopping the firewalls on both machines I was able to create the client setup and have the mount work after starting the firewalls but this did not survive a re-boot.

I may need some help with the firewall configuration here as I have both network interfaces configured in the same way with the same firewall zones, protocols and ports enabled. Am I missing something obvious?

Budgie2 · May 13, 2023, 11:07am

Hi,
My efforts with the second nfs mount were not successful using yast.
I went back to the beginning with command line, went down a couple of rabbit holes withSELinux and AppArmor and didn’t find anything wrong but after reboots all round again I have both connections up and running.
I have not been able to diagnose my initial problem. It is possible I omitted a re-start of a service along the way but more likely I omitted a reboot when one was needed. Possibly a cache issue although using yast I didn’t omit anything.
This last NFS is an important connection so I am now going to embark upon switching to NFSv4, re-enabling IPv6 and building my system back up, but will not waste your time again on this.
Many thanks once more.
Alastair.

dcurtisfra · May 13, 2023, 5:05pm

Um, err – I don’t see this as a “waste of time” –

AFAICS, NFS as such, despite it’s age (or, possibly because of it’s age … ), isn’t so easy to setup and get running.
But, once it’s been setup properly, it’s quite reliable, convenient and, consistent.

So, therefore, please keep us posted on your progress.

dcurtisfra · May 13, 2023, 5:14pm

My personal Firewall view is:

If you’re on a private address LAN @home behind a Router which doesn’t allow any access from the Internet and,
If, your WLAN (also on the private address LAN) is setup to only allow known MAC addresses to use it –
Given that, there’s usually a “Guest WLAN” available on many home/private Routers which, doesn’t allow unknown mobile devices to access the local private address network – only the Internet –

Then, it makes sense to use as little Firewall as possible within that private address LAN space.

If, you have a private address LAN which is a commercial office network then, it’s different – you’ll need a reasonable amount of Firewall within that private address LAN space to guard against visitors and contractors accessing things they shouldn’t really have access to …