This article describes a hotfix for Kerberos authentication that must be installed on Windows Server 2008 R2-based and Windows Server 2008-based global catalogs.
Currently, Kerberos authentication enables a user to log on to a domain-joined computer by using user credentials in one of the following formats:
User principal name (UPN)
FQDN domain name\username
NetBIOS domain name\username
The Kerberos referral mechanism works correctly in all environments when you use the UPN or "FQDN domain name\username" formats. However, when you use the "NetBIOS domain name\username" format, the Kerberos referral mechanism works correctly only in a single forest environment. The "NetBIOS domain name\username" format cannot be used for user accounts in a child domain when the Kerberos referral mechanism is working in a cross-forest environment in which trusts are established among the forests.
For example, when you try to use the "NetBIOS domain name\username" format to log on as a user in a child domain in a trusted forest on a computer that is running Windows 8 Customer Preview, the authentication process fails. However, you can use the "NetBIOS domain name\username" format for user accounts in the forest root domain of the trusted forest.
This issue affects applications that use Kerberos service for user (S4U) extensions to create a context for a user in a trusted forest. For example, consider the following scenario:
A user has an application that uses a Kerberos S4U extension on a server in forest A.
The user is in the child domain of trusted forest B.
The Kerberos S4U extension is invoked to pass the NetBIOS name of the child domain in forest B.
In this situation, the Key Distribution Center (KDC) in forest A cannot generate a Kerberos referral path to trusted forest B, and you receive a "KDC_ERR_S_PRINCIPAL_UNKNOWN (7)" error.
The global catalog recognizes the NetBIOS names of trusted forest root domains but does not recognize the NetBIOS names of child domains in trusted forests. Therefore, when the KDC in one forest tries to find the KDC of a child domain in another forest by using the "NetBIOS domain name\username" format, the global catalog cannot lookup the domain. This behavior causes the KDC to fail because the KDC cannot create a referral ticket.
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 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.
Prerequisites
To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1) or Windows Server 2008 SP2. Additionally, the Active Directory Domain Services (AD DS) role must be installed on the computer.
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Windows Server 2008
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global 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 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
Version
Product
SR_Level
Service branch
6.0.600
2
.
22xxx
Windows Server 2008
SP2
LDR
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" section. MUM files 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 x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ksecdd.sys
6.0.6002.22869
440,704
25-Jun-2012
10:59
x86
Lsasrv.dll
6.0.6002.22962
1,260,032
31-Oct-2012
02:39
x86
Lsasrv.mof
Not Applicable
13,780
09-Sep-2011
11:41
Not Applicable
Lsass.exe
6.0.6002.22962
9,728
31-Oct-2012
01:21
x86
Secur32.dll
6.0.6002.22962
72,704
31-Oct-2012
02:40
x86
Wdigest.dll
6.0.6002.22964
175,104
02-Nov-2012
09:05
x86
Msv1_0.dll
6.0.6002.22964
218,624
02-Nov-2012
09:03
x86
Schannel.dll
6.0.6002.22964
279,552
02-Nov-2012
09:04
x86
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ksecdd.sys
6.0.6002.22869
516,480
25-Jun-2012
10:59
x64
Lsasrv.dll
6.0.6002.22962
1,690,624
31-Oct-2012
03:48
x64
Lsasrv.mof
Not Applicable
13,780
15-Nov-2011
15:19
Not Applicable
Lsass.exe
6.0.6002.22962
11,264
31-Oct-2012
02:09
x64
Secur32.dll
6.0.6002.22962
94,720
31-Oct-2012
03:50
x64
Wdigest.dll
6.0.6002.22964
205,312
02-Nov-2012
09:43
x64
Msv1_0.dll
6.0.6002.22964
269,312
02-Nov-2012
09:41
x64
Schannel.dll
6.0.6002.22964
348,160
02-Nov-2012
09:42
x64
Lsasrv.mof
Not Applicable
13,780
09-Sep-2011
11:41
Not Applicable
Secur32.dll
6.0.6002.22962
77,312
31-Oct-2012
02:41
x86
Wdigest.dll
6.0.6002.22964
175,104
02-Nov-2012
09:05
x86
Msv1_0.dll
6.0.6002.22964
218,624
02-Nov-2012
09:03
x86
Schannel.dll
6.0.6002.22964
279,552
02-Nov-2012
09:04
x86
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Ksecdd.sys
6.0.6002.22869
1,029,504
25-Jun-2012
12:17
IA-64
Lsasrv.dll
6.0.6002.22962
3,262,464
31-Oct-2012
02:11
IA-64
Lsasrv.mof
Not Applicable
13,780
15-Mar-2011
05:54
Not Applicable
Lsass.exe
6.0.6002.22962
17,920
31-Oct-2012
01:07
IA-64
Secur32.dll
6.0.6002.22962
202,752
31-Oct-2012
02:13
IA-64
Wdigest.dll
6.0.6002.22964
482,304
02-Nov-2012
07:42
IA-64
Msv1_0.dll
6.0.6002.22964
570,368
02-Nov-2012
07:40
IA-64
Schannel.dll
6.0.6002.22964
812,032
02-Nov-2012
07:41
IA-64
Lsasrv.mof
Not Applicable
13,780
09-Sep-2011
11:41
Not Applicable
Secur32.dll
6.0.6002.22962
77,312
31-Oct-2012
02:41
x86
Wdigest.dll
6.0.6002.22964
175,104
02-Nov-2012
09:05
x86
Msv1_0.dll
6.0.6002.22964
218,624
02-Nov-2012
09:03
x86
Schannel.dll
6.0.6002.22964
279,552
02-Nov-2012
09:04
x86
Windows Server 2008 R2 file information notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760
1.21xxx
Windows Server 2008 R2
SP1
LDR
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
Back to the top
