A server being 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.
This error occurs when Guest Interaction Proxy ( vSphere | Hyper-V ) fails to connect to the Guest OS of a server 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 is unable to 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$
The key to troubleshooting this issue is to identify what environmental issue is preventing the Guest Interaction Proxy from connecting to the $admin share of the server being processed.
To test connectivity to the $admin share rapidly without having to run the job, use the "Test Now" button on the Guest Processing tab of the job to launch the Guest Credentials Test.
The following is a list of common troubleshooting steps.
Note: 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 tools 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.
If Veeam Backup & Replication will be operating in a vSphere environment where the Veeam server and it's components will never have direct network connectivity to the Guest OS of the Virtual Machines, it is possible to force VIX to be attempted first.
Create the following registry value on the Veeam Backup & Replication server:
For Veeam 9.x and later the value should also be created on the Guest Interaction Proxy
(note that the path is different)
Restarting of services in not required.
For more information on VIX permissions, see http://www.veeam.com/kb1788