Windows 11 can't connect to a shared folder: fixes

If Windows 11 can’t open a shared folder, the cause is usually one of four things: the other device isn’t reachable, the path is wrong, Windows is holding bad saved credentials, or the share permissions don’t allow your account in. The safest fix is to check reachability and the exact path first, then clear saved credentials, then review Windows sharing settings and the server or NAS permissions. The error text matters, because “network path not found” and “access denied” point to different problems.

Symptom

The exact message varies.

This usually appears when you try to open a shared folder from File Explorer, map a network drive, or reconnect to a share after a password change or a restart.

If the share is blocked by credentials, Windows may keep prompting for a password. If the path or name cannot be resolved, you may be told the network path can’t be found. If the share opens but your account is refused, you’ll usually get an access denied message.

Before you start

• This applies to Windows 11 connecting to a shared folder on another PC, a server, or a NAS.
• You do not need administrator rights for the first checks, but you may need them to change Windows sharing or SMB settings.
• No restart is required for the first steps.
• Make sure you know the exact share path, such as the computer name and share name, before you change anything.
• If the shared folder contains important data, avoid changing permissions on the server or NAS until you know whether the problem is the PC, the network, or the share itself.

Fix 1: Check reachability and the exact path first

Do this on the Windows 11 PC. No administrator rights are needed.

1. Try the share by its exact path in File Explorer. ``text title="Settings path" File Explorer > address bar > type the full network path to the share `` If the folder opens, the path is correct and the share is online. If it does not open, keep going.

2. Try the same share by IP address if you know it. ``text title="Settings path" File Explorer > address bar > type the IP address and share name `` If the IP address works but the name does not, the share is reachable and name resolution is the problem. If neither works, the other device may be offline, asleep, blocked by a firewall, or the share may be stopped.

3. Confirm the shared folder is actually online at the server or NAS. ``text title="Settings path" The server or NAS must be powered on, connected to the network, and sharing the folder `` If it is offline or asleep, Windows cannot reach it. If it is online but still unreachable, the problem is likely on the network path or on the server side.

Fix 2: Clear saved credentials that Windows keeps reusing

Do this on the Windows 11 PC. You may need administrator rights depending on how the account was saved.

1. Open Credential Manager. ``text title="Settings path" Control Panel > Credential Manager > Windows Credentials ``

2. Remove any saved entry for the server or NAS. ``text title="Settings path" Credential Manager > Windows Credentials > remove the saved credential for that host `` If Windows was using the wrong password or username, the repeated prompt should stop after you remove the saved entry. If the prompt continues, the account on the share may be expecting a different username format or the share permissions may still be wrong.

3. Connect again and enter the account the server or NAS expects. ``text title="Settings path" File Explorer > open the share again > enter the correct credentials `` If the share opens now, the problem was a stale credential. If it still fails, move on to the Windows sharing settings.

Fix 3: Check Windows 11 network discovery and password-protected sharing

Do this on the Windows 11 PC. Administrator rights may be needed.

1. Open the advanced sharing settings. ``text title="Settings path" Settings > Network & internet > Advanced network settings > Advanced sharing settings ``

2. Make sure network discovery is on for the network you are using. ``text title="Settings path" Advanced sharing settings > Network discovery > On `` If discovery is off, Windows may not find shared devices by name. If you can still reach the share by IP address, the share itself may be fine and only discovery is affected.

3. Check password-protected sharing. ``text title="Settings path" Advanced sharing settings > Password protected sharing `` If this is on, Windows expects a valid username and password for the share. If this is off, some shares may allow easier access, but mixed guest and authenticated access can still cause problems on newer Windows setups. If turning this setting changes the behavior, the issue was on the Windows access side, not the folder itself.

Fix 4: Review the server or NAS permissions if you get Access denied

Do this on the server, NAS, or the computer that hosts the share. Administrator rights are usually required there.

1. Open the share permissions for the folder. ``text title="Settings path" On the server or NAS, open the share settings for the folder you are trying to reach ``

2. Check that your account is allowed through both share permissions and folder permissions. ``text title="Settings path" Share permissions and folder or NTFS permissions must both allow the account `` If the share opens after this change, the problem was permissions on the server or NAS. If it still says access denied, the account you are using may not match the one that the share expects, or the share may be using a different permission set than you changed.

3. Use one consistent account for the share. ``text title="Settings path" Use the same username and password for the share, and update any saved Windows credentials after a password change `` If the account changes and Windows still tries the old one, access denied will keep coming back until the saved credential is updated.

Verify it worked

Open the share again from the Windows 11 PC.

The shared folder opens normally, without repeated password prompts and without a network path or access denied message.

If the folder opens by name and not just by IP address, name resolution is working again too. If the share works from one PC but not from this Windows 11 PC, the problem is still local to the PC and its saved settings. If it fails from every device, the problem is on the server, NAS, or network side.

Why this keeps happening again

This problem often returns for a few predictable reasons. Password changes are a common one: if the account on the server or NAS changes, Windows may keep trying the old credential until you remove it. Mixed guest and authenticated access is another: some shares allow anonymous access in one place but require a password in another, and newer Windows settings may block that mix.

SMB version mismatches can also cause trouble, especially with older NAS devices or very old file servers. If the device only supports older SMB behavior, Windows 11 may refuse the connection or fail in odd ways. Finally, sleep and firewall settings matter. A PC that sleeps too aggressively, or a firewall that blocks file sharing on a Private network, can make a share look broken even when the folder itself is fine.

Prevent it from coming back

If you want this to stay fixed, keep the server awake when it should be available, use one consistent account for the share, and avoid changing share names or passwords without updating the saved Windows credentials afterward. If you manage the server or NAS, keep the share settings and folder permissions aligned so Windows is not forced to guess which rule applies.

When you do change a password, check the saved Windows credential right away. That small step prevents most repeat prompts and saves you from chasing the same error again later.

Conclusion

If the share still fails after these checks, focus on the side that matches the error: reachability and naming for “network path not found,” permissions for “access denied,” and saved credentials for repeated prompts. The next best step is to test the same path from another device and compare what changes. That usually shows whether the problem is on your Windows 11 PC or on the server or NAS.