Hello!
My client has a two-node Windows Server 2012 R2 Hyper-V Cluster which has been running for month or two. The other day I found that from the Hyper-V1 host I couldn't run the Failover Cluster Manager - I got an error "The RPC Server is Unavailable - Exception from HRESULT: 0x800706BA". Then I tried to log into the other Hyper-V Host (Hyper-V2) and found that I couldn't log in using domain credentials - I had to log in locally. On this Hyper-V2 server I saw errors in the System event log:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server hyper-v2$. The target name used was HYPER-V2$. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (XXXX.XXXX.com) is different from the client domain (XXXX.XXXX.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
I've done quite a bit of searching but I didn't find this exact scenario. And because this is a very busy season for my client I'd like to try to resolve this issue with minimal impact to the running VM's. As of right now all of the VM's are working - I just can't manage them from the Failover Cluster Manager (which means that I can't even run live-migrations). I feel pretty much stuck.
Can anyone give me any (safe) guidance on how to proceed? I'd certainly appreciate the help!!!
dave
My client has a two-node Windows Server 2012 R2 Hyper-V Cluster which has been running for month or two. The other day I found that from the Hyper-V1 host I couldn't run the Failover Cluster Manager - I got an error "The RPC Server is Unavailable - Exception from HRESULT: 0x800706BA". Then I tried to log into the other Hyper-V Host (Hyper-V2) and found that I couldn't log in using domain credentials - I had to log in locally. On this Hyper-V2 server I saw errors in the System event log:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server hyper-v2$. The target name used was HYPER-V2$. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (XXXX.XXXX.com) is different from the client domain (XXXX.XXXX.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
I've done quite a bit of searching but I didn't find this exact scenario. And because this is a very busy season for my client I'd like to try to resolve this issue with minimal impact to the running VM's. As of right now all of the VM's are working - I just can't manage them from the Failover Cluster Manager (which means that I can't even run live-migrations). I feel pretty much stuck.
Can anyone give me any (safe) guidance on how to proceed? I'd certainly appreciate the help!!!
dave