How to simplify the creation and maintenance of Internet Protocol (IPsec) security filters in Windows Server 2003 and Windows XP

This article describes an update that you can apply to simplify the creation and maintenance of Internet Protocol security (IPsec) filters in Microsoft Windows Server 2003. This article also includes description of a hotfix for Microsoft Windows XP that simplifies the creation and maintenance of Internet Protocol security (IPsec) filters in Microsoft Windows XP.

The Windows Server 2003 update and the Windows XP hotfix add functionality to Windows that enables you to use an IPsec "Simple Policy." For most environments, the installation of this update and hotfix lets you reduce the number of IPsec filters that are required for a Server Isolation deployment or for a Domain Isolation deployment. You can reduce the number of IPsec filters from many hundreds of filters to only two filters.

Server Isolation and Domain Isolation are two major network security deployment scenarios that can exist together with a Windows Firewall deployment. These two deployment scenarios are based on the use of IPsec to isolate network traffic. However, the number of IPsec filters that administrators must create and maintain in these two scenarios frequently acts as a disincentive. Currently, administrators who want to implement Server Isolation or Domain Isolation by using IPsec must create an isolation policy that contains a significant number of rules. Frequently, administrators must create 300 to 500 rules. For example, rules are required to specify the subnets to isolate, the services that are required by domain controllers and DNS servers, and so on.

The Windows Server 2003 update and the Windows XP hotfix removes the requirement for explicit network infrastructure permit filters and for special filters to help secure a subnet. To remove this requirement, the update and the hotfix introduces enhanced behavior for the "fallback to clear" functionality. The fallback to clear functionality is enhanced in the following two ways:

• The fallback to clear time-out value is reduced from 3 seconds to 500 milliseconds (ms).
• Credential and policy mismatch failures are now permitted to use the fallback to clear functionality.

Windows Server 2003 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:

Windows Server 2003 update information

The following files are available for download from the Microsoft Download Center:

Update for Windows Server 2003, x86-based versions

Download the 914841 package now.

Update for Windows Server 2003, x64-based versions

Download the 914841 package now.

Update for Windows Server 2003, Itanium-based versions

Download the 914841 package now.
Release Date: April 7, 2006

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

You must be running Windows Server 2003 Service Pack 1 (SP1) to apply this update.

Restart requirement

You do not have to restart the computer after you apply this update. However, you must restart the Policyagent service to apply the changes after you apply this update.

Update replacement information

This update does not replace any other updates. However, this update replaces earlier versions of the Oakley.dll file.

Update installation information

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:

By default, the functionality that this update package provides is not enabled. To enable the functionality that this update provides, you must modify the following registry subkey:This IKEFlags registry entry is a REG_DWORD type. You must manually create this entry if it does not already exist.

Important This registry entry is interpreted as a bit-mask. Therefore, if the current value of the entry is not 0x0, we recommend that you carefully consider any modifications that you make to the entry to preserve existing settings.

To enable the Simple Policy functionality that this update provides, you must set the following bits in the IKEFlags registry entry:This value contains two individual settings that you can independently enable, if you require this level of specificity. These two values are as follows:

• 0x4
  This setting enables improved fallback to clear behavior.
• 0x10
  This setting adds more notification messages (notifies) to decrease the fallback to clear time in a Domain Isolation boundary zone scenario.

Note We recommend that you use a value of 0x14 unless you have a specific requirement to limit the sending of Internet Key Exchange (IKE) "notifies."

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, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

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

You must be running Windows XP Professional with Service Pack 2 (SP2) to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the Policyagent service to apply the changes after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes. However, this hotfix replaces earlier versions of the Oakley.dll file.

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 XP, x86-based versions

Hotfix installation information

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:

By default, the functionality that this hotfix package provides is not enabled. To enable the functionality that this hotfix provides, you must modify the following registry subkey:This IKEFlags registry entry is a REG_DWORD type. You must manually create this entry if it does not already exist.

Important This registry entry is interpreted as a bit-mask. Therefore, if the current value of the entry is not 0x0, we recommend that you carefully consider any modifications that you make to the entry to preserve existing settings.

To enable the Simple Policy functionality that this hotfix provides, you must set the following bits in the IKEFlags registry entry:This value contains two individual settings that you can independently enable, if you require this level of specificity. These two values are as follows:

• 0x4
  This setting enables improved fallback to clear behavior.
• 0x10
  This setting adds more notification messages (notifies) to decrease the fallback to clear time in a Domain Isolation boundary zone scenario.

Note We recommend that you use a value of 0x14 unless you have a specific requirement to limit the sending of Internet Key Exchange (IKE) "notifies."

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.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site: