During the rollout of a new NAS array, you create a share for the Projects department and enable the CIFS service. Linux servers can mount the same volume over NFS without problems, but Windows 11 clients that try to map \NAS01\Projects are repeatedly prompted for credentials and finally receive Access denied, even though they are logged on with valid domain accounts. Networking, DNS, and time synchronization are all correct. Which configuration step was MOST likely missed on the NAS?
Create and format an iSCSI LUN with NTFS and present it to a Windows file server.
Join the NAS CIFS/SMB server to the Active Directory domain so Windows clients can authenticate with Kerberos or NTLM.
Enable root-squash on the NFS export to prevent UID conflicts.
Increase the MTU on the NAS interfaces to support jumbo frames on the VLAN trunk.
Windows hosts expect a CIFS/SMB file server to participate in Active Directory so they can authenticate with Kerberos or (if permitted) NTLM using their existing domain logins. If the NAS has not been joined to the AD domain, the SMB service can only use local accounts or work-group authentication, so domain users are prompted for alternate credentials and ultimately rejected. The other options would not affect SMB domain authentication: root-squash is an NFS setting, formatting an iSCSI LUN with NTFS moves the workload off the NAS, and jumbo-frame tuning influences performance, not access control.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is CIFS/SMB, and how does it differ from NFS?
Open an interactive chat with Bash
What is Kerberos authentication, and why is it crucial for CIFS/SMB in Active Directory environments?
Open an interactive chat with Bash
What happens if a NAS is not joined to an Active Directory domain when using CIFS/SMB?