You receive a "Logon failure" message when you use a smart card on a Windows Server 2003-based computer

Article translations Article translations
Article ID: 887578 - View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
Expand all | Collapse all

On This Page

SYMPTOMS

When you try to use a smart card to log on to a Microsoft Windows Server 2003 domain controller, you cannot log on and you may receive the following message:
Logon failure

CAUSE

This problem occurs when the certificate revocation list (CRL) is outdated and a new CRL is not available. A public key infrastructure (PKI) that is not working can cause the distribution server of the CRL not to publish a new CRL. If a new CRL is not published, logons to client computers are not allowed.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

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. 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=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

No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003
IA-64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Crypt32.dll5.131.3790.4251,578,49614-Oct-200505:21IA-64NoneRTMQFE
Cryptnet.dll5.131.3790.425160,25614-Oct-200505:21IA-64NoneRTMQFE
Kdcsvc.dll5.2.3790.425590,33614-Oct-200505:21IA-64NoneRTMQFE
Kerberos.dll5.2.3790.425907,26414-Oct-200505:21IA-64NoneRTMQFE
Wcrypt32.dll5.131.3790.425612,86414-Oct-200505:21x86NoneWOW
Wcryptnet.dll5.131.3790.42561,95214-Oct-200505:21x86NoneWOW
Wkerberos.dll5.2.3790.425344,06414-Oct-200505:21x86NoneWOW
Crypt32.dll5.131.3790.25481,759,23214-Oct-200505:21IA-64SP1SP1QFE
Cryptnet.dll5.131.3790.2548172,54414-Oct-200505:21IA-64SP1SP1QFE
Kdcsvc.dll5.2.3790.2548613,88814-Oct-200505:21IA-64SP1SP1QFE
Kerberos.dll5.2.3790.2548963,07214-Oct-200505:21IA-64SP1SP1QFE
Wcrypt32.dll5.131.3790.2548595,96814-Oct-200505:21x86SP1WOW
Wcryptnet.dll5.131.3790.254862,46414-Oct-200505:21x86SP1WOW
Wkerberos.dll5.2.3790.2548350,72014-Oct-200505:21x86SP1WOW
x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Crypt32.dll5.131.3790.25481,428,99214-Oct-200505:21x64SP1SP1QFE
Cryptnet.dll5.131.3790.2548111,10414-Oct-200505:21x64SP1SP1QFE
Kdcsvc.dll5.2.3790.2548419,84014-Oct-200505:21x64SP1SP1QFE
Kerberos.dll5.2.3790.2548720,89614-Oct-200505:21x64SP1SP1QFE
Wcrypt32.dll5.131.3790.2548595,96814-Oct-200505:21x86SP1WOW
Wcryptnet.dll5.131.3790.254862,46414-Oct-200505:21x86SP1WOW
Wkerberos.dll5.2.3790.2548350,72014-Oct-200505:21x86SP1WOW
x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Crypt32.dll5.131.3790.425612,86414-Oct-200504:10x86NoneRTMQFE
Cryptnet.dll5.131.3790.42561,95214-Oct-200504:10x86NoneRTMQFE
Kdcsvc.dll5.2.3790.425227,84014-Oct-200504:10x86None

After you install the hotfix

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

If the certification authority (CA) is unavailable to publish a new CRL after you install this hotfix, you can use registry keys to extend the validity period of the CRL. To do this, follow these steps.

On domain controllers

  1. Start Registry Editor.
  2. Locate the following registry subkey:
    HKEY_Local_Machine\System\CurrentControlSet\Services\KDC
  3. On the Edit menu, click New, and then add the following registry entry:

    Value Name: CRLValidityExtensionPeriod
    Value Type: DWORD
    Value Data: Hours (Decimal)
    Description: This DWORD value lets you to extend the CRL validity period by a specified number of hours. When you set this value to a nonzero value, the certificate status checking code for smart card logons ignores any validity period errors as long as the CRL is not expired by more than the number of specified hours. This extension of the validity period applies only to CRLs that are used during the evaluation of certificates that are used for smart card logon. For example, this extension would apply to a certificate that is issued by a CA that is populated in the NTAuth store and to any certificates that are part of the trust chain that is used to verify the NTAuth store certificate.
  4. Locate the following registry subkey:
    HKEY_Local_Machine\System\CurrentControlSet\Services\KDC
  5. On the Edit menu, click New, and then add the following registry entry:

    Value Name: CRLTimeoutPeriod
    Value Type: DWORD
    Value Data: Seconds (Decimal)
    Description: This DWORD value lets you to specify the CRL time-out period to reduce false positives. The Key Distribution Center (KDC) passes this value to the certificate policy checking code. By default, the KDC specifies a time-out value of 90 seconds even if this registry value is not set.

On client computers

Windows XP
  1. Start Registry editor.
  2. Locate the following registry subkey:
    HKEY_Local_Machine\System\CurrentControlSet\Control\LSA\Kerberos
  3. On the Edit menu, click New, and then add the following registry entry:

    Value Name: CRLTimeoutPeriod
    Value Type: DWORD
    Value Data: Seconds (Decimal)
    Description: This DWORD value lets you to specify the CRL time-out period to reduce false positives. The Kerberos client passes this value to the certificate policy checking code. By default, the Kerberos client specifies a time-out value of 90 seconds even if this registry value is not set.
  4. Locate the following registry subkey:
    HKEY_Local_Machine\System\CurrentControlSet\Control\LSA\Kerberos
  5. On the Edit menu, click New, and then add the following registry entry:

    Value Name: UseCachedCRLOnlyAndIgnoreRevocationUnknownErrors
    Value Type: DWORD
    Value Data: 1
    Description: After you set this DWORD value to 1, the Kerberos clients (Smartcard logon clients) will ignore "revocation unknown" errors that are caused by an expired CRL.
Windows Server 2003, Windows Vista, and Windows Server 2008
  1. Start Registry Editor.
  2. Locate the following registry subkey:
    HKEY_Local_Machine\System\CurrentControlSet\Control\LSA\Kerberos\Parameters
  3. On the Edit menu, click New, and then add the following registry entry:

    Value Name: CRLTimeoutPeriod
    Value Type: DWORD
    Value Data: Seconds (Decimal)
    Description: This DWORD value lets you to specify the CRL time-out period to reduce false positives. The Kerberos client passes this value to the certificate policy checking code. By default, the Kerberos client specifies a time-out value of 90 seconds even if this registry value is not set.
  4. Locate the following registry subkey:
    HKEY_Local_Machine\System\CurrentControlSet\Control\LSA\Kerberos\Parameters
  5. On the Edit menu, click New, and then add the following registry entry:

    Value Name: UseCachedCRLOnlyAndIgnoreRevocationUnknownErrors
    Value Type: DWORD
    Value Data: 1
    Description: After you set this DWORD value to 1, the Kerberos clients (Smartcard logon clients) will ignore "revocation unknown" errors that are caused by an expired CRL.

WORKAROUND

To work around this problem, disable the policy that requires a smart card to log on. To disable this policy, follow these steps:
  1. Click Start, click Run, type gpedit.msc, and then click OK.
  2. Under Local Computer Policy, expand Computer Configuration, expand Windows Settings, and then expand Security Settings.
  3. Expand Local Policies, and then click Security Options.
  4. In the right pane, double-click Interactive logon: Require smart card.
  5. Click Disabled, and then click OK.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

MORE INFORMATION

For additional information about PKI and CRL, see the "Checklist: Deploying smart cards for logging on to Windows" Help topic on the following Microsoft Web site:
http://technet2.microsoft.com/WindowsServer/en/library/2e0186ba-1a09-42b5-81c8-3ecca4ddde5e1033.mspx?mfr=true
For more information, 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

Properties

Article ID: 887578 - Last Review: December 4, 2008 - Revision: 7.0
APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, 64-Bit Datacenter Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
Keywords: 
kbautohotfix kbwinserv2003sp2fix kbqfe kbhotfixserver kbbug kbcertservices kbppkey kbsmartcard kbwinserv2003presp1fix kbfix kbprb KB887578

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com