Files: Deployment, Configuration, and Shares
Deployment prerequisites
Nutanix Files is deployed as a file server made up of File Server VMs on an AHV cluster. You need a storage container, a network with enough addresses for FSVMs and the file server VIP, DNS, NTP, and Active Directory for SMB. The file server must be joined to AD before SMB shares work. NFS exports do not require an AD join, but they do require correct network access and export rules.
Shares and permissions
- SMB shares combine share-level permissions and NTFS ACLs. Effective access is the intersection of both.
- AD identities and groups drive SMB access. SMB signing and encryption can be enabled for security.
- NFS exports use host or network allowlists, read-write or read-only settings, root squash, and user mapping.
- Multiple FSVMs provide file server high availability; the VIP moves if an FSVM fails.
- Share-level snapshots and quotas help with recovery and capacity control.
Worked example
A user can see an SMB share but receives access denied. Check AD join and DNS first, then verify the share permission and the NTFS ACL. If both look correct, check SMB signing or encryption compatibility on the client. For an NFS client that cannot write, inspect the export rule and root squash before changing file ownership.
Traps
Do not troubleshoot only NTFS; SMB access is the intersection of share and NTFS permissions. Do not assign FSVM addresses by DHCP. Do not forget the file server VIP. Do not assume NFS authentication uses AD. Do not widen an NFS export to all clients as a quick fix.
Key points
- Files deploys FSVMs on an AHV cluster.
- SMB requires AD join; NFS uses export rules.
- SMB effective access is share permission plus NTFS ACL.
- The file server VIP is separate from individual FSVM addresses.
- NFS root squash and allowlists are key security controls.