Console Error - Failed to connect to Veeam Backup & Replication Server

Challenge

When attempting to connect to the Veeam Backup & Replication server using the console the connection fails with the error:

Failed to connect to the Veeam Backup & Replication server:
No connection could be made because the target machine actively refused it <IP>:9392




 

Cause

There are multiple causes for this failure to connect, the following is a list of the most common causes:
 
1. The server the console is installed on cannot reach the Veeam Backup & Replication server due to network limitation.
2. The server the console is installed on cannot resolve the hostname or FQDN of the Veeam Backup & Replication server entered.
3. A firewall is preventing communication between the server where the console is being run and the Veeam Backup & Replication server.
4. On the Veeam Backup & Replication server the Veeam Backup Service is not running.
 
There may be other causes, please contact Veeam Technical Support if you find a cause not listed.

Solution

Connectivity/DNS
From the server where the console is installed attempt to ping the IP/Hostname/FQDN of the Veeam Backup & Replication server specified when using the Veeam Backup & Replication console. If unable to ping the Veeam Backup & Replication server, please resolve the network level issue.
 
Firewall
Please check all firewalls that exist between the server where the Veeam Backup & Replication console installed and the Veeam Backup & Replication server.
 
A tool such as PortQry can be used to test if port 9392 can be reached on the Veeam Backup & Replication server from the console server. https://www.microsoft.com/en-us/download/confirmation.aspx?id=17148
 
Veeam Backup Service
Connect to the Veeam Backup & Replication server and make sure that the Veeam Backup Service is running. If it is stopped, start it. If when attempting to start the server it fails, Check the SQL Service for the instance Veeam is using.
 

More Information

If none of the above methods resolve the issue, please open a support case for further investigation. If the service is not running, this qualifies as a Severity 1 issue provided you do not have any other Veeam consoles and meet the criteria for a severity 1 issue as defined here: https://www.veeam.com/veeam_software_support_policy_pg.pdf