NAS Codex › QNAP › QNAP NFS mount fails: access denied, permission denied or protocol not supported

QNAP NFS mount fails: access denied, permission denied or protocol not supported

When a Linux or UNIX client cannot mount a QNAP shared folder over NFS, or mounts it but cannot open anything, QNAP's FAQs trace it to a short list of settings: the NFS service, the NFS host access rule on each shared folder, the squash option that maps client users, and the path used for NFS v4. QNAP also notes that QTS 5 changed how NFS permissions work.

Written against: QTS NFS service and shared folder NFS host access (QNAP FAQs last modified 2022-06-24 and 2022-08-11). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.

Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.

Fast Answer

In Control Panel > Privilege > Shared Folders, open the folder's Edit Shared Folder Permission, switch to NFS host access and check that Access right is enabled and the client's IP address or network is listed. QNAP says NFS access right is disabled by default.

1. Turn on the NFS service

Go to Control Panel > Network & File Services > Win/Mac/NFS, open the NFS Service tab, enable NFS v2/v3 and/or NFS v4, and click Apply.

If the client shows "mount.nfs4: Protocol not supported", QNAP says to tick Enable NFS v4 Service on that tab and click Apply.

2. Allow the client in NFS host access

NFS access is set per shared folder. In Control Panel > Privilege > Shared Folders, click Edit Shared Folder Permission under Action and select NFS host access. QNAP says NFS access right is disabled by default, so enable it, click Add, enter the client and its permission, and click Apply.

QNAP lists the formats the Host / IP / Network field accepts:

QNAP warns that an incorrect format can lead to access errors.

3. Permission denied after upgrading to QTS 5

QNAP says QTS 5 tightened NFS access permissions and separated the shared folder permissions for NFS and Samba. As a result, some shared folders mount in Windows and Linux but cannot be accessed after the upgrade. QNAP's fix:

  1. In NFS host access for the folder, enable Access right and add the client's IP address or domain name with its permissions.
  2. Under Squash Options, select Squash all users, set the Anonymous UID account or Anonymous GID group, and click Apply.
  3. Go to Privilege > Users or User Groups, select that anonymous account or group, open Edit Shared Folder Permission, give it the permissions it needs on the shared folder, and click Apply.

How the squash options map users

QNAP notes that QTS versions older than 4.4.1 had four squash options.

4. "No such file or directory" with NFS v4

QNAP says NFS v3 and v4 use different paths. NFS v3 mounts /share/Public, for example mount -t nfs 10.64.72.30:/share/Public /mnt/public. NFS v4 mounts /Public, for example mount -t nfs4 10.64.72.30:/Public /mnt/public.

When to stop and get help

Before choosing SQUASH_NO_USERS to keep original file owners, note QNAP's warning: remote root users then have root permission to change any file in the shared folder.

Questions

Why do I get permission denied on a QNAP NFS share?

QNAP says NFS access right is disabled by default per shared folder, and QTS 5 separated NFS and Samba permissions. Enable Access right in NFS host access, add the client, and set the squash option and anonymous account permissions.

How do I fix mount.nfs4 Protocol not supported on QNAP?

QNAP says to enable NFS v4 Service under Control Panel > Network & File Services > Win/Mac/NFS > NFS Service and click Apply.

What path do I use to mount a QNAP share with NFS v4?

QNAP's example uses /share/Public for NFS v3 but /Public for NFS v4, such as mount -t nfs4 10.64.72.30:/Public /mnt/public.

Sources

Every fact on this page comes from the vendor documents below, opened on 2026-11-17.