How do I enable Synology NFS access and fix a mount or permission failure?

QUICK ANSWER

NFS needs both a matching client access rule and suitable file permissions. A working DSM username/password does not automatically make a Linux NFS mount use the same identity.

Applies to: DSM shared folders accessed by authorised NFS clients. NFS version, identity mapping and client configuration must match the environment.

Work through these checks

  1. Confirm the client and service. Identify the client address and required NFS version. On the NAS, review Control Panel > File Services > NFS and enable only the service/version required by the supported setup.
  2. Create a narrow export rule. In Control Panel > Shared Folder, select the share and open its NFS permissions. Match the intended client host or approved subnet and the required read-only or read/write access.
  3. Use the displayed export path. Copy the mount/export path from the NAS configuration and check its case and volume/share spelling on the client. Do not substitute a Windows SMB path.
  4. Review identity mapping. Compare the client's UID/GID and the NAS file ownership/permissions. Examine the selected squash/mapping rule; a mounted directory can still deny file access when identities do not match.
  5. Check the network path. Review permitted client/server traffic and the relevant network segment. A successful ping alone does not prove that the NFS service and export are reachable.
  6. Test with limited data. Mount through the authorised client configuration and test a harmless file according to the intended permissions. Confirm that unapproved clients are not granted access.
Retained reference illustration for How do I enable Synology NFS access and fix a mount or permission failure?
Legacy DSM File Services illustration from the original guide. Current NFS controls may be arranged differently. Select the image to enlarge.

Confirm the result

The correct client mounts the intended export and can perform only its authorised operations, with expected ownership and identity mapping.

Before going further: Do not use a wildcard client rule, map every user to administrator or recursively broaden all file permissions as a general fix.

If you need help

Include these details in your ticket: DSM/model, client OS/address category, NFS version, export rule, mount error and relevant UID/GID/mapping details without private data.

Related guidance: File Sharing: How to set up user's privilege for shared folders on Synology NAS?

Updated 261110

Please Wait!

Please wait... it will take a second!