Select the product you need help with

FIX: User accounts that use DES encryption for Kerberos authentication types cannot be authenticated in a Windows Server 2003 domain after a Windows Server 2008 R2 domain controller joins the domain

Article ID: 978055 - View products that this article applies to.

Hotfix Download Available

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

A user account is created in a Windows Server 2003 domain.
All domain controllers in this domain are running Windows Server 2003.
The user account is configured to use Data Encryption Standard (DES) encryption types for Kerberos authentication.
A computer that is running Windows Server 2008 R2 joins the domain.
Active Directory is installed on the member server.

In this scenario, the user account cannot log on to the domain immediately after the Windows Server 2008 R2 domain controller starts. You may also receive the following error message:

KDC has no support for encryption type while getting initial credentials.

Additionally, the following events are logged in the System log on the domain controller that is running Windows Server 2008 R2:

Log Name: System
Source: Microsoft-Windows-Kerberos-Key-Distribution-Center
Date: date
Event ID: 14
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computer_name
Description:
While processing an AS request for target service krbtgt, the account name did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 16 1 11 10 15 12 13. The accounts available etypes : 23 -133 -128. Changing or resetting the password of user_name will generate a proper key.

Log Name: System
Source: Microsoft-Windows-Kerberos-Key-Distribution-Center
Date: date
Event ID: 16
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computer_name
Description:
While processing a TGS request for the target server server_name, the account account_name did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 9). The requested etypes were 3 1. The accounts available etypes were 23 -133 -128. Changing or resetting the password of account_name will generate a proper key.

Back to the top | Give Feedback

CAUSE

This problem occurs because different data structures are used to save encryption type information about the user account on Windows Server 2003 domain controllers and on Windows Server 2008 R2 domain controllers.

When a user account is created on a Windows Server 2003 domain controller, the encryption type information is saved in a data structure. Then, this information is copied to Windows Server 2008 R2 domain controllers by using AD replication.

Note This problem also occurs when the password of a user account is reset.

When a Windows Server 2008 R2 domain controller authenticates the user account, the domain controller reads this encryption type information from the data structure that is used by the Windows Server 2003 domain controller. It should then copy this encryption type information to a different data structure. However, the information is not copied as expected. Therefore, authentication fails.

Back to the top | Give Feedback

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

The following list contains prerequisites for the hotfix:

You must have Windows Server 2008 R2 installed.
You must have the Active Directory Domain Service role service installed.

Installation note

Install this hotfix on all domain controllers that run Windows Server 2008 R2 in a Windows Server 2003 domain. This hotfix should not be applied to the Windows Server 2003 servers that are in the domain.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart information

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 R2 file information note

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Kdcsvc.dll	6.1.7600.20597	429,568	16-Dec-2009	16:18	x64
Kdcsvc.mof	Not applicable	5,300	10-Jun-2009	21:01	Not applicable

Back to the top | Give Feedback

(http://support.microsoft.com/kb/824684/ )

Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table

File name	Amd64_ace4830253e8e7b2cdbd3bb4f417cba1_31bf3856ad364e35_6.1.7600.20597_none_ec1bf3810896c5c8.manifest
File version	Not applicable
File size	724
Date (UTC)	17-Dec-2009
Time (UTC)	01:36
Platform	Not applicable
---
File name	Amd64_microsoft-windows-k..distribution-center_31bf3856ad364e35_6.1.7600.20597_none_e82d8950c715d523.manifest
File version	Not applicable
File size	35,825
Date (UTC)	16-Dec-2009
Time (UTC)	16:49
Platform	Not applicable
---
File name	Update.mum
File version	Not applicable
File size	1,700
Date (UTC)	17-Dec-2009
Time (UTC)	01:36
Platform	Not applicable