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

MORE INFORMATION

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

Update information

The following file is available for download from the Microsoft Download Center:

Download the Update for Windows Server 2003 x64 Edition (KB914841) 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.


The following file is available for download from the Microsoft Download Center:


Download the Windows Server 2003 (KB914841) 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.


The following file is available for download from the Microsoft Download Center:

Download the Windows Server 2003 for Itanium-based Systems (KB914841) 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.


The following file is available for download from the Microsoft Download Center:

Download the Windows XP (KB914841) 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.


The following file is available for download from the Microsoft Download Center:

Download the Windows XP x64 Edition (KB914841) 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 both of the following files:

• Oakley.dll
• Nshipsec.dll

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

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Nshipsec.dll	5.2.3790.2651	393,216	02-Mar-2006	20:07	x86	SP1	SP1QFE
Oakley.dll	5.2.3790.2651	275,456	02-Mar-2006	20:07	x86	SP1	SP1QFE

Windows Server 2003, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Nshipsec.dll	5.2.3790.2651	587,776	02-Mar-2006	19:26	x64	SP1	SP1QFE
Oakley.dll	5.2.3790.2651	388,608	02-Mar-2006	19:26	x64	SP1	SP1QFE
Wnshipsec.dll	5.2.3790.2651	393,216	02-Mar-2006	19:26	x86	SP1	WOW
Woakley.dll	5.2.3790.2651	275,456	02-Mar-2006	19:26	x86	SP1	WOW

Windows Server 2003, Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Nshipsec.dll	5.2.3790.2651	805,376	02-Mar-2006	19:26	IA-64	SP1	SP1QFE
Oakley.dll	5.2.3790.2651	544,256	02-Mar-2006	19:26	IA-64	SP1	SP1QFE
Wnshipsec.dll	5.2.3790.2651	393,216	02-Mar-2006	19:26	x86	SP1	WOW
Woakley.dll	5.2.3790.2651	275,456	02-Mar-2006	19:26	x86	SP1	WOW

Update installation information

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.

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

Windows XP

Hotfix information

A 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 XP 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.

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

File name	File version	File size	Date	Time	Platform	SP requirement
Oakley.dll	5.1.2600.2859	269,824	02-Mar-2006	03:43	x86	SP2

Windows XP, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Nshipsec.dll	5.2.3790.2651	587,776	02-Mar-2006	19:26	x64	SP1	SP1QFE
Oakley.dll	5.2.3790.2651	388,608	02-Mar-2006	19:26	x64	SP1	SP1QFE
Wnshipsec.dll	5.2.3790.2651	393,216	02-Mar-2006	19:26	x86	SP1	WOW
Woakley.dll	5.2.3790.2651	275,456	02-Mar-2006	19:26	x86	SP1	WOW

Hotfix installation information

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.

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

MORE INFORMATION

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

Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with 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 your x64-based version of Windows. 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.

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: