"Failed to establish connection: no valid IP addresses were found. 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 10.x.x.x:10005"

The problem here is my Veeam VM is not on that network. It is only home network 192.x.x.x using  hyper-v switch.  The network referenced in the error strictly a closed vlan for security cams which is a secondary nic on the host server.  The host server and domain controller backup fine but the win11 clients Veeam keeps trying to use secondary nic which is not connected to the vm. AD DNS does not have any enters for the other network.  so somehow it Veeam is trying to use the host server nics at will.

I have set the global traffic preferred network to the home network. makes non difference disabled all firewalls on all devices not joy same error.  my only other thought would be to force all the firewall rules to a scope for the home network.  But do to the work involved I thought I should ask if I missing a hidden setting some where.  its either going to be veeam firewall scope or some weird way of Veeam VM communicating with the host os.

I use Veeam in my professional work environment which is more complicated setup then the community edition setup I using here at home.