A "STOP 0xA" Error Message Occurs When You Use Routing and Remote Access with NAT and VPN (318437)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q318437 SYMPTOMS
If you use the Routing and Remote Access feature of Windows 2000 and you also use virtual private networking (VPN) and network address translation (NAT) functionality on the same computer, you may receive the following error message:
STOP: 0x0000000a (0x00000098, 0x00000002, 0x00000001, 0x80464659
CAUSE
If an IP packet that is sent through NAT is updated by NAT, the reference count for the routes is not updated correctly. The cleanup routine does not work because of the inaccurate reference count.
RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------
19-Nov-2001 16:42 5.0.2195.4667 118,896 Afd.sys
22-May-2002 17:24 5.0.2195.5823 313,232 Tcpip.sys
30-Jul-2001 20:15 5.0.2195.3988 16,240 Tdi.sys
22-May-2002 17:26 5.0.2195.4874 105,232 Msafd.dll
22-May-2002 17:26 5.0.2195.4874 17,680 Wshtcpip.dll
WORKAROUND
To work around this problem, move the NAT to a different server that does not accept VPN connections.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
Modification Type: | Minor | Last Reviewed: | 10/5/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbWin2kSP4fix kbbug kbfix kbWin2000preSP4Fix kbNetwork KB318437 |
---|
|