Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
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.
Consider the following scenario:
Additionally, the following events are logged in the System log on the domain controller that is running Windows Server 2008 R2:
KDC has no support for encryption type while getting initial credentials.
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.
Hotfix informationA 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=supportNote 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.
PrerequisitesThe following list contains prerequisites for the hotfix:
Installation noteInstall 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 informationTo use the hotfix in this package, you do not have to make any changes to the registry.
Restart informationYou may have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe 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
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
To work around this issue, reset the password of the problematic user account on the domain controller that is running Windows Server 2008 R2.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(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