STATUS_NETWORK_OPEN_RESTRICTION 0XC0000201 fix

The 30-second fix: check your network profile

I've seen this error more times than I can count. It usually shows up when you're trying to access a network share or a remote computer and Windows just says no. The system event log might show 0XC0000201 with the description STATUS_NETWORK_OPEN_RESTRICTION.

First thing to check — your network profile. Windows 10 and 11 love to set your network to Public when it should be Private. Public profile blocks a lot of network traffic by default. That includes file sharing, printer sharing, and remote access.

1. Click the network icon in the system tray (bottom right).
2. Select Network & Internet settings.
3. Click Properties under your active network.
4. Look for Network profile. If it says Public, switch it to Private.

That's it. 30 seconds, maybe less. Had a client last month who couldn't access his file server across the office. His Wi-Fi had switched to Public after a Windows update. Changed it to Private, problem gone.

If that didn't fix it — move to step 2.

The 5-minute fix: Windows Defender Firewall

If the network profile is already set to Private, the next suspect is Windows Defender Firewall. It's got a rule that can block inbound connections even on a Private network. That rule is called File and Printer Sharing (Echo Request - ICMPv4-In) — but there's a bigger one: File and Printer Sharing (SMB-In).

Here's how to check and enable it:

1. Open Control Panel (yes, the old one).
2. Go to Windows Defender Firewall.
3. Click Advanced settings on the left.
4. In the left pane, click Inbound Rules.
5. Find rules named File and Printer Sharing (SMB-In). There might be two — one for Domain, one for Private.
6. Right-click each one and make sure they're Enabled.
7. Also check File and Printer Sharing (NB-Session-In) and File and Printer Sharing (LLMNR-UDP-In) — enable those too.

I once spent 45 minutes on a call with a guy in Ohio who couldn't access his NAS drive. Turned out a security update had disabled all File and Printer Sharing rules. Enabled them, boom, it worked.

If you're still stuck after this, we go deeper.

The 15+ minute fix: Group Policy or registry tweak

This one's for network admins or anyone on a work computer. The error might come from a Group Policy setting that restricts network access. Specifically, the policy Network access: Do not allow anonymous enumeration of SAM accounts and shares can cause this if it's misconfigured.

Here's how to check it:

1. Press Win + R, type gpedit.msc, hit Enter. (If you're on Windows Home, skip this — you don't have it. Try the registry method below.)
2. Go to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
3. Find Network access: Do not allow anonymous enumeration of SAM accounts and shares.
4. Double-click it and set it to Disabled.
5. Also check Network access: Restrict anonymous access to Named Pipes and Shares — set it to Disabled as well.

If you don't have Group Policy Editor, you can do the same via registry:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v restrictanonymous /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v restrictanonymoussam /t REG_DWORD /d 0 /f

Then restart your computer.

One more thing — some third-party firewalls like Norton or McAfee can block SMB traffic even when Windows Firewall is off. Check your third-party security suite and temporarily disable it to test.

If none of that works, you might be dealing with a corrupted network stack. Run these commands from an admin command prompt — they've saved me more than once:

netsh int ip reset
netsh winsock reset
ipconfig /flushdns

Reboot after. I've seen this fix weird network errors that nothing else touched.

That's it. Start with the profile, then firewall, then policy. You'll likely be done by step 1 or 2.