Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | The network location cannot be reached (Error 0x800704B3) | Event Viewer > Windows Logs > System | -> Event ID 1129 |
| Affected build range | Windows 10 / Windows 11 | Microsoft Docs | |
| Registry key involved | HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents | Registry Editor | -> Temporarily disable IPv6 preference |
| Relevant service/endpoint URL | https://<serverIP>:445 | Test-NetConnection cmdlet output | |
| Log line signature | Event ID 1129 with error code 0x800704B3 | Event Viewer > Windows Logs > System |
Log Files to Check
C:\Windows\System32\winevt\Logs\System.evtxC:\Windows\System32\winevt\Logs\Security.evtx
What This Error Actually Means
The error code 0x800704B3, often referred to as "ERROR_NETWORK_UNREACHABLE," is raised by the Windows networking stack when it fails to establish a network path to a specified resource such as a UNC path (\\server\share), a mapped drive, or a network printer. This error occurs after DNS resolution has succeeded but before establishing an SMB session or NetBIOS connection. The underlying issue can be related to routing problems, firewall rules blocking necessary ports, or misconfigurations in VLAN settings that prevent the client from reaching the server's subnet.Affected Versions and Scope
This error is prevalent across all builds of Windows 10 and Windows 11 but does not affect earlier versions such as Windows 7. It can occur in various tenant configurations, including corporate environments with strict network segmentation policies or complex routing setups involving VLANs and subnets.Where To Look First: Logs and Event IDs
To diagnose this issue, start by examining the System event log located atC:\Windows\System32\winevt\Logs\System.evtx. You should look for entries with Event ID 1129 that include the error code 0x800704B3. Additionally, check the Security log at C:\Windows\System32\winevt\Logs\Security.evtx for any related access denials or policy enforcement events.
Root Causes
Routing Gap or Firewall Blocking SMB/NetBIOS
When a client device cannot reach a server due to routing issues, the network path is not established at Layer 3. This can be caused by missing routes on either the client's machine or intermediate routers between the client and the server. Additionally, firewalls might block necessary ports (TCP 445 for SMB and UDP/TCP 137-139 for NetBIOS).Split-Tunneling Configuration Issues with VPN
In environments where clients use a split-tunneling configuration via a corporate or third-party VPN, the routing table on the client machine might not include routes to the server's subnet through the tunnel. This results in network unreachable errors when attempting to access resources that should be routed through the tunnel.Network Interface Issues
If the server-side network interface is down or if NIC teaming has failed over incorrectly, clients may attempt to connect using an incorrect IP address or route, leading to 0x800704B3 errors. This can also occur when a client roams between wireless access points (APs) with different VLAN assignments.Fix Procedure
- Confirm Layer 3 Reachability: Use the command line to ping the server's IP address:
ping. If this fails, proceed to check routing and firewall rules. - Trace Route: Run a trace route to identify where packets stop forwarding:
tracert. - Test SMB Port Directly: Use PowerShell's Test-NetConnection cmdlet to check if the SMB port is reachable:
Test-NetConnection -ComputerName. If this fails, it indicates a firewall issue.-Port 445 - Check Routing Table: View the client's routing table using
route printand ensure there is an entry for the server's subnet. If missing, add a route manually:route add -p.mask - Test IPv6: Check if the issue persists with IPv6 by disabling it temporarily or removing AAAA records for the affected server.
- For Split-Tunneling Issues: Ensure that the VPN client's routing table includes routes to all necessary subnets after connecting. Adjust split-tunnel settings in the client configuration if needed.
Be cautious when modifying firewall rules or adding new routes, as incorrect changes can disrupt network connectivity for other services.
Error Code Variants
| Code | Description |
|---|---|
| 0x800704B3 | The network location cannot be reached (Layer 3 routing issue) |
| 0x800704CF | The specified network name is no longer available (DNS resolution failure) |
| 0x80072EE7 | No connection could be made because the target machine actively refused it (Port blocked by firewall) |
Verification
After applying fixes, verify that the network location can now be reached. Useping to confirm reachability and Test-NetConnection -ComputerName -Port 445 to ensure SMB is accessible. Open File Explorer and browse \\server\share to confirm that the issue has been resolved.
Prevention
To prevent recurrence of this error, implement network policies that enforce consistent routing configurations across all VLANs and subnets. Ensure that firewall rules are properly configured to allow necessary traffic without blocking critical ports like TCP 445 for SMB. Additionally, configure wireless access points (APs) with consistent VLAN assignments to avoid issues when clients roam between different APs.
Use PowerShell's
This guide provides a comprehensive approach to diagnosing and resolving the 0x800704B3 error in Windows environments, ensuring that network connectivity issues are addressed effectively.Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 cmdlet for quick access to recent device management events.