General Discussion
General Discussion
Hi,
I'm new here, so please accept my apologies if I do something wrong.
I have a security style NTFS volume mounted and shared to a client.
The client has a new host to manage that volume too. But he demands to manage through NFS protocol with Linux O.S.
I change the security style do Mixed on the volume and on the actual mixed mounted share, I kept the Share Access Control to the users in production on the NTFS services.
I changed the export policies to allow NFS protocols on the new host, adding IP Host on Client Rules, plus NFS Access Protocol and Rules of Read/Write as Any, just to start the configuration of this host.
After the export policy, we can mount the volume and see it, but we can't open directory.
It says Permission denied.
This is the Output of Security file-directory that I hve from the vserver:
Can you help me on why we doesn't have permission to open directory after mounting the volume share ?
Thank you in advance for your support,
Best regards,
Filipe
Solved! See The Solution
When the security style is mixed or unified, the effective permissions depend on the client type that last modified the permissions because users set the security style on an individual basis. For Mixed – (UNIX or NTFS permissions), depends on who last changed permissions.
If the last client was an SMB client, the permissions are Windows NTFS ACLs. Hence, when NFS clients are accessing the same resource, the storage node will need to collect windows credentials for the Unix user to determine if access can be granted. If the Windows credentials do not grant permissions on the file, access will be denied. Most likely your case.
There is plenty of stuff around this (mixed style security) on internet (google/netapp supprot site).
Some references:
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/Understanding_name-mapping_in_a_multiprotocol_environment
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/NFS_permission_denied_on_NTFS_security_style_volume_due_to_missing_fil...
When the security style is mixed or unified, the effective permissions depend on the client type that last modified the permissions because users set the security style on an individual basis. For Mixed – (UNIX or NTFS permissions), depends on who last changed permissions.
If the last client was an SMB client, the permissions are Windows NTFS ACLs. Hence, when NFS clients are accessing the same resource, the storage node will need to collect windows credentials for the Unix user to determine if access can be granted. If the Windows credentials do not grant permissions on the file, access will be denied. Most likely your case.
There is plenty of stuff around this (mixed style security) on internet (google/netapp supprot site).
Some references:
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/Understanding_name-mapping_in_a_multiprotocol_environment
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/NFS_permission_denied_on_NTFS_security_style_volume_due_to_missing_fil...
Hi,
Thank you for your prompt response.
Thank you for the documents and links you sent it.
Has we have a mixed security style and a Path Share for NTFS.
We made a workaround. We create a Qtree mount path with unix security style.
Now we can open the directory on that new mount path </path/qtree path>.
<path> - security style mixed
<qtree path> - security style unix
Thank you very much for your help !
Best regards,
Filipe
Hi , How the storage node will collect windows credentials for the Unix user to determine if access can be granted ?
Many Thanks