Incorrect Routing Table When You Connect to Some VPN Servers

This article was previously published under Q300561
This article has been archived. It is offered "as is" and will no longer be updated.
If you make a virtual private network (VPN) connection to certain non-Microsoft VPN servers, you may not be able to send data over the VPN connection. The problem also occurs if you are making a one-way dial-on-demand connection from a Windows 2000-based server that is running the Routing and Remote Access service to certain non-Microsoft VPN servers. You may be able to establish a VPN connection, but you do not have connectivity and the VPN connection is dropped after a time-out period.

This problem only occurs when the VPN client is running one of the following programs:
  • Windows 2000 that is using Internet Connection Sharing.
  • Windows 2000 Professional that has the Incoming Connections functionality turned on.
  • Windows 2000 Server that has Routing and Remote Access installed.
Standard Windows 2000-based VPN clients that are not running the Routing and Remote Access service do not experience this problem.
This problem occurs if the non-Microsoft VPN server is using the same Internet Protocol (IP) address for both its Internet Protocol Control Protocol (IPCP) server and its network interface. In this scenario, the local routing table is incorrectly updated during the connection. Although the Request for Comments (RFC) is not clear about how to handle this scenario, this scenario is not a standard implementation of VPN. Windows 2000 is not designed to handle this scenario.

Service Pack Information

To 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 Information

NOTE: Microsoft recommends that you apply the hotfix that is described in this section to only a Windows 2000-based computer that has Service Pack 3 (SP3) installed.

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.

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, submit a request to 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.The English version of this fix has the file attributes (or later) 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 tool in Control Panel.

The English version of this fix should have the following file attributes or later:
 Date         Time   Version        Size     File name --------------------------------------------------------  07-May-2003  15:24  5.0.2195.6606  159,504  Iprtrmgr.dll  07-May-2003  15:24  5.0.2195.6626  198,928  Rasppp.dll				

For standard Windows 2000 client VPN connections, do not turn on Routing and Remote Access, Incoming Connections, or Internet Connection Sharing on the VPN client computer. For Windows 2000 Routing and Remote Access one-way dial-on-demand connections, there is no workaround for this problem.
Microsoft 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.
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Identyfikator artykułu: 300561 — ostatni przegląd: 02/27/2014 21:08:48 — zmiana: 4.7

Microsoft Windows 2000 Server SP1, Microsoft Windows 2000 Service Pack 3, Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP1, Microsoft Windows 2000 Advanced Server SP2, Microsoft Windows 2000 Advanced Server SP3, Microsoft Windows 2000 Professional SP1, Microsoft Windows 2000 Professional SP2, Microsoft Windows 2000 Service Pack 3

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix kbnetwork kbwin2000presp3fix kbwin2000presp4fix kbwin2000sp3fix KB300561