Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot connect a DirectAccess client to a corporate network in Windows 8 or Windows Server 2012


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You deploy DirectAccess in a corporate environment by using a Kerberos Key Distribution Center (KDC) proxy service.
  • The KDC proxy service uses the Network Access Protection (NAP) certificate for TLS/SSL client authentication.
  • You try to connect a DirectAccess client that is running Windows 8 or Windows Server 2012 to the corporate network.

In this scenario, the DirectAccess client remains in the Connecting state and is not connected to the corporate network.

↑ Back to the top


Cause

This issue occurs because the NAP certificate expires after 3 days, and the KDC proxy service does not release the certificate after the certificate expires.

↑ Back to the top


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 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 8 or Windows Server 2012.

Registry information

To use 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 8 and Windows Server 2012 file information note
Important Windows 8 and Windows Server 2012 updates are included in the same packages.
  • 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:
    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows 8 and Windows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows 8 and for Windows Server 2012" section. 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 8
File nameFile versionFile sizeDateTimePlatform
Kerberos.dll6.2.9200.16432653,82410-Oct-201206:30x86
Kerberos.dll6.2.9200.20533653,82410-Oct-201206:43x86

For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Kerberos.dll6.2.9200.16432816,64010-Oct-201207:04x64
Kerberos.dll6.2.9200.20533816,64010-Oct-201207:16x64
Kerberos.dll6.2.9200.16432653,82410-Oct-201206:30x86
Kerberos.dll6.2.9200.20533653,82410-Oct-201206:43x86

↑ Back to the top


Workaround

To work around the issue, restart the DirectAccess client.

↑ Back to the top


Status

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

↑ Back to the top


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

Additional file information

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File nameX86_50491aef0565ba1fb218033cf19e404d_31bf3856ad364e35_6.2.9200.16432_none_f7cc0a51e1fae74a.manifest
File versionNot applicable
File size705
Date (UTC)10-Oct-2012
Time (UTC)20:54
PlatformNot applicable
File nameX86_52d106c924a20b4905b8cd744e156b8e_31bf3856ad364e35_6.2.9200.20533_none_99b95a639591dc9e.manifest
File versionNot applicable
File size705
Date (UTC)10-Oct-2012
Time (UTC)20:54
PlatformNot applicable
File nameX86_microsoft-windows-security-kerberos_31bf3856ad364e35_6.2.9200.16432_none_e3b5f9fa820d937d.manifest
File versionNot applicable
File size47,997
Date (UTC)10-Oct-2012
Time (UTC)07:16
PlatformNot applicable
File nameX86_microsoft-windows-security-kerberos_31bf3856ad364e35_6.2.9200.20533_none_e440970f9b2a4c9e.manifest
File versionNot applicable
File size47,997
Date (UTC)10-Oct-2012
Time (UTC)07:38
PlatformNot applicable

Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_2d2573a36bf61e79e8b8ed08337a7ead_31bf3856ad364e35_6.2.9200.16432_none_e14aa6c6ca6ad68e.manifest
File versionNot applicable
File size709
Date (UTC)10-Oct-2012
Time (UTC)20:54
PlatformNot applicable
File nameAmd64_4899d20f89c847a99b8a1d71d5f897f4_31bf3856ad364e35_6.2.9200.20533_none_4c5e3407896d8e08.manifest
File versionNot applicable
File size1,060
Date (UTC)10-Oct-2012
Time (UTC)20:54
PlatformNot applicable
File nameAmd64_81d859c50f0a019f2b929930bd5b8e04_31bf3856ad364e35_6.2.9200.16432_none_6b640c20c125b574.manifest
File versionNot applicable
File size1,060
Date (UTC)10-Oct-2012
Time (UTC)20:54
PlatformNot applicable
File nameAmd64_89b79c0045f9f0dc97bee30bc4006c25_31bf3856ad364e35_6.2.9200.20533_none_f6966b602703a48e.manifest
File versionNot applicable
File size709
Date (UTC)10-Oct-2012
Time (UTC)20:54
PlatformNot applicable
File nameAmd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.2.9200.16432_none_3fd4957e3a6b04b3.manifest
File versionNot applicable
File size48,001
Date (UTC)10-Oct-2012
Time (UTC)09:43
PlatformNot applicable
File nameAmd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.2.9200.20533_none_405f32935387bdd4.manifest
File versionNot applicable
File size48,001
Date (UTC)10-Oct-2012
Time (UTC)09:57
PlatformNot applicable
File nameWow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.2.9200.16432_none_4a293fd06ecbc6ae.manifest
File versionNot applicable
File size37,746
Date (UTC)10-Oct-2012
Time (UTC)07:13
PlatformNot applicable
File nameWow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.2.9200.20533_none_4ab3dce587e87fcf.manifest
File versionNot applicable
File size37,746
Date (UTC)10-Oct-2012
Time (UTC)07:51
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbexpertisebeginner, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2769240
Revision : 1
Created on : 1/7/2017
Published on : 6/12/2013
Exists online : False
Views : 281