Can’t Access a Shared Network Drive or Folder on Windows

Can’t Access a Shared Network Drive or Folder on Windows

You try to open a shared drive or folder from another PC or a NAS on your network and instead you get “Windows cannot access \\PC-NAME\Share,” a permission-denied message, or a mapped drive that just shows as disconnected in File Explorer.

Network shares depend on several things lining up at once — both devices actually being reachable on the same network, sharing and discovery settings being turned on, credentials matching what the other device expects, and in some cases an older protocol version Windows no longer trusts by default. Any one of those breaking produces roughly the same frustrating error.

Quick explanation: this guide covers what the different error messages actually mean, confirming both devices are really on the same network, network discovery and file sharing settings, credential and permission mismatches on mapped drives, the older SMB1 protocol issue that trips people up with older NAS devices, and when a firewall is the real culprit.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

Most “can’t access a shared drive” problems come down to one of three things: Network discovery and file and printer sharing being turned off in Windows’ network settings, stale or mismatched login credentials saved for that share, or both devices no longer actually being on the same network (a Wi-Fi reconnect can quietly drop a PC onto a different subnet). Open Control Panel > Network and Sharing Center > Advanced sharing settings and confirm discovery and sharing are on for your current network profile, then try removing and re-entering the share’s saved credentials through Credential Manager. If it’s an older NAS or router-attached drive, an outdated SMB1-only setup is also a common cause, covered further down.

What “Windows Cannot Access” Actually Means

The exact wording of the error narrows things down. “Windows cannot access \\PC-NAME\Share” with no further detail usually means Windows can’t even reach the other device — a network or discovery problem, not a permissions one. A message that specifically mentions you don’t have permission, or asks you to enter network credentials, means the connection worked fine but the login being offered isn’t accepted.
A previously mapped drive letter showing as disconnected in File Explorer (often with a small red X) means Windows successfully connected to it before, but can’t right now — that’s a strong hint the other device is off, asleep, or has moved to a different network rather than the mapping itself being broken.
Knowing which of these you’re actually looking at saves time, since a connectivity problem and a credentials problem need completely different fixes even though the symptom on screen looks similar.

Confirm Both Devices Are Actually on the Same Network

A shared folder is only reachable from devices on the same local network. It’s easy to assume that’s true and be wrong — a PC that reconnected to a guest Wi-Fi network, a second router creating its own separate subnet, or a device still connected to a VPN can all technically have “internet access” while being invisible to everything else on the home network.
Check the IP address on both devices. If one is something like 192.168.1.x and the other is 192.168.0.x or 10.0.0.x, they’re on different subnets and won’t see each other no matter what sharing settings say. Open Command Prompt and run the command below on each device to compare.
ipconfig
Fixyfier’s Network & Connectivity tools include a View IP Configuration shortcut that shows the same information without opening Command Prompt, making it quick to compare the address on this PC against the other device.

Network Discovery and File Sharing Turned Off

Windows treats network profiles differently depending on whether you told it a network is Private or Public when you first connected. On a Public profile, network discovery and file sharing are switched off by default as a security precaution — which also means shared folders on that network simply won’t show up, even though nothing about the share itself is broken.
Open Settings > Network & internet > Wi-Fi (or Ethernet), confirm the network is set to Private, then go to Control Panel > Network and Sharing Center > Change advanced sharing settings and turn on network discovery and file and printer sharing for that profile. This needs doing on both the PC trying to connect and the device sharing the folder.
This single setting is responsible for a surprisingly large share of “the shared folder just disappeared” reports, especially after reinstalling Windows or reconnecting to Wi-Fi after being away from a network for a while.

Mismatched Credentials on a Mapped Drive

If the error specifically mentions permissions or repeatedly asks for a username and password, Windows is reaching the share fine — it’s the login it’s offering that the other device won’t accept. This happens often after a password change on the sharing PC, since Windows can keep offering the old, now-invalid credentials automatically without asking.
Open Control Panel > Credential Manager > Windows Credentials, find the entry for the network address in question, and remove it. The next time you try to open the share, Windows will prompt you fresh, and entering the current, correct username and password fixes it in one pass.
This is worth checking before anything more involved whenever access to a share stops working right after a password was changed anywhere in the household or office.
NordVPN
One Thing Worth Knowing

Fixing Shared Drive Access Sometimes Means Loosening Network Defenses

Getting a stubborn share working again can mean temporarily switching a network to Private, or opening firewall exceptions for file sharing — settings that are fine on your own home or office network, but worth being more careful about on a coffee shop Wi-Fi or any network you don't control. NordVPN encrypts your traffic so you're not left more exposed while those settings are loosened somewhere unfamiliar.

Browse More Safely

Older NAS Devices and the SMB1 Protocol Problem

Recent versions of Windows disable the older SMB1 file-sharing protocol by default, since it’s an old, insecure standard. Most modern NAS boxes, routers with USB sharing, and other PCs use the newer SMB2 or SMB3 protocol without issue — but some older or budget NAS devices, and some routers’ USB-attached storage features, still only speak SMB1, and Windows simply refuses to connect to them without extra configuration.
This shows up as the share being completely unreachable despite discovery and sharing settings all being correct, often with a message about an unsupported version of the SMB protocol. Updating the NAS or router’s firmware to a version that supports SMB2/3 is the better long-term fix; re-enabling the SMB1 client through Turn Windows features on or off works too, but it does bring back a genuinely outdated, less secure protocol just to talk to one older device.
Treat this as the likely explanation any time the device you’re trying to reach is several years old and every other troubleshooting step here checks out fine.

When a Firewall Is Blocking the Connection

If both devices are confirmed to be on the same network, sharing settings are on, and credentials are correct, a firewall — Windows Defender Firewall or third-party security software on either device — silently blocking file and printer sharing traffic is the remaining likely cause. It tends to produce the same generic “cannot access” message as a network problem, which is what makes it easy to miss.
Open Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall and confirm File and Printer Sharing is checked for the Private network column on both the PC opening the share and the one hosting it. If either device runs third-party antivirus with its own firewall, check its network sharing exception there too.
Fixyfier’s Network & Connectivity tools include a Test Internet Connection shortcut and a one-click Reset All Network Configurations option — useful for ruling out a broader, stuck networking state before assuming the problem is a firewall rule specifically blocking this one share.

Frequently Asked Questions

Why did a shared drive that worked yesterday suddenly stop working today?

The most common cause is one of the two devices reconnecting to a different network profile or a different Wi-Fi network entirely — for example after a router reboot, a sleep/wake cycle, or Windows updating and resetting a network to Public. Confirming both devices are still on the same network and the profile is still set to Private, both covered above, resolves most cases like this.

Do I need to map a drive letter to access a shared folder, or can I just browse to it?

Mapping a drive letter isn’t required — typing the share’s network path directly into File Explorer’s address bar works too, and it’s a useful way to test whether the underlying connection and permissions are actually fine before troubleshooting a specific mapped drive that’s showing as disconnected.

Is it safe to re-enable SMB1 just to connect to an older NAS device?

It works, but SMB1 is a genuinely outdated protocol with known security weaknesses, so it’s best treated as a temporary workaround rather than a permanent setting — checking whether the NAS or router has a firmware update that adds SMB2/3 support is worth doing first, since that removes the need to re-enable SMB1 at all.

Let Fixyfier Rule Out the Network Itself First

Fixyfier’s Network & Connectivity tools put View IP Configuration, Test Internet Connection, and a one-click Reset All Network Configurations a click away, so you can confirm the network itself is healthy before spending time chasing sharing settings, credentials, or firewall rules that were never the actual problem.
Get Fixyfier from the Microsoft Store