A. To enable WWW and FTP browsing when you connect via RAS you enable the "use default gateway on remote network" of the RAS options. This has the effect of when the connection is made a new route is added to the route list superseding the existing LAN routes so any traffic destined for a node outside your local subnet will attempt to be sent using the RAS route. This is because a metric is used to identify the number of hops needed and once connected to RAS it will have a metric 1 and existing routes will be bumped out to a metric of 2.

To solve this a persistent route can be manually added for your LAN's subnet and the associated subnet gateway. While not connected via RAS you can examine your route information using the ROUTE PRINT command:

If your network was 160.82.0.0 (your company has a class B address) and the gateway was 160.82.220.1 for your local subnet you can add a route for the LAN only and all addresses outside of 160.82.0.0 will be routed using the RAS gateway.

C:\>route -p add <ip network> mask <subnet mask> <local gateway for the route>
e.g. C:\>route -p add 160.82.0.0 mask 255.255.0.0 160.82.220.1

This would mean all addresses from 160.82.1.1 to 160.82.254.254 would be routed via 160.82.220.1 and anything else via the RAS gateway.

If you wanted to add a route for a single host (maybe your internet firewall which is on another subnet) use the following:

C:\>route -p add 192.168.248.8 mask 255.255.255.254 160.82.220.1

Notice the subnet mask of 255.255.255.254 which means only for this single host.

When connected via RAS you will still be able to access resources outside of your local subnet on the LAN with no problems.