Cannot access shared network drives

Summary

This guide helps you troubleshoot and resolve: Cannot access shared network drives. Follow the steps below to fix the issue.

Common Causes

Problem

You cannot access shared drives or folders on the company network (e.g., \\server\shared or mapped drives such as S:).

Symptoms

• “Network path not found” error
• “Access denied” message
• Drive letter appears but shows “Disconnected”
• Files take a long time to load

Solutions

Step 1 – Verify VPN connection

1. Open the VPN client and confirm it shows a connected status.
2. Ensure the VPN is configured to route internal traffic.
3. If you are working remotely, see Connecting to company network remotely for additional configuration steps.

Step 2 – Verify VPN DNS resolution and split‑tunnelling

1. Open an elevated Command Prompt.
2. Run nslookup servername using the DNS servers assigned to the VPN adapter.
3. If the name does not resolve, test with nslookup 192.168.1.10 (replace with the server’s IP).
4. Confirm that split‑tunnelling is not preventing internal DNS queries; disable it temporarily if necessary.

Step 3 – Check the mapped‑drive status

1. Open File Explorer (Windows + E).
2. In the navigation pane, verify that your mapped drives are listed.
3. If a drive shows a red X, it is disconnected.
4. Right‑click the drive, choose Disconnect, then attempt to reconnect.

Step 4 – Clear stale mappings

1. Open a Command Prompt (Windows + R, type cmd, press Enter).
2. Run net use * /delete to remove any lingering connections.
3. Proceed to Step 5 to re‑map the drive.

Step 5 – Re‑connect the mapped drive

1. Press Windows + R, type explorer, and press Enter.
2. In the address bar, enter the full UNC path (e.g., \\servername\sharename).
3. If prompted, provide your domain credentials. Ensure you are signed into the correct domain.
4. To map permanently: right‑click This PC → Map network drive → select a drive letter → enter the path → check “Reconnect at sign‑in”.

Step 6 – Verify name resolution, firewall settings and SMB version

1. Open a Command Prompt and run nslookup servername or ping the server’s IP address to confirm DNS resolution.
2. Ensure TCP ports 445 and 139 are allowed on any intervening firewalls.
3. SMBv1 is deprecated. It should remain disabled unless you are connecting to a legacy server that absolutely requires it. If required, enable SMBv1 temporarily via “Turn Windows features on or off”, perform the test, then disable it immediately afterwards.

Step 7 – Confirm Group Policy or logon‑script drive mappings

1. Run gpresult /h gpresult.html and open the generated HTML file to verify that drive‑mapping policies have applied.
2. Check the Event Viewer under Applications and Services Logs → Microsoft → Windows → GroupPolicy → Operational for any drive‑mapping errors.
3. If a logon script is used, open a Command Prompt and run the script manually (e.g., \\domain\sysvol\domain\scripts\mapdrives.bat) to test.

Step 8 – Run the network troubleshooter

1. Open Settings (Windows + I).
2. • Windows 10: Network & Internet → Status → Network troubleshooter.
   • Windows 11: System → Troubleshoot → Other troubleshooters → Network Adapter.
3. Follow the prompts and apply any recommended fixes.

Step 9 – Check permissions and Credential Manager

1. Confirm you have the required share permissions. See File sharing permission issues for guidance.
2. Open Credential Manager and remove or update any stored credentials for the server.

Step 10 – Verify the server is online

1. Open a Command Prompt and run ping servername (replace with the actual server name).
2. If you receive “Request timed out” or “Destination host unreachable”, the server may be offline; contact IT via Open a Ticket.

Step 11 – Offline Files / Sync status

1. If the Sync Centre is still present (Control Panel → Sync Centre), ensure Offline Files are not causing a “disconnected” state.
2. On Windows 10/11 you can also manage offline files via Settings → Sync your files. Disable the feature temporarily to see if the drive reconnects.
3. Note: Offline Files is a legacy feature and may be hidden in newer builds.

Step 12 – Check local firewall and antivirus/endpoint protection

1. Open Windows Defender Firewall (or your third‑party firewall) and confirm that inbound and outbound rules allow SMB traffic on ports 445 and 139.
2. Review any antivirus or endpoint‑protection alerts that may be blocking SMB. See Antivirus alerts – what to do for remediation steps.

Step 13 – Azure AD‑joined or hybrid‑joined devices

1. Ensure the device is signed into the corporate Azure AD account.
2. Verify the device complies with conditional‑access policies (e.g., encryption, OS version). See How to protect your PC with built‑in Windows security features.
3. If the device is hybrid‑joined, confirm it can obtain a Kerberos ticket for the domain; run klist to view tickets.

What to do next – Quick reference

• Confirm VPN is connected and DNS resolves internal names.
• Check drive status, clear stale mappings, and re‑map the drive.
• Verify firewall/SMB ports and ensure SMBv1 remains disabled.
• Validate Group Policy or logon‑script mappings.
• Run the appropriate network troubleshooter for your OS version.
• Review permissions, Credential Manager, and server availability.
• Disable Offline Files if it interferes.
• Check local firewall, antivirus, and Azure AD compliance.

Need more help?

If you still cannot access shared drives, Open a Ticket and provide:

• The specific drive or folder you are trying to reach.
• The exact error message displayed.
• Whether other network resources (e.g., SharePoint sites) are accessible – see Cannot access SharePoint site for related troubleshooting.
• Any recent Windows updates (see How to update Windows) or domain‑credential login issues (Cannot login with domain credentials).

Still Having Issues?