Microsoft KB Archive Search

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.

  1. Home
  2. You cannot use a certificate-based logon method to authenticate requests on a computer that is running Windows Server 2008 R2

You cannot use a certificate-based logon method to authenticate requests on a computer that is running Windows Server 2008 R2

View products that this article applies to.

Symptoms

On a computer that is running Windows Server 2008 R2, you use a certificate-based logon method to authenticate requests for access to one or more of the following kinds of service:
  • Wireless authentication
  • Virtual private network (VPN)
  • Smart Card-based authentication
In this situation, you cannot authenticate the requests. However, you may successfully authenticate the requests after one or more retries.

Notes This issue occurs when you have an Online Certificate Status Protocol (OCSP) URL in the OCSP extension on the server-side certificate.

You may experience the following two issues:
  • Event ID 29 may be logged in the System log on a domain controller. This event indicates that the currently-selected domain controller certificate is invalid and therefore blocks smart card logon. However, you may experience this issue without this event being logged.
  • A middle tier server accepts certificate based authentication and then needs to acquire a handle to the incoming credentials for impersonation. The likely scenarios for this are, but are not limited to:
    • Internet Information Server (IIS) server
    • VPN server
    • Data Access Server (DAS) server
    • NPS server


    Example event 29:
  • Log Name: System
    Source: Microsoft-Windows-Kerberos-Key-Distribution-Center
    Event ID: 29
    Task Category: None
    Level: Warning
    Keywords: Classic
    Description:
    The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate could not be verified. Smart card logon may not function correctly if this problem is not resolved. To correct this problem, either verify the existing KDC certificate using certutil.exe or enroll for a new KDC certificate.

↑ Back to the top

Cause

This issue occurs because the locally cached Certificate Revocation List (CRL) is expired and the OSCP responder is offline.

↑ Back to the top

Resolution

To resolve this issue, install the following hotfix on the affected middle tier server or on the domain controller.

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:
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

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
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:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, 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 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" 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.
    VersionProductSR_LevelService branch
    6.1.760
    0.
    21xxx    		Windows Server 2008 R2RTMLDR
    6.1.760
    1.
    21xxx    		Windows Server 2008 R2SP1LDR
  • 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
File nameFile versionFile sizeDateTimePlatform
Cryptnet.dll6.1.7600.21149138,75211-Feb-201206:27x64
Cryptnet.dll6.1.7601.21921138,75211-Feb-201206:21x64
Cryptnet.dll6.1.7600.21149103,42411-Feb-201205:32x86
Cryptnet.dll6.1.7601.21921103,42411-Feb-201205:22x86
For all supported IA-64–based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Cryptnet.dll6.1.7600.21149266,75211-Feb-201205:16IA-64
Cryptnet.dll6.1.7601.21921266,75211-Feb-201205:14IA-64
Cryptnet.dll6.1.7600.21149103,42411-Feb-201205:32x86
Cryptnet.dll6.1.7601.21921103,42411-Feb-201205:22x86

↑ 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

The frequency of this issue depends on the availability of the OCSP server. This issue occurs when the following conditions are true:
  • A response from an OCSP URL is not received when a certificate-based logon attempt is verified.
  • None of the locally cached revocation data is time valid.

By default, Windows tries to cache and prefetch CRL certificates in advance. Sometimes, this behavior is skipped. This depends on the CRL lifetime and the presence of a NextPublish Extension. When a certificate is verified, the OCSP URL is checked first. If this verification attempt fails, Windows behaves as if it has recently tried to retrieve a CRL from a CDP point. Therefore, successive verification attempts to connect to a CRL point fail.

After you install the following hotfix, the attempt to retrieve a CRL after a failed OCSP retrieval is successful.

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 Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_047bbbbfdd6e8da3418389ccc596f0fc_31bf3856ad364e35_6.1.7601.21921_none_2e957a196650a594.manifest
File versionNot applicable
File size702
Date (UTC)11-Feb-2012
Time (UTC)12:19
PlatformNot applicable
File nameAmd64_2806d6f4168d2765e88e5d9373bf9a95_31bf3856ad364e35_6.1.7601.21921_none_8cc20b26eca42bd3.manifest
File versionNot applicable
File size1,048
Date (UTC)11-Feb-2012
Time (UTC)12:19
PlatformNot applicable
File nameAmd64_8533c7e087c9a8c9728e1de9d757b5fb_31bf3856ad364e35_6.1.7600.21149_none_1995cb01990ef133.manifest
File versionNot applicable
File size704
Date (UTC)11-Feb-2012
Time (UTC)12:19
PlatformNot applicable
File nameAmd64_86778bb3da99fe6329898e5a3eba5738_31bf3856ad364e35_6.1.7601.21921_none_8cc891846384c2ea.manifest
File versionNot applicable
File size704
Date (UTC)11-Feb-2012
Time (UTC)12:19
PlatformNot applicable
File nameAmd64_9c6816328add12ab044eafb482413f93_31bf3856ad364e35_6.1.7600.21149_none_3161088aee555619.manifest
File versionNot applicable
File size702
Date (UTC)11-Feb-2012
Time (UTC)12:19
PlatformNot applicable
File nameAmd64_bb3bfb175d0a328820a99b7449d950ef_31bf3856ad364e35_6.1.7600.21149_none_17b0da8104d6b1ec.manifest
File versionNot applicable
File size1,048
Date (UTC)11-Feb-2012
Time (UTC)12:19
PlatformNot applicable
File nameAmd64_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7600.21149_none_73c6f3ea2e807779.manifest
File versionNot applicable
File size2,282
Date (UTC)11-Feb-2012
Time (UTC)07:02
PlatformNot applicable
File nameAmd64_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7601.21921_none_75bb183c2b9daab0.manifest
File versionNot applicable
File size2,282
Date (UTC)11-Feb-2012
Time (UTC)06:50
PlatformNot applicable
File nameX86_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7600.21149_none_17a8586676230643.manifest
File versionNot applicable
File size2,280
Date (UTC)11-Feb-2012
Time (UTC)06:05
PlatformNot applicable
File nameX86_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7601.21921_none_199c7cb87340397a.manifest
File versionNot applicable
File size2,280
Date (UTC)11-Feb-2012
Time (UTC)05:52
PlatformNot applicable
Additional files for all supported IA-64–based versions of Windows Server 2008 R2
File nameIa64_4884d8c77b8bb852a9f7d0522449c0c8_31bf3856ad364e35_6.1.7600.21149_none_791acb5ac56b3def.manifest
File versionNot applicable
File size1,046
Date (UTC)11-Feb-2012
Time (UTC)12:19
PlatformNot applicable
File nameIa64_5b3bc8046eab21b7d0d21e15e47660a0_31bf3856ad364e35_6.1.7601.21921_none_3451a477fd76986f.manifest
File versionNot applicable
File size1,046
Date (UTC)11-Feb-2012
Time (UTC)12:19
PlatformNot applicable
File nameIa64_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7600.21149_none_17a9fc5c76210f3f.manifest
File versionNot applicable
File size2,281
Date (UTC)11-Feb-2012
Time (UTC)06:52
PlatformNot applicable
File nameIa64_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7601.21921_none_199e20ae733e4276.manifest
File versionNot applicable
File size2,281
Date (UTC)11-Feb-2012
Time (UTC)06:43
PlatformNot applicable
File nameX86_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7600.21149_none_17a8586676230643.manifest
File versionNot applicable
File size2,280
Date (UTC)11-Feb-2012
Time (UTC)06:05
PlatformNot applicable
File nameX86_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7601.21921_none_199c7cb87340397a.manifest
File versionNot applicable
File size2,280
Date (UTC)11-Feb-2012
Time (UTC)05:52
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2666300
Revision : 1
Created on : 1/7/2017
Published on : 1/4/2013
Exists online : False
Views : 282