Update Mapped Network Drives to Use duq.local (Kerberos Authentication)

Tags cts

KB: Update Mapped Network Drives to Use duq.local (Kerberos Authentication)

Overview

Some users have mapped network drives using short names or IP addresses. This causes Windows and macOS to fall back to NTLM authentication instead of Kerberos, which is less secure and may cause access or performance issues.

✅ Fix: Remap your drives using the fully qualified domain name (FQDN):

\\servername.duq.local\sharename

 

Windows 11 Instructions

Step 1 – Disconnect Existing Drive

  1. Open File Explorer
  2. Click This PC
  3. Locate the mapped drive
  4. Right-click the drive → select Disconnect

 

Step 2 – Map Drive Using duq.local

  1. In File Explorer, click This PC
  2. Click the three dots (… ) menu → select Map network drive
  3. Choose a Drive letter
  4. In the Folder field, enter the new path using FQDN:
    \\servername.duq.local\sharename

    ✅ Example:
    \\einstein.duq.local\deptshare
  5. Ensure:
    • ✅ Reconnect at sign-in is checked
    • ✅ Connect using different credentials is unchecked (unless instructed otherwise)
  6. Click Finish

 

 

macOS Instructions

Step 1 – Disconnect Existing Share

  1. In Finder, locate the mounted share (in the sidebar or desktop)
  2. Click the eject icon next to the share

 

Step 2 – Connect Using duq.local

  1. In Finder, click Go → Connect to Server (or press Command + K)
  2. In the Server Address field, enter:
    smb://servername.duq.local/sharename

    ✅ Example:
    smb://einstein.duq.local/deptshare
  3. Click Connect

 

Step 3 – Authenticate

  • Use your domain credentials:
    username: yourusername

    or
    yourusername@duq.local
  • Select Remember this password in Keychain if appropriate

 

Step 4 – Add to Login Items (Optional)

To automatically reconnect at login:

  1. Go to System Settings → General → Login Items
  2. Click +
  3. Add the mounted network share

 

Important Notes

 

Why This Matters

Using the full domain name:

  • ✅ Enables Kerberos authentication
  • ✅ Improves security (no NTLM fallback)
  • ✅ Reduces authentication prompts and access issues
  • ✅ Aligns with domain security policy

 

Print Article