#Nfs run for mac windows#

SMB clients can do *some* permissions changes, but on a very limited basis. SMB clients will require mappings to a valid UNIX user for permissions NFS clients will only require mapping to a UNIX user name if using NFSv4 ACLs. UNIX security styles use UNIX mode bits (rwx) and/or NFSv4 ACLs Then, permissions are controlled via ACLs.

#Nfs run for mac windows#

SMB clients will map to UNIX users and NFS clients will require mappings to valid Windows users for authentication. TR-4887 goes into more detail on how all that works, but at a high level: The way ONTAP does Multiprotocol NAS (and keeps permissions predictable) is via name mappings and volume вЂњsecurity styles,вЂќ which controls what kind of ACLs are in use. Many clients can actually do both protocols вЂ“ MacOS is one of those clients. In ONTAP, you can serve the same datasets to clients regardless of the NAS protocol they use (SMB or NFS). This wonвЂ™t be an exhaustive list, and it is certain to change over time and possibly make its way into a TR, but here we goвЂ¦ ONTAP and Multiprotocol NASД«efore I get into the MacOS client stuff, we need to understand ONTAP multiprotocol NAS, as it can impact how MacOS clients behave.

A blog is a great place to do that, as it might help other people in similar scenarios. When IвЂ™m testing stuff out for customer deployments that I donвЂ™t work with a ton, I like to keep notes on the work so I can reference it later for TRs or other things.