You cannot log on to Windows 8 or Windows Server 2012 when you use SAM format against an MIT KDC

Applies to: Windows 8Windows 8 ProWindows 8 Enterprise


Consider the following scenario:
  • You have a Massachusetts Institute of Technology (MIT) Key Distribution Center (KDC) for Kerberos authentication in a Linux domain (the realm domain name is in lowercase).
  • You have a Windows Server 2008 R2 Active Directory domain and create a trust relationship with the realm domain name.
  • You use Windows 8 client in AD domain to map drive against the Linux domain share.
In this scenario, when you use Security Accounts Manager (SAM) format (<<linuxdomain>>\username) to log on the computer, it fails. However, if you use User principal name (UPN) format (username@<<linuxdomain>>), it works.

Note For more information about Kerberos authentication, go to the following website:


This issue occurs because Windows 8 or Windows Server 2012 uses uppercase in SAM account format (<<linuxdomain>>\username) against an MIT KDC.


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 this specific problem.

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, submit a request to 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 website: 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.


To apply this hotfix, you must be running Windows 8 or Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates