Add Azure Local Cluster fails with "bad network path"

[tmue]

Hi all!

I have a problem when trying to add our Azure Local Cluster (23H2) to VBR 12.3. as HyperV-Cluster.
When I try to add it it fails with the error on both nodes: Infrastructure item save failed: *HOSTNAME*: The network path was not found.

DNS and network config is fine. I am able to access both nodes with SMB from the VBR server, also C$ and Admin$. Credentials also working.

What I have found on our firewall is that the VBR server - as soon as I try to add the cluster - tries to open port 445 connections to the Cluster-Internal IPs of both nodes which they are using for S2D traffic. These IPs are HyperV internal only and are also configured as "Cluster only". Veeam cannot know these IP adresses - they must come back from the HyperV nodes I think. As I said - DNS is fine. The connections to the Management-IPs of the HyperV Nodes is also fine - 6160, 443, 445, everything is ok, also in our firewall logs. But then it tries the internal IPs and it fails.

Is this a configuration setting I am missing here? Can I force Veeam to use ONLY the Management IP of the Nodes? (They are added with DNS names)
Or am I looking in the wrong places?

[david.domask]

Hi Thomas,

I think before making changes, it's best to open a Support Case and let Support review the situation. While the message sounds like a normal Windows networking issue, it can present this way for a few reasons, and Support will be able to narrow it down with a review of the logs. Please be sure to include logs for Support to review. (Use the 3rd radio button, select the Veeam server itself to export logs from)

Please share your case number once created. Thanks!

[tmue]

Case Number: 07610327

[Moderator: Edited to include Case ID instead of Support ID]

Yeah, it looks like a network issue but it seems nothing is blocking and DNS is working fine.