Return to index


RAS wasn't designed to provide connectivity between LANs.

It works fine on the client end. You can use an RAS client machine with IP forwarding enabled and the "Use default gateway on remote network" option set to allow the client's LAN to access the dial up server to which the RAS client is connected. If that dial up server is capable of routing incoming dual up connections through to other networks and willing to do so, then machines on the RAS client's network can be provided access to those remote networks through the RAS client's connection.

The problem is with RAS server. There is no provision equivalent to RAS client's "Use default gateway on remote network" in RAS Server. So RAS Server is unable to add the necessary routes once the connection is established. You can manually add the route(s), but you will always have to do so. They cannot be made persistent and RAS Server provides no easily available trigger event to allow you automate the route additions.

There are also some registry pokes you need to make to allow RAS to fully act as a router. You will find more information on using RAS as a router in the Tech section of and in the MS KB article Q121877 "Using RAS for Routing of IP Packets".

In most cases, your best bet (assuming both RAS machines are running NT Server) is to install Routing & RAS. RRAS allows the definition of route, filters, etc. based on a defined, but not necessarily established, RAS connection. In other words, you define a phonebook entry for your connection, as with normal RAS. Then RRAS allows you to define routes, etc. that are to be added, whenever that connection is established. RRAS also allows the creation of Dial On Demand connections.