Fix Windows 10/11 Network Drive Access: Map SMB Share with Credentials + Reconnect

Fix Windows 10/11 Network Drive Access: Map SMB Share with Credentials + Reconnect​

Difficulty: Intermediate | Time Required: 15 minutes
Network drives that worked yesterday but suddenly prompt for a password, connect as the “wrong user,” or show errors like “Access is denied,” “Multiple connections to a server…,” or “The mapped network drive could not be created” are extremely common on Windows 10/11—especially after a reboot, password change, VPN use, or switching between Microsoft and local accounts.
This tutorial shows a clean, reliable way to map an SMB share with the exact credentials you want, save them correctly in Windows, and reconnect automatically at sign-in—using both the File Explorer method and a “power user” command-line method (NET USE). You’ll also learn how to clear conflicting cached sessions that silently break mapping.

---

Prerequisites​

Before you start, confirm you have:

• The share path in UNC format, e.g.:
  • \\NAS\Share
  • \\192.168.1.50\Backups
• A valid username/password that has permission to the share
  • Example formats:
  • NAS\username (common for NAS devices)
  • SERVERNAME\username (Windows server/local users)
  • DOMAIN\username (Active Directory)
  • [email]username@domain.com[/email] (some AD/Azure hybrid setups)
• Your PC is on the same network (or VPN) and the host is reachable:
  • Try opening \\SERVERNAME in File Explorer to verify discovery.

Windows version note: The steps below apply to Windows 10 and Windows 11. Screens may differ slightly (Windows 11 uses a simplified ribbon/toolbar), but the options are the same.

---

Step-by-step: Map the SMB share with the right credentials (File Explorer)​

1) Disconnect any existing broken or wrong mappings​

1. Open File Explorer.
2. Click This PC.
3. Under Network locations, right-click the problematic mapped drive.
4. Select Disconnect.

Why this matters: Windows may keep an old connection “alive” under the hood even after the drive disappears. Clearing it prevents credential conflicts.

---

2) Remove conflicting cached credentials (Credential Manager)​

1. Press Win + S, type Credential Manager, and open it.
2. Click Windows Credentials.
3. Look for entries related to your server/share, such as:
   • \\NAS
   • \\NAS.local
   • \\192.168.1.50
   • Any entry that matches the host you’re mapping
4. Expand the matching entry and click Remove.

Tip: If the server can be reached by name and IP, you may have two credential entries. Remove both if you’re unsure and re-add cleanly.

---

3) Map the drive and force Windows to ask for credentials​

1. In File Explorer, go to This PC.
2. Click Map network drive.
   • Windows 11: Click the three-dot menu (⋯) or toolbar option, then Map network drive.
3. Choose an available Drive letter (e.g., Z:).
4. In Folder, enter your share path, e.g. \\NAS\Share.
5. Check Reconnect at sign-in.
6. Check Connect using different credentials.
7. Click Finish.
8. When prompted, enter your credentials:
   • User name: NAS\username (or DOMAIN\username, etc.)
   • Password: your share password
9. (Optional but recommended) Check Remember my credentials.
10. Click OK.

If successful, the drive will appear under This PC and should reconnect automatically after a reboot.

Warning: If you use the wrong username format, Windows may authenticate as a guest or as your current Windows account. If you get “Access denied,” re-map and try SERVERNAME\user or NAS\user.

---

Step-by-step: Map and reconnect using NET USE (more reliable + scriptable)​

If File Explorer mapping is flaky—or you want a deterministic setup—use net use.

4) Open an elevated Command Prompt (recommended)​

1. Press Win + X.
2. Choose Windows Terminal (Admin) or Command Prompt (Admin).
3. If prompted by UAC, click Yes.

---

5) Clear existing SMB sessions to that server (prevents “multiple connections”)​

Run:
net use
Look for any connections to the target host (by name or IP). Then remove them:
net use \\NAS /delete
Or remove all network connections (more aggressive):
net use * /delete

Warning: net use * /delete disconnects all mapped drives and SMB sessions. Use it only if you understand the impact.

---

6) Map the share with explicit credentials + persistent reconnect​

Use this template:
net use Z: \\NAS\Share /user:NAS\username yourpassword /persistent:yes
Examples:
net use Z: \\192.168.1.50\Backups /user:NAS\backupuser MySecurePass /persistent:yes
For a domain:
net use Z: \\FILESERVER\Dept /user:DOMAIN\j.smith MySecurePass /persistent:yes

Security note: Putting passwords in clear text is not ideal. If you’d rather type it interactively, omit the password:
net use Z: \\NAS\Share /user:NAS\username /persistent:yes
Windows will prompt you securely.

---

7) Verify reconnect behavior​

1. Restart your PC (or sign out/in).
2. Open File Explorer → This PC.
3. Confirm the drive reconnects without prompting.

If it doesn’t reconnect:

• Ensure you used /persistent:yes or checked Reconnect at sign-in in Explorer.
• Confirm the credential is saved under Credential Manager → Windows Credentials.

---

Tips, warnings, and troubleshooting​

Tip: Use consistent server naming (avoid duplicate credentials)​

Windows treats these as different “servers”:

• \\NAS
• \\NAS.local
• \\192.168.1.50

If you map with one but saved credentials for another, reconnect may fail. Pick one naming method and stick with it.

---

Fix: “Multiple connections to a server or shared resource by the same user…”​

This usually means Windows already has an SMB session to that host using different credentials.

1. Disconnect all sessions:
   net use \\NAS /delete
2. Remove stored credentials for that host in Credential Manager.
3. Map again with the correct username format.

---

Fix: “Access is denied” (but password is correct)​

Common causes:

• You authenticated as the wrong user (Windows silently reused a cached session).
• The NAS/Server expects NAS\user not just user.
• Permissions on the share (or NTFS permissions on a Windows server) don’t allow that user.

Try:

• Clear sessions (net use \\NAS /delete)
• Remove saved credentials
• Re-map with SERVER\user or DOMAIN\user

---

Fix: Drive shows “Disconnected” after boot until you click it​

This can happen if the network isn’t ready at sign-in.
Workarounds:

• Wait 30–60 seconds after logon; Windows often reconnects in the background.
• If you’re on Wi‑Fi, ensure you’re connected before logging in.
• On managed/Pro systems, admins sometimes enable policies like “Always wait for the network…”; home users typically don’t need this.

---

Note about SMB versions​

• Windows 10/11 use modern SMB (SMB2/SMB3).
• SMB1 is legacy and insecure; only enable it if you fully understand the risk and have a specific legacy device that requires it.

---

Conclusion​

Mapping an SMB share with the correct credentials is mostly about eliminating cached conflicts and then creating a persistent connection with the username format your server expects. Once you remove old sessions and store credentials cleanly, your network drive should reconnect reliably after restarts—without repeated password prompts or “access denied” surprises.
Key Takeaways:

• Clear old SMB sessions and wrong mappings before re-mapping (net use … /delete helps).
• Remove conflicting entries in Credential Manager so Windows doesn’t reuse the wrong login.
• Map using Reconnect at sign-in (Explorer) or /persistent:yes (NET USE) for automatic reconnection.
• Use consistent server addressing (name vs IP) to avoid duplicate credential problems.

---

This tutorial was generated to help WindowsForum.com users get the most out of their Windows experience.