Can't add VBR server to Enterprise Manager after migration to new server

[Eric F.]

We are getting an error of:

"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"

.. when trying to add a VBR server to the Veeam Enterprise Manager. This happened after we migrated VBR to a new server. The old server, in the same network / domain was able to connect just fine.

I tested with known bad credentials and got the expected "The server has rejected the client credentials" so the connection error above is not being caused by incorrect credentials.

All permissions should be set properly per Veeam support (logged into the VEM server as the backup service account, the service account is a local admin on the VBR & VEM server, the service account is a VBR Veeam Admin, and the account is a VEM Portal Admin).

We ran a Wireshark and port 9392 connects and communicates without issue. Port 9405 communicates back and forth, but we get a reset packet soon after connection from the VBR server. We verified that the Veeam Backup service on the VBR is listening on port 9405. The bindings on the VEM IIS site is set to use the self-signed certificate. We reinstalled the VEM server and are having the same issue.

We don't know where to turn next. This is being worked on Case #07699093.

[david.domask]

Hi Eric F.,

Thank you for sharing the case number and the case details -- I see the case is already escalated to our Advanced Support, so please continue working with Support on the matter.

The error itself unfortunately does not tell much except that there is some connection issue, and what you've checked so far with Support seems reasonable.