Link to home
Create AccountLog in
Avatar of Bryan Ryan
Bryan Ryan

asked on

Kerberos error

I have 3 Hyper-V hosts. Servers are Windows Server 2012 R2. All of them are reporting error in event viewer:

The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server server3$. The target name used was HTTP/ 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 ( is different from the client domain (, check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

If I try to refresh page on Server Manager the error is:

Error      ourserver : Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error with errorcode 0x80090322 occurred while using Kerberos authentication: An unknown security error occurred.  

Ourserver in DNS has 3 A records and IP are the same as Server1, Server2 and Server3.

I can connect with domain accounts to servers. Why is this happening?
Avatar of Casey Weaver
Casey Weaver
Flag of United States of America image

Have you checked for any time skew? Are the hosts domain joined, or using local admin accounts?
Avatar of RAFA
Flag of Venezuela, Bolivarian Republic of image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Bryan Ryan
Bryan Ryan


Time is ok, they are domain joined. They are joined to failover cluster. But in dns there is a record ourserver, which is pointing to 3 ip (all of three hyper-v hosts). Servercluster is on different name and IP than "ourserver".
Maybe you have an idea or from experience, why was it built this way.

DNS resolution answers by name and ip?

Do not erase any DNS record, put your DNS zone ServerCluster is called like this?

Pointing to your Hyper-V host

I remain attentive to your comments.

No there is server1, server2, server3. It's Hyper-V hosts.
The failover cluster has name Servercluster and separate IP and dns entry. Ourserver is also failover cluster name (don't know why architect made two names). In dns Ourserver has 3 A records, which are same as servers. But the guy who worked before said he remember that Servercluster and Ourserver had same one IP and A record.
In addition Server 3 and Servercluster have each the same two IP's. It was never like this before, because they have one teamed interface.

You can create new records and validate.

Without deleting the other records, or taking note of those records, delete them and create new records.

I remain attentive to your comments.

Proper diagnostic steps are given.