2019 Hyper-V servers cannot connect to each other.

JeffCleverley-1148 1 Reputation point


We have set up a 2019 Hyper-V/Failover cluster. We have some type of authentication issue between them I can't figure out. We have 4 servers in the cluster that all have the same behavior. I'll just reference 2 as server1 and server2.

If you open Hyper-V manager on server1 and want to connect to server2 I get an error like this:

failed: WinRM cannot process the request. The following error
occurred while using Kerberos authentication: Cannot find the computer server2.mydomain.net. Verify that the
computer exists on the network and that the name provided is spelled correctly.

If I try to connect using the IP address it gives errors about HTTPS or a TrustedHosts list.

If I open a PowerShell window on server1, I can run a enter-pssession to server2 with no issues. If I run a compare-vm command on server1 pointing to server2 I get the same error about not finding the server on the network. I even tried editing the host file on server1 with server2's IP and hostname. I've included both fqdn and short names. It still fails.

If I use our Server 2012R2 Hyper-V manager, it can connect to both server1 and server2 with no issues. If I use the Failover Cluster manager, I can see all VMs, but there are quirks. I can tell server1 to live migrate vm1 to server2 and it will work. If I want to look at the properties of a VM running on server1 but running Failover Cluster on server2, it can't see properties, or connect to the console. It only works if failover cluster is on the name node that the VM is running on.

Here are more details on the setup:
All computers are part of the same domain and in the same OU.
My account is in the administrators account on all servers.
All servers are in each others administrators group.
The storage for the VMs in a CIFS share.

I have noticed that on the 2012 cluster all nodes in the cluster have permissions on the VM image. The 2019 cluster only shows permissions for whatever node it is running on at the time.

I've spent hour on many web pages and tried a lot of configuration changes. I'm at a loss and appreciate any help.



Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
953 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Limitless Technology 39,331 Reputation points


    Thank you for your question and reaching out.

    I understand that you're having issue with regards to setting up 2019 Hyper-V/Failover cluster. Did this connection work once before? If yes, when was the last time you successfully connected both servers? Also, have you made any changes that could cause the issue?

    Based on the information you provided and based on my personal experience, the best way to resolve this is to perform a network reset on both servers first and see if it helps. To do so, kindly follow the steps below:

    Step 1: Select the Start button, then select Settings > Network & Internet > Status > Network reset.

    Step 2: On the Network reset screen, select Reset now > Yes to confirm.

    After doing those steps above, Windows will give you 5 minutes to close all documents and programs before it automatically restart. You can do the restart yourself to save time.


    If the reply was helpful, please don’t forget to Upvote or Accept as answer. Thank you!

    Best regards,

  2. Xu Gu (Shanghai Wicresoft Co,.Ltd.) 501 Reputation points Microsoft Vendor

    Hi ,

    I have a similar case to yours here, and I hope to help you:

    Alternatively, you can check if the Hyper-V Manager is configured correctly by following the link below:

    Best Regards,
    Xu Gu

  3. JeffCleverley-1148 1 Reputation point

    Unfortunately I still have not been able to get the hyper-v manager on any of the nodes to talk to each other. I also still have the issue where the failover cluster manager will only show settings for a VM if the VM is running on that specific node.

    I have tried all the winrm options I can find (quickconfig, etc), enabled psremoting, adding the computer accounts to the remote management group, and still no luck.

    For now we have been able to work around this as an annoyance but it is still something I want to get functional.



    0 comments No comments