You receive a "Logon failure" message when you use a smart card on a Windows Server 2003-based computer (887578)
The information in this article applies to:
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Datacenter Edition
- Microsoft Windows Server 2003, Enterprise Edition
- 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, 64-Bit Enterprise Edition
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 SYMPTOMSWhen 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 failureCAUSEThis 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.RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesNo prerequisites are required. Restart requirementYou must restart your computer after you apply this hotfix. Hotfix replacement informationThis 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 |
Crypt32.dll | 5.131.3790.425 | 1,578,496 | 14-Oct-2005 | 05:21 | IA-64 | None | RTMQFE | Cryptnet.dll | 5.131.3790.425 | 160,256 | 14-Oct-2005 | 05:21 | IA-64 | None | RTMQFE | Kdcsvc.dll | 5.2.3790.425 | 590,336 | 14-Oct-2005 | 05:21 | IA-64 | None | RTMQFE | Kerberos.dll | 5.2.3790.425 | 907,264 | 14-Oct-2005 | 05:21 | IA-64 | None | RTMQFE | Wcrypt32.dll | 5.131.3790.425 | 612,864 | 14-Oct-2005 | 05:21 | x86 | None | WOW | Wcryptnet.dll | 5.131.3790.425 | 61,952 | 14-Oct-2005 | 05:21 | x86 | None | WOW | Wkerberos.dll | 5.2.3790.425 | 344,064 | 14-Oct-2005 | 05:21 | x86 | None | WOW | Crypt32.dll | 5.131.3790.2548 | 1,759,232 | 14-Oct-2005 | 05:21 | IA-64 | SP1 | SP1QFE | Cryptnet.dll | 5.131.3790.2548 | 172,544 | 14-Oct-2005 | 05:21 | IA-64 | SP1 | SP1QFE | Kdcsvc.dll | 5.2.3790.2548 | 613,888 | 14-Oct-2005 | 05:21 | IA-64 | SP1 | SP1QFE | Kerberos.dll | 5.2.3790.2548 | 963,072 | 14-Oct-2005 | 05:21 | IA-64 | SP1 | SP1QFE | Wcrypt32.dll | 5.131.3790.2548 | 595,968 | 14-Oct-2005 | 05:21 | x86 | SP1 | WOW | Wcryptnet.dll | 5.131.3790.2548 | 62,464 | 14-Oct-2005 | 05:21 | x86 | SP1 | WOW | Wkerberos.dll | 5.2.3790.2548 | 350,720 | 14-Oct-2005 | 05:21 | x86 | SP1 | WOW |
x64-based versions |
Crypt32.dll | 5.131.3790.2548 | 1,428,992 | 14-Oct-2005 | 05:21 | x64 | SP1 | SP1QFE | Cryptnet.dll | 5.131.3790.2548 | 111,104 | 14-Oct-2005 | 05:21 | x64 | SP1 | SP1QFE | Kdcsvc.dll | 5.2.3790.2548 | 419,840 | 14-Oct-2005 | 05:21 | x64 | SP1 | SP1QFE | Kerberos.dll | 5.2.3790.2548 | 720,896 | 14-Oct-2005 | 05:21 | x64 | SP1 | SP1QFE | Wcrypt32.dll | 5.131.3790.2548 | 595,968 | 14-Oct-2005 | 05:21 | x86 | SP1 | WOW | Wcryptnet.dll | 5.131.3790.2548 | 62,464 | 14-Oct-2005 | 05:21 | x86 | SP1 | WOW | Wkerberos.dll | 5.2.3790.2548 | 350,720 | 14-Oct-2005 | 05:21 | x86 | SP1 | WOW |
x86-based versions |
Crypt32.dll | 5.131.3790.425 | 612,864 | 14-Oct-2005 | 04:10 | x86 | None | RTMQFE | Cryptnet.dll | 5.131.3790.425 | 61,952 | 14-Oct-2005 | 04:10 | x86 | None | RTMQFE | Kdcsvc.dll | 5.2.3790.425 | 227,840 | 14-Oct-2005 | 04:10 | x86 | None | | Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. After you have installed the hotfix, the following three registry keys are made available so that you can extend the validity period of the CRL. HKEY_Local_Machine\System\CurrentControlSet\Services\KDC\CRLValidityExtensionPeriodThis DWORD value lets you to extend the CRL validity period by a specified number of hours. When you set this value to a non-zero 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 only applies to CRLs that are used during the evaluation of certificates used for smart card logon. For example, this extension would apply to a certificate that is issued by a certification authority (CA) that is populated in the NTAuth store and to any certificates that are part of the trust chain used to verify the NTAuth store certificate. HKEY_Local_Machine\System\CurrentControlSet\Services\KDC\CRLTimeoutPeriodThis 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. HKEY_Local_Machine\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters\CRLTimeoutPeriodThis 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. WORKAROUNDTo work around this problem, disable the policy that requires a smart card to log on. To disable this policy, follow these steps: - Click Start, click Run, type gpedit.msc, and then click OK.
- Under Local Computer Policy, expand Computer Configuration, expand Windows Settings, and then expand Security Settings.
- Expand Local Policies, and then click Security Options.
- In the right pane, double-click Interactive logon: Require smart
card.
- Click Disabled, and then click OK.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 7/24/2006 |
---|
Keywords: | kbQFE kbHotfixServer kbBug kbCertServices kbPPKey kbSmartCard kbWinServ2003preSP1fix kbfix kbprb KB887578 kbAudITPRO |
---|
|