Article ID: 259171 - Last Review: October 31, 2006 - Revision: 1.1

Client VPN IP Address Must Be Used When You Add Static Routes for Windows 2000 VPN Interface

This article was previously published under Q259171
Expand all | Collapse all

SYMPTOMS

The Windows 2000 Resource Kit incorrectly states that the IP address of the VPN server should be used as the gateway address when adding static routes for the VPN interface.

CAUSE

This problem can occur if the host subnet mask is 255.255.255.255 because only the client's VPN IP address can be used for the gateway.

RESOLUTION

To resolve this problem, the gateway IP address in the route commands for each intranet route is the IP address assigned by the VPN server to the client's virtual interface, not the IP address of the VPN server's Internet interface. You can only determine the IP address of the VPN client's virtual interface when the client is connected by double-clicking the virtual private networking connection object when the VPN connection is active. In the resulting Status dialog box, click the Details tab.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
254231  (http://support.microsoft.com/kb/254231/EN-US/ ) Change in Remote Access Route Behavior with Windows 2000

APPLIES TO
  • Microsoft Windows 2000 Server
Keywords: 
kbdocerr kbprb KB259171
 

Article Translations

 

Related Support Centers