Article ID: 317025 - View products that this article applies to.
This article was previously published under Q317025
After you use a Virtual Private Network (VPN) connection to log on to a server that is running Routing and Remote Access, you may be unable to connect to the Internet.
This issue may occur if you configure the VPN connection to use the default gateway on the remote network. This setting overrides the default gateway settings that you specify in your Transmission Control Protocol/Internet Protocol (TCP/IP) settings.
To resolve this issue, configure the client computers to use the default gateway setting on the local network for Internet traffic and a static route on the remote network for VPN-based traffic.
NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
Step 1: Configure the Server That Is Running Routing and Remote Access to Use a Static IP Address Pool
Windows 2000 Server
Windows NT Server 4.0
Step 2: Configure the VPN Client TCP/IP PropertiesTo disable the Use Default Gateway on Remote Network setting in the VPN dial-up connection item on the client computer:
Step 3: Connect to the Server That Is Running Routing and Remote AccessOn the client computer, connect to the Internet, and then establish a VPN connection to the server that is running Routing and Remote Access.
NOTE: You cannot connect to resources on the remote network because you have disabled the Use Default Gateway on Remote Network setting in the VPN TCP/IP configuration.
Step 4: Add a Static Route on the ClientAdd a static route on the client computer that uses the following configuration:
140859For example, to add a static route to a network that has the IP address of 192.168.10.0, the subnet mask of 255.255.255.0, and the gateway (the first IP address of the range assigned to the static IP address pool) of 192.168.1.1, type the following command at the command prompt, and then press ENTER:
(http://support.microsoft.com/kb/140859/EN-US/ )TCP/IP Routing Basics for Windows NT
route -p add 192.168.10.0 mask 255.255.255.0 192.168.1.1NOTE: If you use the -p switch with Windows 2000 or Windows NT 4.0, the route is made "persistent." Use this switch to ensure that the routing entry is preserved when the computer is restarted.
NOTE: The -p switch is not supported on either Microsoft Windows Millennium Edition-based, Microsoft Windows 98-based, or Microsoft Windows 95-based computers.
To work around this issue, create a batch file that contains the necessary route add command, and then configure it to run each time that a client connects to the VPN Server.
For additional information about how to use static routes, click the article number below to view the article in the Microsoft Knowledge Base:
178993For additional information about how to configure a VPN server, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/178993/EN-US/ )How to Use Static Routes with Routing and Remote Access Service
(http://support.microsoft.com/kb/308208/EN-US/ )HOW TO: Install and Configure a Virtual Private Network Server in Windows 2000
Article ID: 317025 - Last Review: March 2, 2007 - Revision: 1.3