Another machine cannot open a shared folder in Windows 11 because of misconfigured network discovery, incorrect sharing permissions, or disabled SMB protocols. This guide resolves connectivity issues by verifying Advanced Sharing Settings, ensuring the correct user accounts have access, and checking firewall rules that block local network traffic.
Verify Network Discovery and File Sharing Settings
The most common cause for this issue is that Windows 11 has network discovery turned off for the current profile. When you connect to a new network, Windows often defaults to "Public" mode, which hides your PC from other devices and blocks file access. You must switch to "Private" or "Home/Work" mode and enable specific sharing features.
Navigate to
Settings > Network & internet > Ethernet (or Wi-Fi) and ensure the network profile is set to Private. Next, open the Control Panel and go to
Network and Internet > Network and Sharing Center > Change advanced sharing settings. Under the Private section, make sure both
Turn on network discovery and
Turn on file and printer sharing are selected. Crucially, expand the
All networks section at the bottom. Here, you must disable password protected sharing if you want anonymous access, or keep it enabled but ensure the remote machine uses a valid account. If you choose to keep password protection on, the username and password used on the remote machine must match an account on the host PC exactly.
Check Folder Permissions and Share Properties
Even with network settings correct, specific folder permissions can prevent access. Windows distinguishes between NTFS permissions (security tab) and Share permissions (sharing tab). Both must allow the intended users to read or write data. Right-click the target folder and select
Properties, then go to the
Sharing tab. Click
Advanced Sharing and check
Share this folder. Click
Permissions and ensure the group
Everyone (or specific users) has at least Read access. If you need write access, grant Change or Full Control here.
Next, verify the security layer. Go to the
Security tab in the same Properties window. Ensure the same users or groups listed in the Sharing tab exist here. If they are missing, add them. The Security tab controls the underlying file system access, while the Sharing tab controls network access. A common error occurs when the Security tab restricts access even if the Sharing tab allows it. For example, if
Everyone is not listed in the Security tab, no one can access the folder over the network, regardless of share settings.
Ensure SMB Protocol Support is Enabled
Windows uses the Server Message Block (SMB) protocol for file sharing. In recent updates, Microsoft has deprecated SMBv1 due to security vulnerabilities like WannaCry, but some older devices or specific configurations may still rely on it or require SMBv2/v3 to be active. By default, Windows 11 enables SMBv2 and v3, but sometimes these features get disabled during system optimization or clean installs.
Open PowerShell as Administrator and run
Get-SmbServerConfiguration | Select EnableSMB2Protocol. If this returns
false, your sharing will fail. To fix this, run:
Set-SmbServerConfiguration -EnableSMB2Protocol $true -Force
If you are connecting to very old legacy systems, you might need SMBv1, but this is strongly discouraged. Instead, ensure that the
File and Printer Sharing exception is allowed in Windows Defender Firewall. Go to
Control Panel > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall. Ensure both Private and Public checkboxes are checked for File and Printer Sharing.
Test Connectivity and Resolve Name Resolution Issues
Sometimes the issue is not permissions but name resolution. The remote machine might not be able to resolve the host's computer name to an IP address. Try accessing the share using the IP address directly instead of the hostname. Open the command prompt on the host machine and run
ipconfig to find the IPv4 address. On the remote machine, press
Win + R and type
\\\FolderName. If this works, the problem is DNS or NetBIOS name resolution.
You can also try pinging the host from the remote machine to verify basic connectivity. If ping fails, there may be a deeper network isolation issue, such as AP Isolation being enabled on the router, which prevents devices on the same Wi-Fi from communicating. If you are experiencing intermittent connection drops while trying to troubleshoot, you might find our guide on
How to Troubleshoot Windows 11 Laptop Connection to Specific WiFi Network without Internet Access helpful for diagnosing broader network stability issues.
For more complex permission inheritance problems, refer to
Fixing SFCDISM Fail Issues in Windows 11 Without Uninstalling Programs to understand how system integrity tools might affect file system operations.
Frequently Asked Questions
Why can I see the shared folder but get "Access Denied"?
This usually means the network path is found, but your credentials are rejected. Ensure the remote machine is logging in with a username and password that exists on the host PC. If password protected sharing is disabled, ensure no password is set for the user account on the host.
Does disabling password protected sharing make my PC insecure?
Yes, it allows anyone on the local network to access shared folders without authentication. It is safer to keep it enabled and create a dedicated user account with limited privileges for sharing purposes rather than exposing your main admin account.
What if the remote machine says the network path was not found?
This indicates a connectivity or name resolution failure. Try using the IP address instead of the computer name. If it works via IP, configure static DNS entries or ensure NetBIOS over TCP/IP is enabled in your network adapter properties.
Can antivirus software block folder sharing?
Third-party firewalls or aggressive antivirus suites can block inbound connections on ports 445 and 139. Check your antivirus logs for blocked applications and add
svchost.exe or the specific sharing service to the exclusion list.
Why does sharing work on Wi-Fi but not Ethernet?
This often happens if the Ethernet adapter is set to a Public network profile while Wi-Fi is Private. Ensure both adapters are configured under the same network profile type in the Network & Internet settings to maintain consistent sharing rules.