Verify Network Profile and Discovery Settings
Windows categorizes networks into Public, Private, and Domain profiles, each with different security defaults. If your current network is set to "Public," Windows will hide the computer from other devices on the local area network (LAN) to protect it from unauthorized access. This is the most common cause for the "not accessible" error when both machines are on the same Wi-Fi or Ethernet segment. To change the network profile to Private, navigate toSettings > Network & Internet. Select Wi-Fi or Ethernet depending on your connection type. Click on the properties of the connected network and change the Network profile type from Public to Private. Once changed, ensure that "Network discovery" is turned on. This allows your PC to see other devices and allows others to see yours. Without this setting, the target machine effectively disappears from the network neighborhood, leading to immediate connection failures.
Check Advanced Sharing Configuration
Even with the correct network profile, the underlying sharing protocols must be explicitly enabled. Open the Control Panel and go toNetwork and Internet > Network and Sharing Center. From there, click on Change advanced sharing settings in the left pane. Under the Private network profile section, verify that Turn on network discovery and Turn on file and printer sharing are selected. Additionally, ensure that Turn on automatic setup of network connected devices is checked if you are adding new hardware to the mix.
It is also critical to check the All Networks section at the bottom of this window. Here, you should look for Turn off password protected sharing. If this option is enabled, any user attempting to connect must provide valid credentials. If you intend to allow anonymous or guest access for internal troubleshooting, you can disable password protection. However, note that this reduces security significantly. For most corporate or secure home environments, keeping password protection on is recommended, but you must then ensure the connecting user has a matching account on the target machine.
Validate User Permissions and Credentials
If network settings are correct, the issue often lies in authentication. The error message explicitly mentions permission issues. To fix this, you need to ensure that the user account on the target machine has the necessary rights. First, create a standard user account on the target Windows machine if one does not exist, or use an existing administrator account. Ensure this account has a strong password, as empty passwords are often rejected by modern SMB implementations for security reasons. On the target machine, right-click the folder you wish to share and selectProperties. Go to the Sharing tab and click Advanced Sharing. Check Share this folder and click Permissions. By default, only Everyone might have Read access. Add the specific user account you plan to use for connection and grant it Full Control or Change permissions depending on your needs. Do not forget to apply these changes.
Next, switch to the Security tab in the same Properties window. Here, ensure the same user account is listed under Group or user names. If it is missing, click Edit > Add and add the user again. Grant appropriate NTFS permissions here as well. Even if Share permissions allow access, restrictive NTFS permissions on the Security tab will block the connection, resulting in the exact error you are seeing.
Restart Relevant Services
Sometimes, the Windows services responsible for handling network requests become unresponsive or stuck. Restarting these services can clear temporary glitches. PressWin + R, type services.msc, and hit Enter. Locate the following services:
- Function Discovery Provider Host
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
- TCP/IP NetBIOS Helper
Restart. Ensure their Startup Type is set to Automatic. After restarting, try accessing the computer name again via the Run dialog (Win + R) using \\.
For deeper connectivity issues, consider reviewing how your network infrastructure handles traffic. If you are using complex routing or bridging setups, ensure those configurations do not interfere with local broadcast discovery. You might find value in understanding broader network bridge configurations, such as those discussed in Setting Up a Permanent Network Bridge Between Two PCs on Windows 11, which can help isolate whether the issue is within the OS or the physical/virtual network layer.
Frequently Asked Questions
Why does the error persist after enabling file sharing?
The error often persists because NTFS permissions on the target folder override Share permissions. You must configure both the Advanced Sharing permissions and the Security tab permissions to include the user account attempting to connect. If either layer denies access, the connection will fail.Can I connect without a password?
Yes, but you must disable password-protected sharing in the Advanced Sharing Settings. Be aware that this allows anyone on the local network to access shared resources without authentication, which poses a significant security risk in public or semi-public networks.What if I can ping the computer but cannot access shares?
Ping uses ICMP protocol, while file sharing uses SMB (TCP ports 445 and 139). If you can ping but not share, your firewall is likely allowing ICMP but blocking SMB traffic. Ensure that "File and Printer Sharing" is allowed through Windows Defender Firewall for both Private and Public profiles.Does changing the IP address resolve this error?
No, changing the IP address does not resolve permission errors. It only helps if there is an IP conflict causing connectivity drops. The "not accessible" error is strictly related to authentication, sharing configuration, or service availability, not the IP assignment itself.How do I reset network settings to default?
If previous fixes fail, you can reset network components by going toSettings > Network & Internet > Status and clicking Network reset. This reinstalls network adapters and resets all networking components to their default settings, requiring a reboot afterward.