ERROR_HOST_UNREACHABLE 0X000004D0: Fix Network Location Error

Fix #1: Disable IPv6 on your network adapter

I know this error is infuriating—you're staring at a path that worked yesterday, and now Windows says the host can't be reached. The number one culprit I've seen in six years of help desk work is IPv6. Windows prioritizes IPv6 when both stacks are available, and if your router or the target device has flaky IPv6 support, you get 0X000004D0 even though IPv4 would work fine.

This tripped me up the first time too. A user on Windows 10 22H2 couldn't reach a NAS drive. IPv4 ping worked, but the SMB share failed. Disabling IPv6 fixed it instantly.

Here's how to do it:

1. Press Win + R, type ncpa.cpl, hit Enter.
2. Right-click your active adapter (usually Ethernet or Wi-Fi) and select Properties.
3. Uncheck Internet Protocol Version 6 (TCP/IPv6).
4. Click OK, then reboot.

Don't worry about breaking anything—most networks run perfectly on IPv4. If you're on a corporate network that uses IPv6 internally, check with your admin first. But for home or small office, this is the real fix.

Fix #2: Allow the connection in Windows Defender Firewall

If disabling IPv6 didn't do it, the next suspect is the firewall silently dropping the connection. This happens when you're trying to access a shared folder or a network printer, and Windows Firewall has the File and Printer Sharing rule turned off. The error pops up as 0X000004D0 because the remote host responds to pings but not to the actual file-sharing traffic.

I've seen this on fresh Windows 11 installs—the firewall rules get reset, and suddenly your shared drive is gone.

Let's check and fix it:

1. Open Windows Security from the Start menu.
2. Click Firewall & network protection.
3. Click Allow an app through firewall.
4. Click Change settings (you'll need admin rights).
5. Find File and Printer Sharing in the list. Make sure both Private and Public checkboxes are ticked.
6. If it's not there, click Allow another app and browse to C:\Windows\System32\svchost.exe—but that's rare.

Also, if you're on a laptop that switches between networks, double-check that your current network is marked as Private. Windows treats Public networks as hostile and blocks file sharing by default.

Fix #3: Reset the network stack and clear the ARP cache

This one is the sneaky fix. Sometimes the network stack gets corrupted—stale ARP entries, broken routing tables, or a hung TCP/IP driver. The error shows up when you try to access a host, but the local machine can't map the IP to a MAC address. This happens after a VPN disconnect or when your computer wakes from sleep and the network hasn't fully reinitialized.

The quickest way to clear the mess is a full network reset. Run these commands in an elevated Command Prompt (right-click Command Prompt and choose Run as administrator):

netsh int ip reset
netsh winsock reset
ipconfig /flushdns
arp -d *
route -f

Then reboot. Yes, it's a lot of commands, but each one targets a different layer. The arp -d * clears the ARP cache—that's the one that directly fixes the “host unreachable” symptom. The others clean up lingering TCP/IP and Winsock issues.

If you're in a hurry, just the arp -d * and a reboot might be enough. But run the whole batch to avoid a second trip.

Quick-reference summary

Try them in this order. Nine times out of ten, you'll fix 0X000004D0 within ten minutes. If none of these work, you're looking at a router or remote host issue—check if the remote device is actually online by pinging it, and verify with the network admin.