Hyper-V 2016 3-Node Cluster - Getting 'Your credentials did not work" connecting to Roles on one node but not the others.

Wayne Eaton 5 Reputation points
2023-02-26T20:39:33.57+00:00

Hi - I have a 2016 Hyper-V failover cluster using a cluster storage volume on a Dell SAN. Node 1 and 2 were part of an original installation and I can do live migrations between the two and I can log onto either node, open Failover Cluster Manager and connect to any hyper-v role on Node 1 and 2. Recently added Node 3. Processor was different than Node 1 and 2 but I updated Node 1 and 2 processors. Validate Cluster and all is good (few Roles Integration Services aren't updated but these aren't necessarily the machines I'm having problems with.) Problem 1: When I'm on Node 1 or 2 and use Failover Cluster Manager to connect to a role on Node 3, I get the message 'Your credentials did not work". Problem 2: I cannot perform live migrations from Node 1 or 2 to Node 3 and vice-versa. I have compared every possible setting I can find between Nodes 1, 2 and 3 but cannot figure out why I'm having these problems. Hundreds of Google searches and reading articles have not helped me resolve this. All the Virtual Switches are named the same, firmware is all the same, tried enabling Processor Compatibility, checked permissions, etc.. During Live Migration I get the typical EventID 21502, 1205, 1069. In 21502 it says:

User "DOMAIN\WDHVCLS01$" failed to create external configuration store at 'c:\ClusterStorage\Volume1\Hyper-V\SERVERNAME' General access denied error ()x80070005.

Failed to set security info for '\?\Volume [SID]\hyper-v\servername\Virtual Machines' General access denied error (0x80070005)

You are using Kerberos authentication option for live migration which requires setting up credential delegation. The access denied might have been caused by incorrect delegation setup.

I've checked all the above and have not been able to fix anything. I've also evicted the Node 3 and joined it in again, but no luck.

Any help anyone can provide would be appreciated.

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. risolis 8,741 Reputation points
    2023-02-26T21:24:08.3366667+00:00

    Hello @Wayne Eaton

    Thank you for posting this concern on this community space.

    I have read your case scenario description and I am wondering if you have checked the TLS certificate on your Kerberos set up (If this applies to your scenario)

    Looking forward to your feedback,

    Cheers,

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.