While the above might be true in some cases, the solution is to make sure that one users actual name of the machine (and not some secondary SAN name in certificate - something that might have been recommended in various blogs - it might have worked years ago this way)
That is because WinRM in involved in the replication & you get
If you want to send the traffic via another VLAN (like Live Migration and not the main management vlan), make sure that using hosts file on the source HV server, the ACTUAL name of the replica machine resolves to the VLAN-you-want-to-use IP
So if the hostname is ie RealHV-Host.domain.local with IP 10.10.10.1 but SAN also has vhost01.domain.local & using host file one can resolves that to 172.15.0.1
you will get an error:
Enable-VMReplication : The operation on computer 'vhost01.domain.local' failed: WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer vhost01.domain.local. Verify that the computer exists on the network and that the name provided is spelled correctly.
Just "cheat" using host file & make sure RealHV-Host.domain.local resolves to 172.15.0.1