KDC error 26 and 27 constantly on DCs

Getting Tons of KDC errors on tons of user accounts.

There are both windows 2003 and windows 2008 domain controllers.

While processing an AS request for target service krbtgt, the account User123 did not  have a suitable key for generating a Kerberos ticket (the missing key has an ID of 2). The requested etypes were 18.  The accounts available etypes were 23  -133  -128  3  1  -140.

While processing a TGS request for the target server krbtgt/domain.com, the account Computer$@domain.COM did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 8). The requested etypes were 18.  The accounts available etypes were 23  -133  -128  3  1.

Also getting netlogon alerts 5805 and 5723

The session setup from the computer SOMECOMPUTER failed to authenticate. The name(s) of the account(s) referenced in the security database is SOMECOMPUTER$.  The following error occurred:
Access is denied.

The session setup from computer SOMECOMPUTER failed because the security database does not contain a trust account SOMECOMPUTER$ referenced by the specified computer.
Who is Participating?
ZenVenkyConnect With a Mentor ArchitectCommented:
This happens only in mixed environment (Server 2003 and 2008). These KDC events occurs when clients requests service ticket with a etype 18 (aes256-cts-hmac-sha1-96), which is not supported by Windows Server 2003 but supported by Windows Server 2008 R2. Best way is to resolve it is make 2008 DC as PDCe role holder and reboot it once. Also make sure PDCe role holder as Authoritative Time Server.




DNS Best Practices

Authoritative Time Server
Sarang TinguriaConnect With a Mentor Sr EngineerCommented:
I agree with below link..In my case too it was 2003 DC logging events

KDC Event ID 26 and 27 logged on 2003 DC
SandeshdubeyConnect With a Mentor Senior Server EngineerCommented:
The problem is that the client is sending a TGS request using the Etype of 18  (AES). Windows 2003 does not support this etype for Kerberos where 2008  does. The error that is being logged on the domain controller can safely be  ignored as it is by design.The domain controller is just informing the  client what etypes it does support.
EventID 26 & 27 : KDC: suitable keys
KDC Event ID 16 or 27 is logged if DES for Kerberos is disabled
Event ID 27 — KDC Encryption Type Configuration

Reference link:http://social.technet.microsoft.com/Forums/windowsserver/en-US/ba598be9-3a06-4a7a-932b-013891d35f78/final-check-before-demoting-the-win2k3-dc
Hope this helps
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.