Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
The StrongCRLCheck setting does not work on a Windows Server 2008 R2-based computer that has the RRAS role service installed
Article ID: 2351254 - View products that this article applies to.
Consider the following scenario:
The issue occurs because the Remote Access Service (RAS) ignores the StrongCRLCheck setting.
Note After you install the hotfix, you have to create an L2tpCRLCheckLevel registry subkey to configure the level of check to be performed for L2TP/IPsec connections. For more information about how to create this registry subkey, see the "Registry information" section.
Hotfix informationA 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=supportNote 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.
PrerequisitesTo apply this hotfix, you must be running Windows Server 2008 R2.
Registry informationImportant 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:
322756After you install the hotfix, you have to create a registry subkey to configure the level of check to be performed for L2TP/IPsec connections.
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Note This registry subkey does not affect Internet Key Exchange version 2 (IKEv2) connections.To do this, follow these steps:
Restart requirementYou may have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe 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 notesImportant 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.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
For all supported IA-64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
961361For more information about Internet Protocol security (IPsec), visit the following Microsoft webpage.
(http://support.microsoft.com/kb/961361/ )The IPsec client can connect to a Windows Server 2003-based server even when the StrongCRLCheck attribute is set to 1 and a revoked certificate exists in the certificate chain
Step-by-Step Guide to Internet Protocol Security (IPSec)
For more information about Netsh commands for Internet Protocol security (IPsec), visit the following Microsoft webpage.
Introduction to Netsh Commands for Internet Protocol Security (IPSec)
Additional file information
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Article ID: 2351254 - Last Review: January 4, 2011 - Revision: 2.0