Summary

This article shows you how to connect to shared network folders, map them as drive letters in File Explorer, and fix the failures that follow — the red X that clears itself, the "Could not reconnect all network drives" message at sign-in, drives that break every morning on a VPN laptop, and prompts that reject the password you know is correct.

In this guide

• 1. Access a Shared Folder Directly (Without Mapping)
• 2. Map a Network Drive (Permanent Drive Letter)
• 3. Map a Network Drive Using the Command Line
• 4. Disconnect (Unmap) a Network Drive
• 5. Pin a Network Location to Quick Access
• 6. Reconnect a Mapped Drive After a Network Change
• The mapped drive shows a red X but opens when you click it
• "Could not reconnect all network drives" appears at sign-in
• The drive fails every morning on a VPN laptop
• The drive rejects your password after a password reset
• The server name works for a colleague but not for you

Before You Start

• Windows 11 or Windows 10. On a Mac the route is different — see How to Connect a Mac to a Shared Network Drive.
• Your computer must be connected to the same network as the shared folder (on-site, VPN, or DirectAccess).
• You need the network path (UNC path) to the shared folder — this looks like \\servername\sharename (e.g., \\fileserver01\Finance). If you do not know it, ask your IT team for the full share path in the form \\server\share. That exact string is what every step below needs.
• Make sure you have permission to access the shared folder. Your IT team manages share permissions.
• No admin rights are required for any step in this article.

Instructions

1. Access a Shared Folder Directly (Without Mapping)

You can open a shared folder on-the-fly without permanently mapping it as a drive letter.

1. Press Windows + E to open File Explorer.
2. Click in the address bar at the top of the File Explorer window.
3. Type the full network path to the shared folder (e.g., \\fileserver01\Finance) and press Enter.
4. If prompted, enter your username and password. Use the format DOMAIN\username or [email protected] if a simple username does not work.
5. The shared folder opens and you can browse, open, and edit files as if they were on your local drive.

Tip: To quickly access a path you recently used, open the Run dialog (Windows + R), type the UNC path, and press Enter.

2. Map a Network Drive (Permanent Drive Letter)

Mapping creates a persistent drive letter (e.g., Z:) in File Explorer that reconnects automatically every time you sign in.

1. Press Windows + E to open File Explorer.
2. Click This PC in the left navigation pane.
3. Click the three-dot menu (⋯) in the toolbar and select Map network drive (Windows 11). On Windows 10, click Computer > Map network drive in the ribbon.
4. In the Map Network Drive dialog:
   • Drive: Select a drive letter from the dropdown (e.g., Z:, S:, P:). Choose a letter that is meaningful (e.g., S: for Shared, P: for Projects).
   • Folder: Enter the full network path (e.g., \\fileserver01\Finance). Click Browse if you want to navigate to it visually.
   • Reconnect at sign-in: Check this box to reconnect the drive automatically every time you log in.
   • Connect using different credentials: Check this box only if the shared folder requires a username different from the one you used to sign in to Windows.
5. Click Finish.
6. The mapped drive now appears under This PC in File Explorer with the drive letter you selected.

Verification: Open File Explorer and click This PC. The mapped drive appears in the Network locations section with the assigned drive letter. Double-click it to confirm the contents load.

3. Map a Network Drive Using the Command Line

If the graphical method does not work, or you need to script the mapping, use the net use command.

1. Press Windows + R to open the Run dialog.
2. Type cmd and press Enter to open the Command Prompt.
3. Type the following command and press Enter:

   net use Z: \\fileserver01\Finance /persistent:yes

   • Replace Z: with your desired drive letter.
   • Replace \\fileserver01\Finance with your actual network path.
   • /persistent:yes makes the mapping survive a reboot.
4. If prompted, enter your username and password.
5. A confirmation message appears: The command completed successfully.

Tip: To see all currently mapped drives, open Command Prompt and type: net use

4. Disconnect (Unmap) a Network Drive

Remove a mapped drive when you no longer need it.

Method A — File Explorer

1. Open File Explorer and click This PC.
2. Right-click the mapped drive you want to remove.
3. Select Disconnect.
4. The drive letter disappears from the list.

Method B — Command Line

1. Open Command Prompt.
2. Type the following command and press Enter:

   net use Z: /delete

   • Replace Z: with the drive letter you want to remove.

5. Pin a Network Location to Quick Access

If you access a shared folder frequently but do not want a permanent drive letter, pin it to Quick Access instead.

1. Navigate to the shared folder in File Explorer using the UNC path (Method 1).
2. Once the folder is open, right-click the folder name in the left navigation pane or address bar.
3. Select Pin to Quick Access (Windows 10) or Pin to Home (Windows 11).
4. The shared folder now appears in your Quick Access list for one-click access.

Verification: Close and reopen File Explorer. The pinned shared folder appears at the top of the navigation pane under Quick Access.

6. Reconnect a Mapped Drive After a Network Change

Mapped drives sometimes fail to reconnect after switching networks (e.g., coming back from remote work to the office).

1. Open File Explorer and click This PC.
2. If the mapped drive shows a red X icon, double-click it. Windows attempts to reconnect.
3. If it does not reconnect:
   • Confirm you are on the correct network (office network or VPN).
   • Right-click the drive and select Disconnect.
   • Re-map the drive using Method 2 or Method 3.
4. If your computer is on VPN, ensure the VPN is connected before opening the mapped drive.

Note: If mapped drives consistently fail to reconnect at startup, it may be because the network connection is not established before Windows tries to mount the drive. Ask your IT team to confirm the exact UNC path for the share (\\server\share) and whether a logon script or Group Policy already maps it — if one does, the startup delay belongs in that script rather than on your machine, and fixing it there fixes it for your whole team.

Troubleshooting

DANGER

If you receive an "Access denied" or "You do not have permission" error, the issue is almost always a permissions problem managed by your IT team. Document the exact network path, the error message, and your username, then submit a ticket — you cannot fix share permissions yourself.

Symptom / Error	Potential Cause	Solution
"Windows cannot access \\server\share"	Incorrect path or server offline	Verify the network path with your IT team. Ensure you are on the same network (or connected via VPN). Try pinging the server: open Command Prompt and type ping servername.
"Access is denied" when opening the share	Insufficient permissions	Share permissions are set by IT, not on your machine. Send them: I get "Access is denied" opening \\fileserver01\Finance from my laptop. My user name is <your user name>. Please confirm whether I am in the group that has access to this share, and add me if not. Fill in your own share path and user name — naming the path is what stops the ticket coming back to ask for it.
Mapped drive shows a red X at startup	Network not ready before drive mounts	Double-click the drive to force reconnect. If persistent, disconnect and re-map with Reconnect at sign-in checked.
Drive letter conflict (letter already in use)	Another device or mapping uses the same letter	Choose a different drive letter when mapping. Use net use in Command Prompt to see all current mappings.
"The specified network password is not correct"	Password changed or cached credentials expired	Open Control Panel > Credential Manager > Windows Credentials. Delete the old entry for the server and try connecting again with your current password.
Mapped drive works on-site but not remotely	VPN not connected or split-tunnel excludes file server	Connect to VPN first, then access the mapped drive. If still failing, ask IT to confirm the file server is reachable over the VPN, and give them the full path you are trying to open.

The mapped drive shows a red X but opens when you click it

Most of the time this is not a fault, and knowing that saves a ticket.

Windows drops the live connection to a share it has not touched for a while — the documented default is 15 minutes of inactivity — so the file server is not left holding a session nobody is using. The drive letter stays mapped. Only the connection goes, and Windows does not re-check it until something asks for the drive. File Explorer marks it with a red X in the meantime.

Double-click the drive. It reconnects, normally in under a second, the X clears, and the contents load. That is the whole fix. Disconnecting and re-mapping a drive that behaves this way changes nothing, because nothing was broken.

The timeout itself is a setting on the file server, not on your computer, so there is nothing to change at your end and nothing worth raising. Treat the red X as a fault only when double-clicking returns an error instead of opening the folder — that case is covered below.

"Could not reconnect all network drives" appears at sign-in

Windows shows this notification when it restores your mapped drives during sign-in and at least one of them does not answer. Alongside it, the drives carry a red X in File Explorer.

The mapping itself is intact. Only the reconnect attempt failed, almost always because the network was not ready yet.

1. Dismiss the notification.
2. Confirm you are on a network that reaches the file server. If you are working off-site, connect the VPN and wait for it to report that it is connected.
3. Press Windows + E to open File Explorer and select This PC.
4. Double-click the mapped drive. It reconnects and works normally for the rest of the session.
5. If double-clicking returns an error instead, right-click the drive, select Disconnect, then map it again using Map a Network Drive (Permanent Drive Letter) above. Disconnecting removes only the drive letter on your own computer — no file on the share is touched, and nobody else's access changes.

Getting this message once after an unusual start-up is normal. Getting it every single morning is the ordering problem in the next section.

The drive fails every morning on a VPN laptop

On a company laptop the sign-in sequence works against mapped drives, and the order is what causes it:

1. You sign in.
2. Windows immediately tries to restore every drive marked Reconnect at sign-in.
3. The VPN client starts and connects, which takes several seconds longer.
4. By the time the tunnel is up, Windows has already given up and marked the drives unavailable.

Nothing is broken. The drives were asked to reach a server that was not reachable yet. Two fixes work from a standard account:

• Connect the VPN first, then open the drive. Sign in, wait for the VPN to report connected, then open File Explorer and double-click the drive. It connects on the first attempt and stays connected for the session.
• Reconnect afterwards. If you already opened the drive and got the error, connect the VPN and double-click the drive again. You do not need to re-map it, and re-mapping will not help.

You cannot reorder Windows sign-in from a standard account. If this hits your whole team every morning, the durable fix belongs with IT, and it is worth asking for by name:

Our mapped drives are restored at sign-in before the VPN connects, so we get "Could not reconnect all network drives" every morning and have to open each drive by hand. Share path: \\fileserver01\Finance. Drive letter: S:. VPN client: name of your VPN app. Can the mapping be delivered by a logon script or Group Policy preference that runs after the VPN connects, or triggered by the VPN connection event, instead of at sign-in?

Microsoft's own guidance for this problem is to trigger the reconnect from the VPN connection event rather than from sign-in, so that is a request your IT team will recognise — and fixing it there fixes it for everyone on the same setup rather than one laptop at a time.

The drive rejects your password after a password reset

The symptom is either the message The specified network password is not correct, or a sign-in prompt that reappears every time however carefully you type the password you know is right.

Windows saved your sign-in for that server the first time you connected. Changing your account password does not update that saved copy, so Windows keeps presenting the old one and the server keeps refusing it. Removing the stale entry is the fix.

1. Type credential manager in the taskbar search box and select Credential Manager Control panel.
2. Select Windows Credentials.
3. Find the entry whose name contains the server from your share path. For \\fileserver01\Finance, look for fileserver01.
4. Select the entry to expand it, then select Remove (older Windows builds label this Remove from Vault) and confirm.
5. Open File Explorer, select This PC, and double-click the mapped drive.
6. Enter your current password when prompted. If your plain user name is rejected, use DOMAIN\username or [email protected]. Tick the box to save the new details so you are not asked again.

What removing a saved credential costs you: it deletes Windows' stored copy of one user name and password for one server. Your account password does not change, and no file on the share is touched. The next time you open the drive Windows asks you to sign in, which is the point. If that same saved entry was also getting you into another share on the same server, you will be asked to sign in there once as well.

If Windows rejects your current password too, the account rather than the credential is the problem — confirm you can sign in to another company service with the same password, then raise it with IT quoting the exact message on screen.

The server name works for a colleague but not for you

Someone at the next desk opens \\fileserver01\Finance without a prompt while you get Windows cannot access \\fileserver01\Finance. Two things are worth checking before this becomes a ticket, and both take under a minute.

Check which network you are on. Guest Wi-Fi, a phone hotspot, and a hotel network all reach the internet without reaching the file server. Select the network icon in the taskbar and read the name of the connection. Switch to the corporate network or connect the VPN, then try the path again.

Try the full server name. Ask your colleague for the server's full name — it looks like fileserver01.company.local — then type the full path into the File Explorer address bar, for example \\fileserver01.company.local\Finance, and press Enter. If the full name opens the folder and the short name does not, the share and your permissions are both fine, and the problem is name resolution on your machine. That single result changes what IT has to look at.

Send them this, with your own values filled in:

I cannot reach \\fileserver01\Finance from my laptop. A colleague on the same team opens the same path from the same office with no problem. The short name gives "Windows cannot access \\fileserver01\Finance". The full name \\fileserver01.company.local\Finance opens normally / gives the same error. I am connected to network or VPN name. My user name is your user name and my computer name is your device name, from Settings > System > About > Device name. Please confirm the share path and whether my machine is resolving the server name.

Naming the exact share path is what stops the ticket coming back to ask for it.

Related Articles

• How to Troubleshoot VPN Connection Issues (User-Level Steps)
• How to Use Quick Access and Pin Folders in File Explorer
• How to Use File Explorer Tabs in Windows 11
• How to Share Files and Folders via OneDrive
• How to Manage Files in SharePoint Document Libraries

Did this solve your problem?