Resolve inaccessible shared folders on Windows 11 by verifying network profile settings, ensuring SMB 2.0 or higher is enabled, and checking advanced sharing permissions. Most connectivity failures stem from the network being classified as "Public" rather than "Private," which blocks discovery protocols, or from misconfigured NTFS and share-level permissions that prevent authentication.
Verify Network Profile Classification
Windows 11 strictly enforces security boundaries based on whether a network adapter is identified as Private or Public. If your home network is set to Public, Windows Firewall automatically disables file and printer sharing features to protect your device from unauthorized access. This is the most common reason why a shared folder disappears from the network view of other devices. To correct this, navigate to Settings > Network & internet > Wi-Fi (or Ethernet). Click on the properties of your currently connected network. Under the Network profile type section, select Private. This action instructs Windows to trust devices on this local segment, allowing them to discover your PC and access shared resources. Without this change, no amount of permission tweaking will allow remote access because the underlying firewall rules remain in a blocking state for all inbound sharing traffic.Enable Advanced Sharing Settings
Even with a Private network profile, specific sharing protocols must be explicitly allowed through the Control Panel interface. Microsoft has moved many of these legacy settings into a dedicated control panel applet rather than the modern Settings app. Open the Start menu, type Control Panel, and launch it. Navigate to Network and Internet > Network and Sharing Center. On the left sidebar, click Change advanced sharing settings. Expand the Private network section and ensure that Turn on network discovery and Turn on file and printer sharing are both selected. Crucially, under Password protected sharing, you must decide whether to require a password for every connection. For a secure home environment, keeping this enabled is recommended, but it requires that the accessing user account exists on the host machine with a known password. If you disable this, any device on the network can access shares without credentials, which poses a significant security risk. Save changes after adjusting these toggles.Configure Folder Permissions Correctly
A folder may be shared globally, but access is ultimately governed by two layers of permissions: Share permissions and NTFS (file system) permissions. The most restrictive setting between these two layers always applies. If you grant "Read" at the share level but "Full Control" at the NTFS level, users will only see read-only files. Conversely, if Share permissions allow Full Control but NTFS permissions restrict access to "Read," the user cannot modify files. Right-click the target folder and select Properties. Go to the Sharing tab and click Advanced Sharing. Ensure Share this folder is checked. Click Permissions here to define who can access the share over the network. Add the specific user accounts or groups (like "Everyone" for basic home use, though less secure) and assign appropriate rights. Next, switch to the Security tab. Verify that the same users or groups listed in the Share permissions exist here. If a user is missing from the Security tab, they will be denied access regardless of Share settings. Click Edit to add necessary accounts and assign their base NTFS permissions. It is best practice to mirror the Share and Security permissions to avoid confusion during troubleshooting.Check SMB Protocol Versions
While older guides often suggest enabling SMB 1.0 for compatibility, this protocol is deprecated, insecure, and vulnerable to ransomware attacks like WannaCry. Windows 11 relies on SMB 2.0 and SMB 3.0 for all standard file sharing operations. These protocols are enabled by default and should never be disabled. Attempting to force SMB 1.0 via PowerShell or registry edits introduces severe vulnerabilities and is not a valid solution for connectivity issues. If you suspect protocol negotiation issues, verify that the server and client are communicating correctly using modern standards. You can check the status of SMB services by opening PowerShell as Administrator and runningGet-SmbServerConfiguration | Select EnableSMB2Protocol. The output should return True. If it returns False, enable it with Set-SmbServerConfiguration -EnableSMB2Protocol $true and restart the Server service. Do not touch SMB 1.0 settings unless you are connecting to extremely legacy hardware that predates Windows XP, which is rare in modern home networks.
Validate Firewall and Service Status
If the above steps fail, the Windows Firewall may still be blocking specific ports associated with file sharing. SMB uses TCP port 445 for direct hosting. Open Windows Defender Firewall with Advanced Security and ensure that inbound rules for File and Printer Sharing (SMB-In) are active for the Private profile. Additionally, confirm that the following services are running: Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host. These services handle the discovery of network devices and are essential for seeing shared folders in the Network neighborhood. Restarting these services can often resolve transient discovery glitches. For more details on configuring LAN file sharing across Windows versions, see our guide on Enable WIN10/11 LAN File Sharing.Frequently Asked Questions
Why can I see the computer but not the shared folder?
This usually indicates a mismatch between Share permissions and NTFS permissions. Check the Security tab in the folder properties to ensure the user account has at least Read access at the file system level. Even if Share permissions allow full access, restrictive NTFS settings will block entry.Does disabling password protected sharing make my network unsafe?
Yes, it allows any device on the local network to access your shared folders without authentication. While convenient for isolated home labs, it exposes your data to any neighbor or guest connected to the same Wi-Fi. Use Guest accounts with limited privileges if you must disable passwords.How do I reset network sharing settings to default?
You can reset these settings by going to Settings > Network & internet > Advanced network settings and selecting Network reset. This reinstalls network adapters and restores all networking components to their default configuration, including firewall rules for sharing. Note that this will disconnect you from Wi-Fi temporarily.What is the difference between SMB 1.0 and SMB 3.0?
SMB 1.0 is an outdated protocol with known security flaws and poor performance, while SMB 3.0 offers encryption, faster speeds, and improved reliability. Windows 11 supports SMB 3.0 natively and should never have SMB 1.0 enabled unless connecting to very old non-Windows devices.Can I share folders between Windows 11 and macOS?
Yes, but macOS primarily uses AFP or SMB protocols. Ensure your Windows 11 PC has SMB 2.0/3.0 enabled, which is default. On macOS, open Finder, press Command+K, and entersmb://[Windows-PC-IP]. You may need to create a specific user account on Windows with a simple password to facilitate easier cross-platform authentication.