Can't connect to a network drive? Here's the fix that actually works

Network drive not working? Don't waste time on the obvious stuff first

You've been there. You map a network drive, it works for a day, then suddenly it's gone. Or you get an access denied error that makes zero sense because you logged in with the same credentials yesterday. I've had a client last month whose entire print queue died because of a faulty network drive mapping — the printer was on a different server and the drive mapping broke the print spooler. Weird? Yes. Real? Absolutely.

Let me walk you through the actual fixes, from the 30-second no-brainer to the deeper stuff that takes 15 minutes. Stop when your drive works.

The 30-second fix: restart your PC and the file server

I know, I know. You've heard this a million times. But here's the thing: half the time, it's a cached credential issue that a reboot clears. I'd say 40% of network drive problems I see are solved by restarting both the machine and the server that holds the share.

Don't just restart your PC. If you can, restart the file server too. If you can't restart the server (because it's a production box with other services), at least restart the Server service on it. Open an admin command prompt on the server and type:

net stop server && net start server

This restarts the file sharing service without taking down the whole machine. I've used this trick on a client's Windows Server 2016 box that hosted 20 different shares — worked like a charm.

If that doesn't work, move on. Don't spend more than 30 seconds on this step. If rebooting didn't fix it, it's almost certainly not a temporary glitch.

The 5-minute fix: check and reset credentials in Credential Manager

This is the fix that solves 80% of stubborn network drive issues. Windows caches your login credentials for network shares, and sometimes they get corrupted or outdated. Here's the exact process:

1. Open Control Panel, then click Credential Manager (or search for it from the Start menu).
2. Click Windows Credentials.
3. Look for any entries under Generic Credentials that mention your file server's name or IP address. They'll look like TERMSRV/server-name or just server-name.
4. Click the arrow to expand each one, then click Remove. Say yes to the warning.
5. Now, from File Explorer, right-click the network drive and select Disconnect (if it's still mapped).
6. Remap the drive fresh: net use Z: \\server\share /persistent:yes in a command prompt, or via File Explorer's Map network drive option.

When you map it fresh, Windows will ask for credentials again. Use the correct username and password for the server. Don't save them as a different user — use the exact same domain and username format the server expects (like SERVER\username if it's a workgroup, or domain\username if it's domain-joined).

I had a client whose drive kept dropping because they were using their email address as the username, but the server only accepted the short username. Credential Manager had cached the wrong format. Removing the entry and re-mapping fixed it.

The 15-minute fix: enable SMB 1.0/CIFS File Sharing Support (if needed)

Here's where things get technical. Windows 10 and 11, by default, have SMB 1.0 disabled. That's a good security thing — SMB1 is ancient and vulnerable. But some older NAS devices, printers, or even some small business servers (I'm looking at you, Windows 7-era file servers) still require SMB1.

Don't just enable SMB1 blindly. Check what your server supports first. On the machine that's hosting the share, run this in PowerShell:

Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol

If it returns True, your server is using SMB1. If it returns False, the server is using SMB2 or later, and you don't need to touch anything.

If your server does use SMB1, you have two choices:

1. Upgrade the server — if possible, update the NAS firmware or replace the old server with something that supports SMB2 or SMB3. It's safer and faster.
2. Enable SMB1 on your Windows 10/11 client — only do this if you absolutely can't upgrade the server. Open Control Panel, go to Programs and Features, click Turn Windows features on or off. Scroll down to SMB 1.0/CIFS File Sharing Support, check the box, and click OK. Reboot. Then disable it again as soon as you've connected and copied your files to a newer server.

I had a client last year who had a 2008-era Buffalo NAS in their office. They couldn't connect their new Windows 11 laptops to it. The fix? Enable SMB1, copy the data to a new Synology NAS, then disable SMB1. The old NAS was a security risk anyway.

Still broken? Check the firewall and IP changes

If none of the above worked, you've got something rarer. Two things to check:

• Windows Defender Firewall — make sure File and Printer Sharing is allowed on private networks. Go to Control Panel > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall. Look for File and Printer Sharing. It should be checked for Private networks. If it's not, check it and click OK.
• IP address changes — if the server's IP address changed (because DHCP gave it a new one), your mapped drive will fail. Use the server's hostname instead of the IP when mapping. Or assign a static IP to the server if you can. I've seen businesses where the receptionist's computer had a mapped drive using an IP, then the server got a new IP after a power outage, and everyone lost access until they remapped.

That's it. Start with the reboot, move to Credential Manager, then check SMB. You'll fix 95% of network drive issues with those three steps. If not, you're probably dealing with a firewall or network configuration problem that needs a deeper look.