Remote Access Client Issues

  • Behavior based on Use default gateway on remote network selections.
  • Use default gateway on remote network example.

Behavior based on Use default gateway on remote network selections

If the RAS client is connected to a local network with a NIC and you are using RAS, the destination host is located using the following process:

If the Use default gateway on remote network in the TCP/IP options of the RAS PhoneBook entry used to dial the remote network:

Is enabled, and the:

Destination Address is: The packets are sent via the:
On the same subnet as the RAS Server's NIC NIC.
Not on the same subnet as the RAS Server's NIC RAS connection to the default gateway assigned by the RAS server.

Is not enabled, and the:

Destination Address is: The packets are sent via the:
On the same subnet as the RAS Server's assigned RAS IP address RAS connection.
Not on the same subnet as the RAS server's assigned RAS IP address RAS server's NIC.

Use default gateway on remote network example

  • Your LAN is divided into two Class C subnets, 1.1.1.x and 1.1.2.x,
  • You configure your computer on the 1.1.1.x subnet to use RAS with the Use default gateway on remote network option enabled.

All packets that you send to the 1.1.2.x subnet will be sent via the RAS connection...not your computer's NIC.

To route packets correctly:

  • Use the Windows route.exe command to add a static route to your TCP/IP route table
  • The static route should instruct Windows to send packets intended for the 1.1.2.x subnet to a router on the 1.1.1.x subnet.

Consult Microsoft Windows documentation for details about the ??route.exe command.