Article ID: 931322
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003 Service Pack 2, when used with:
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Standard x64 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, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003 SP1, when used with:
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
Beta Information
This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.
SYMPTOMS
On a Microsoft Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2)-based computer that has the Routing and Remote Access service enabled and configured to use the Network Address Translation (NAT) functionality. When the Windows Server 2003-based computer is under heavy load, you may experience one of the following symptoms:
- Your computer automatically restarts.
After you log on, you receive the following error message:
If the error message still appears and if you want to see the data that the error report contains, click the click here link at the bottom of the message box. Then, you see error signature information that may resemble to the following:
BCCode : 000000D1 BCP1 : parameter1 BCP2 : 0x00000002 BCP3 : 0x00000000 BCP4 : 0xf27b4e8e OSVer : 5_2_3718 SP : 0_0 Product : 272_3
- You receive the following error message:
- When you view the System log in Event Viewer, you may notice an event ID 1003 entry with information that resembles the following:
Notes
- The symptoms of a Stop error vary according to your computer's system failure options. For more information about how to configure system failure options, click the following article number to view the article in the Microsoft Knowledge Base:
307973 HOW TO: Configure Recovery Options in Windows
- The four parameters that are inside the parentheses of the technical information for the Stop error vary according to the computer's configuration.
- Not all Stop 0x000000D1 errors are caused by the problem that is described in this article.
CAUSE
The problem may occur if a user uses IP preservation in a Windows Server 2003-based computer that is under heavy load and uses Windows Server 2003 SP1 or Windows Server 2003 SP2. The IP NAT driver may incorrectly process the reset interface request in Windows Server 2003 SP1 and in Windows Server 2003 SP2.
RESOLUTION
Hotfix Information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed on the computer. For more informationabout how to obtain Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2), 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
914961 General information regarding Windows Server 2003 Service Pack 2
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 with SP1, x86-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ipnat.sys | 5.2.3790.2862 | 103,424 | 16-Jan-2007 | 10:51 | x86 | SP1 | SP1QFE |
| Ipnat.sys | 5.2.3790.4006 | 119,296 | 16-Jan-2007 | 13:29 | x86 | SP2 | SP2QFE |
Windows Server 2003 with SP1, x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ipnat.sys | 5.2.3790.2862 | 156,160 | 16-Jan-2007 | 04:34 | x64 | SP1 | SP1QFE |
| Ipnat.sys | 5.2.3790.4006 | 180,736 | 16-Jan-2007 | 04:40 | x64 | SP2 | SP2QFE |
Windows Server 2003 with SP1, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ipnat.sys | 5.2.3790.2862 | 350,208 | 16-Jan-2007 | 04:35 | IA-64 | SP1 | SP1QFE |
| Ipnat.sys | 5.2.3790.4006 | 383,488 | 16-Jan-2007 | 04:40 | IA-64 | SP2 | SP2QFE |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about the terms that are used to describe software updates, 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
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:
Keywords: kbbug kbfix kbqfe kbpubtypekc kbwinserv2003sp1fix kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB931322
