[FIX] mount.nfs: access denied by server while mounting synology nas drive

Question

I have the same issue where my fstab from Ubuntu 16 worked, and under 18.04 does not. I found through experimentation that if I changed the permissions on the share from using *.fully_qualified_domain.us to 172.16.10.0/24 then I would be able to mount my volumes.

I opened an issue with Synology. Synology believes that dnsmasq daemon is ignoring the fully qualified name in the mount process.

From my fstab where “hostname.fullyqualified.us” is my fully qualified hostname.

hostname.fullyqualified.us:/volume1/music /media/coolwave/Music nfs ro,user,async,nolock,nfsvers=3 0 3
hostname.fullyqualified.us:/volume1/photo /media/coolwave/Photo nfs ro,user,async,nolock,nfsvers=3 0 3
hostname.fullyqualified.us:/volume1/homes/jcfowler /mnt/home nfs rw,user,async,nolock,nfsvers=3 0 2
hostname.fullyqualified.us:/volume1/Family /mnt/Family nfs rw,user,async,nolock,nfsvers=3 0 3
hostname.fullyqualified.us:/volume1/homes/pi /mnt/pi nfs rw,user,async,nolock,nfsvers=3 0 2

Click Here to see answer

in progress 0
payam 7 months 2022-03-08T05:31:50+00:00 1 Answer 48 views

Answer ( 1 )

  1. 2022-03-08T15:04:55+00:00

    I have the same issue where my fstab from Ubuntu 16 worked, and under 18.04 does not. I found through experimentation that if I changed the permissions on the share from using *.fully_qualified_domain.us to 172.16.10.0/24 then I would be able to mount my volumes.

    I opened an issue with Synology. Synology believes that dnsmasq daemon is ignoring the fully qualified name in the mount process.

    From my fstab where “hostname.fullyqualified.us” is my fully qualified hostname.

Leave an answer

By answering, you agree to the Terms of Service and Privacy Policy.