Cannot Discover Hyper-V Cluster with Direct Connect Transporter

Product version: 11.1

Last modified: 24 April 2025

Problem

The operation fails when attempting to discover a Microsoft Hyper-V cluster from the client site using a Direct Connect Transporter. At the same time:

• The Direct Connect Transporter is successfully connected to the MSP.

• The Direct Connect Transporter can ping the Hyper-V cluster and its hosts with their IPs.

However, the discovery process fails.

Solution

To fix the problem and enable proper discovery of the Hyper-V cluster, ensure the Direct Connect Transporter can resolve the FQDN of the cluster. You can achieve this by using one of the following methods:

• Use a Proper DNS Server: Configure the DNS settings of the Transporter VM to use a DNS server that can resolve the cluster’s FQDN.

• Manually Edit the Hosts File: Add entries for the Hyper-V cluster nodes in the hosts file of the Direct Connect Transporter VM, for example:

10.10.33.55 cluster01.domain.local

10.10.33.53 node01.domain.local

10.10.33.54 node02.domain.local