Failed to add the Hyper-V host and Windows repository to the Veeam Backup Appliance.

[eric123321]

My Veeam backup appliance is running on a Hyper-V 2022 host equipped with Broadcom network adapters and VMQ enabled.

When attempting to add Windows or other Hyper-V servers, I encounter intermittent errors including 'Connection reset by peer' and 'KDC realm not found.' I can successfully ping and telnet into ports 6160, 445, and 139 from backup appliance to windows server or hyperV server.

I have also tried using the Veeam Deployment Toolkit, but I am still unable to add the servers.

One strange thing is the appliance cannot communicate with its own Hyper-V host. Specifically, pinging from the appliance to the host results in a 'No route to host' error.

Could this be related to known Broadcom VMQ issues, or is there another underlying cause? I have already uninstalled the antivirus and disabled the firewalls on both sides.

[david.domask]

Hi eric123321,

Please open a Support Case and allow Veeam Support to review the behavior. We will not be able to meaningfully troubleshoot over the forums.

A quick check on VMQ related to Hyper-V suggests that it does struggle when there is high I/O, but not sure that's related to your situation. Temporarily disabling it and testing may help isolate, but still it's best to check the behavior with Support. Please share your case number once created, thanks.