Skip to main content
NetApp Knowledge Base

Mount operation fails with permission denied due to IP address translation by the NAT service

  1. Last updated
  2. Save as PDF
Views:
4,215
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • NFS
  • Network Address Translation (NAT) service.
  • AIX 5.4

Issue

  • Mount operation fails with "Permission denied" despite correct permission settings on storage and client end.
[root@linux1 ~]# mount -t nfs -o vers=3,tcp 10.20.30.40:/vol -vvv
mount.nfs: timeout set for Mon Dec 7 16:28:48 2020
mount.nfs: trying text-based options 'vers=3,tcp,addr=10.20.30.40'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.20.30.40 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 10.20.30.40 prog 100005 vers 3 prot TCP port 635
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 10.20.30.40:/vol
  • NFS Export Policy configuration 

Example:
clipboard_c6a4c109-dea4-4227-b1c5-1c66adf96b3e.png

  • NAT service is used in the environment to mask the client IP addresses.
  • Error "Access denied" and "File access permission not allowed" from Client Side:

Example:

clipboard_fa01513d-300c-40a4-b243-47605945855e.png

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.