Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x800704CF | ConfigMgr client logs | -> ERROR_NETWORK_UNREACHABLE |
| Affected build range | SCCM/ConfigMgr | Product documentation | |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Scripts | Registry Editor | -> Client settings |
| Relevant service/endpoint URL | https://<MP_FQDN>/SMS_<GUID>/ccm_client/ | ConfigMgr console | -> Management point endpoint |
| Log line signature | Network is unreachable | UpdatesDeployment.log, CcmExec.log |
Log Files to Check
C:\Windows\CCM\Logs\UpdatesDeployment.logC:\Windows\CCM\Logs\CcmExec.log
What This Error Actually Means
The error code 0x800704CF, which translates to "ERROR_NETWORK_UNREACHABLE," is raised when the Microsoft Configuration Manager (SCCM/ConfigMgr) client fails to establish a connection with its management point or other necessary endpoints such as distribution points or software update points. This error typically occurs during software distribution, software updates, or OS deployment tasks where network communication between the ConfigMgr client and server components is essential. The component that raises this error is primarily the Configuration Manager client on the endpoint device, which attempts to communicate with the management point (MP) over HTTP/HTTPS protocols using standard ports 80 and 443. If the MP or other required endpoints are unreachable due to network issues, firewall rules, or misconfiguration, the ConfigMgr client logs this error in its local log files.Affected Versions and Scope
This error is relevant across all builds of Microsoft Configuration Manager (SCCM/ConfigMgr). It impacts any environment where software distribution, updates, or OS deployment tasks are managed through SCCM. The error does not apply to standalone systems without a ConfigMgr client installed or environments using alternative management tools like Intune for Windows device management.Where To Look First: Logs and Event IDs
To diagnose the root cause of 0x800704CF, start by examining specific log files on the affected clients. The primary logs to review are:C:\Windows\CCM\Logs\UpdatesDeployment.log- Look for entries mentioning "Network is unreachable" or the exact error string0x800704CF.C:\Windows\CCM\Logs\CcmExec.log- This log captures client-side operations and may include details about failed network connections.C:\Windows\CCM\Logs\PolicyAgent.log- Useful for identifying issues with communication between the ConfigMgr client and management point.C:\Windows\CCM\Logs\WUAHandler.log- Contains logs related to Windows Update Agent errors, which can be relevant if software updates are failing.- IIS logs on distribution points:
C:\inetpub\logs\LogFiles\W3SVC1- These logs may show HTTP 404 or connection refused messages from clients trying to reach the MP or DP.
- Error ID:
8267- This event is logged when a client fails to connect to its management point due to network issues. - Error ID:
1054- Indicates that the ConfigMgr client cannot reach the software update point (SUP).
Root Causes
This section outlines several distinct causes of 0x800704CF, each with specific diagnostic steps to differentiate them:DNS Resolution Issues
When DNS resolution fails for the management point's fully qualified domain name (FQDN), clients cannot establish a connection. Check the client’s DNS configuration and ensure that the FQDN of the MP is correctly resolved.Firewall or Network Policy Blocking Communication
Network policies, including firewalls, can block necessary traffic between ConfigMgr clients and servers on ports 80 and 443. Verify firewall rules to allow communication through these ports for both inbound and outbound connections from client machines.Incorrect Boundary Group Assignment
Clients must be assigned to a boundary group that includes the management point or distribution point responsible for their subnet. Incorrect assignments can lead to unreachable endpoints. Review the hierarchy configuration in the ConfigMgr console underAdministration > Hierarchy Configuration > Boundaries.
Detailed Diagnostic Steps:
To distinguish between these causes, start by confirming DNS resolution using tools like nslookup or ping from affected clients against the MP FQDN. Next, review firewall rules and network policies for any blocks on standard ports used by ConfigMgr. Finally, check boundary group assignments in the ConfigMgr console to ensure proper coverage of client subnets.Fix Procedure
Follow these steps to resolve 0x800704CF:- Verify DNS Resolution: Use
nslookuporpingfrom an affected client machine to check if the management point's FQDN resolves correctly. Example:nslookup mp.fqdn.com. - Check Firewall Rules: Ensure that firewall rules allow traffic on ports 80 and 443 for both inbound and outbound connections from clients to the MP, DP, and SUP.
- Review Boundary Group Assignments: Navigate to
Administration > Hierarchy Configuration > Boundariesin the ConfigMgr console. Ensure that each client's IP address falls within a boundary group assigned to its management point or distribution point. - Run CCM Client Repair: Execute
ccmrepair.exeon affected clients to re-register them with their management points and resolve any local configuration issues. - Update Boundary Group Memberships: If necessary, modify boundary group memberships in the ConfigMgr console to ensure full coverage of client subnets. Use PowerShell cmdlets like
Set-CMBoundaryGroupfor bulk updates if needed. - Check Software Update Point Connectivity: Verify that the software update point (SUP) can reach its upstream WSUS server and that the SUP is correctly configured in the ConfigMgr console under
Administration > Site Configuration > Sites > [Your Site] > Components.
Error Code Variants
| Error Code | Description |
|---|---|
0x800704CF | ERROR_NETWORK_UNREACHABLE - Network path was not found or network location cannot be reached. |
0x80072EFD | ERROR_INTERNET_TIMEOUT - The request timed out because the server did not respond within the specified time period. |
0x800704B3 | ERROR_NOACCESS - No access to the given file or directory. |
Verification
After applying fixes, verify that the issue is resolved by checking log files for successful operations and no recurrence of 0x800704CF errors. Look for entries inC:\Windows\CCM\Logs\UpdatesDeployment.log indicating a successful connection to the management point or distribution point.
Use PowerShell cmdlets like:
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 | Where-Object { $_.Id -eq 8267 }
to confirm that event ID 8267 no longer appears in the logs.
Prevention
To prevent recurrence of this issue, implement a baseline configuration for network policies and firewall rules that explicitly allow ConfigMgr client traffic on necessary ports. Additionally, regularly review boundary group assignments to ensure they remain up-to-date with changes in subnet configurations or infrastructure updates.
Warning: Modifying registry keys such as
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\Scripts can affect system behavior and should be done cautiously.
A quick diagnostic shortcut is to use the ConfigMgr client's built-in network test feature, accessible via
ccmexec /testnetwork, which performs connectivity checks against management points and other endpoints.