Operational Defect Database
BugZero found this defect 4618 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb1230
Win32 error: The network path was not found. Code 53
Last update date:
8/18/2023
Affected products:
Veeam Backup & Replication
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
A server processed by a job fails with the following error: Error: Failed to connect to guest agent. Errors: 'Cannot connect to the host's administrative share. Host: [<hostname>]. Account: [...]. Win32 error:The network path was not found. Code: 53 Cannot connect to the host's administrative share. Host: [<ip>]. Account: [...]. Win32 error:The network path was not found. Code: 53 Note: This applies to both VMware and Hyper-V environments.
Cause
This error occurs when Guest Interaction Proxy ( vSphere | Hyper-V ) fails to connect to the Guest OS while attempting to perform Application-Aware Processing ( vSphere | Hyper-V ).The Guest Interaction Proxy will attempt to connect via the hostname first and may fail if it cannot resolve the IP address. If the Guest Interaction Proxy Fails to connect to the guest Admin Share by hostname, it will try to use the IP reported to the Hypervisor.The Win32 error, "The network path was not found," is received by Guest Interaction Proxy from the OS when it attempts to connect to \\<guest-hostname\ip>\admin$
Solution
The key to troubleshooting this issue is identifying the environmental problem preventing the Guest Interaction Proxy from connecting to the admin$ share of the server being processed. Tip: To test connectivity to the admin$ share rapidly without running the job, use the "Test Now" button on the Guest Processing tab of the job to launch the Guest Credentials Test. Troubleshooting: Test connectivity to the admin$ share (for example, \\<hostname>\admin$) from the Guest Interaction Proxy with the same credentials specified in the Guest Process section of the job.Test from multiple machines, including the Veeam Backup & Replication server and other Guest Interaction Proxies to isolate if there is a connectivity issue specific to one of the Guest Interaction Proxies Make sure the Guest Interaction Proxy can access the VM ping the hostname and IP Test connectivity to port 445
More Information
Networkless Guest Processing in vSphere Environments When working with vSphere environments, it is possible for Veeam Backup & Replication to use a network-less connection method (VIX) if direct communication fails. This method uses VMware VIX/vSphere Web Services to push the runtime components into the machine and manage them. If the VM being protected is in a DMZ or other network-isolated configuration, it may not be possible to get RPC working and require that connectivity via VIX be investigated. Reference: https://www.veeam.com/kb1788.
