Hi @Walter.Emmanuel -

The error pretty much is explicit on what’s going on. Now, the problem is pinpointing what the ‘connection problem’ is. There are logs in: C:\ProgramData\Veeam\Backup\<backup-job-name>.log you can look at to see if there are more details to help you out. You can also look at things like pingability from Veeam or your Proxy, check if there’s a firewall issue on the VM (i.e. if it’s Windows..or even Linux), check if UAC is enabled and causing issues, etc.

Also, do you have AAIP (guest processing) enabled? If so, is the account used a local admin? Can you do the ‘test’ of this and it all be successful in connecting? Those are some things to look at to start.

A few more details will also help like the exact build of Veeam v12 - 12.1.x, 12.2 (new build last week).  Also ensure to check the Firewall in Windows (if that is the OS being backed up) as well as permissions, etc.  Usual checks for Veeam.  

Insufficient information actually to help pinpoint your issue. 

In terms of pingablility from the Veeam server, I am able to ping said server. However when I try to rescan that server I am getting the same issue

The Veeam build version that I have is 12.1.2.172

Did you check Windows Firewall and/or UAC? Is this a VM that’s failing in a regular VM-based Backup Job? Another type of Veeam Job? Need way more details here @Walter.Emmanuel . Also, Job logs can be reviewed in the location I shared above. At the very least (and recommended to do as we’re not them) is to contact Veeam Support for better assistance.

Best.

Not sure if you are willing to update to 12.2 released last week but something to suggest.  Also support seems like the best route at this point in time.