Demand Dialing Cannot Be Triggered with NAT If There Is a Destination Port Number in a Filter (296529)
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 Q296529 SYMPTOMS
If you configure network address translation (NAT) on a Windows 2000-based server, the Demand-dial interface cannot be initialized with a destination TCP port number from a client computer that is connected to the private local area network (LAN). For example, if you configure TCP port 80 as the destination port in the Demand-dial interface, the client cannot initialize NAT dialing by using "telnet IP_Address 80."
CAUSE
This problem occurs because Ipnat.sys passes the IP frame address to Ipfltdrv.sys instead of to the protocol layer (such as TCP or UDP).
RESOLUTIONTo resolve this problem, obtain the latest service pack for 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
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
----------------------------------------------------
18-May-2001 19:59 5.0.2195.3615 65,712 Ipnat.sys
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 Windows 2000 Service Pack 3.
| Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbnetwork kbWin2000PreSP3Fix kbWin2000sp3fix KB296529 |
|---|
|