Hyper V environment-Active Directory/Domain
Veeam 12 is on VM1 on my domain pc
Backup repository is a VM2 on a hyper v host1
We have a firewall doing what firewalls do etc
VM1 successfully added VM2(veeam backup repository)
The problem:
- Tried adding a windows server VM3 to VM1(located on hyper v host2) - I get the network path & credentials error
- Tried adding a veeamproxy machine VM4 to VM1 - I get the network path & credentials error
The AD admin user account used in above attempts works perfectly on all computers in my LAN
I used same ad admin account that I used to add VM2 to VM1(now listed in veeam as a valid AD account) for VM3 & VM4
There is solid communication between VM1 and other servers, confirmed via icmp/pings
I have other hyper v hosts and dont want to be testing this on all of them
What is going on here, is this a firewall issue? if so, what specific ports (you have a table full of ports) must be opened for your application and where should I focus these changes/policies, on the external firewall or windows firewall on the hyper v host and/or vm guest on the host?
In earlier versions of veeam e.g. 9.5, i had no issues adding servers, backup proxies etc and I had fully setup firewalls in my environment cisco, checkpoint.