Fix STATUS_NETWORK_UNREACHABLE (0XC000023C) in 3 Steps

You're working away, trying to open that mapped drive or connect to a remote server, and boom — STATUS_NETWORK_UNREACHABLE. The full message reads "The remote network is not reachable by the transport". I've seen this error a hundred times on support forums, and it's usually not as scary as it looks. It just means Windows can't find a route to the target IP or hostname right now. Could be a dead VPN tunnel, a flaky Wi-Fi signal, or a DNS hiccup. Let's fix it step by step — stop when yours is gone.

Step 1: The 30-Second Fix — Check Your Connection

I know, checking if you're online sounds insultingly obvious. But when this error pops up, it's almost always because the network path changed under you. Here's what to check:

• Is your VPN connected? If yes, disconnect and reconnect. That alone clears 0XC000023C half the time.
• Are you on Wi-Fi? Walk closer to the router or switch to Ethernet if you can.
• Try pinging the target server. Open Command Prompt and run ping <server-ip>. If you get Request timed out, the network really is unreachable — move to Step 2.

One real-world scenario: you're in a coffee shop, and their guest Wi-Fi blocks certain ports. Your mapped drive to the office server fails with this exact error. Reconnecting to your phone's hotspot would prove it.

If ping works but the error persists, it's not a basic connectivity issue. Keep going.

Step 2: The 5-Minute Fix — Flush DNS and Reset Winsock

Sometimes the issue is a stale DNS entry or a corrupted network stack. Windows caches DNS aggressively, and after a VPN disconnect or router change, it can hold onto a dead route. Here's the fix that works for most people:

1. Open Command Prompt as Administrator.
2. Run these commands one at a time:

ipconfig /flushdns

ipconfig /registerdns

netsh winsock reset

netsh int ip reset

Then restart your computer — no skipping that part. The netsh winsock reset rebuilds the network stack, which clears weird socket states that trigger this error.

I've also seen this error pop up when Windows is using a wrong DNS server. If flushing doesn't work, check your DNS settings: set them to 8.8.8.8 and 8.8.4.4 (Google's public DNS) temporarily. Go to Control Panel > Network and Sharing Center > Change adapter settings, right-click your active adapter, choose Properties, select Internet Protocol Version 4 (TCP/IPv4), and set the DNS manually. This is a quick test — if the error disappears, your router's DNS is the culprit.

Step 3: The 15+ Minute Fix — Check Routing and Firewall

If you've gotten this far, the problem is deeper — likely a routing misconfiguration or a firewall rule blocking the connection. Let's dig in.

Check the Route Table

If you're using a VPN, Windows might have a route that's stuck or missing. Open Command Prompt as Administrator and run:

route print

Look for the destination you're trying to reach. If you see a route with 0.0.0.0 for your VPN interface, that means all traffic is going through the tunnel — which is fine if the VPN is up. But if the VPN is down and that route still exists, that's your problem. Delete it with:

route delete 0.0.0.0

Then reconnect your VPN or force a new route. Be careful — deleting routes without knowing what you're doing can kill your internet. If you're not comfortable, skip this and try the next bit.

Disable IPv6 Temporarily

Windows sometimes prefers IPv6, but many enterprise networks aren't actually reachable via IPv6. If your server is IPv4-only, this mismatch can throw 0XC000023C. Here's how to disable IPv6 on your adapter:

1. Open Control Panel > Network and Sharing Center &em; Change adapter settings.
2. Right-click your active connection, select Properties.
3. Uncheck Internet Protocol Version 6 (TCP/IPv6).
4. Click OK and restart the connection.

This is a common fix for users connecting to older Windows Server versions that don't have IPv6 configured properly.

Check Windows Firewall

Your own firewall can block outbound traffic if it's set to strict mode. Temporarily disable Windows Firewall for a test — don't forget to turn it back on:

1. Go to Windows Security > Firewall & network protection.
2. Click on each active network profile and toggle the firewall off.
3. Try the connection again.

If it works, the issue is a firewall rule. You'd then add a specific rule to allow traffic to that IP or port, rather than disabling the firewall permanently.

One More Thing: The Hosts File

If you're using a hostname rather than an IP, a bad entry in your hosts file can redirect you to a dead address. Open C:\Windows\System32\drivers\etc\hosts in Notepad (as Administrator) and check for any lines pointing to your target server with an old IP. Remove or fix them.

Pro tip: This error also shows up when you're mapping a drive with a UNC path like \\server\share and Windows resolves the server name to an unreachable IP. Try using the IP directly: \\192.168.1.10\share. If that works, it's a DNS naming issue, not a connectivity one.

When to Call Your IT Department

After all this, if you still see 0XC000023C, the problem might be on the server side — maybe the remote network is genuinely down or your account lacks permission to route there. Check with your network admin whether the target subnet is reachable from your current location.

That's it. Start with the quick steps, and you'll likely dodge the deep-dive. Good luck — you've got this.