Static routes for VPN Clients

  • Thread starter Thread starter KJ
  • Start date Start date
K

KJ

I need some help with RRAS VPN clients and their static routes.

I have 2 networks
Network A 192.168.1.0/24
Network B 192.168.2.0/24

Router on Network A IP is 192.168.1.1
Router on Network B IP is 192.168.2.1

RRAS Server IP 192.168.1.200

Currently I have RRAS configured to allow PPTP clients access
configured on a Windows 2000 server located on Network A. IP
addresses are handed out to the clients via DHCP server not a set
pool.

When I connect to Network A using vpn client I can gain access to
anything and everything on Network A. However I cannot gain access to
anything on Network B.

If I add the following to my route tables on my VPN Client
route add 192.168.2.0 mask 255.255.255.0 192.168.1.1
route add 192.168.2.255 mask 255.255.255.255 192.168.1.1

I am then able to gain access to both Network A and B.

I cannot seem to find a way to push those routes to the VPN client
when they log in. I tried adding it to the apply static route under
the Dial in tab in active directory but that did not seem to do
anything. I tried to add it in the Static route section of the RRAS
msc but that did not seem to do anything either. I know I am missing
something really simple but I just do not know what it is.

Could someone here please help.

Thanks
KK
 
Your RRAS Server should have 2 interfaces: 1 for the Network A and another
for Network B. Only then client which VPN into the RAS Server can contact
machines in the Network B.

As per the below info, the RRAS Server seems to have only 1 interface and
that is in Network A.

BTW, which network is your client on? (Because by modifying the routes on
the client, you are able to access Network A and B)
 
You can use Connection Manager client to solve this problem. For more
information you can look at:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_CMAKtopnode.asp

It has a specific section on updating route table -
http://www.microsoft.com/resources/.../2003/standard/proddocs/en-us/cmak_ops_54.asp

Note that routing table update feature was added only with CMAK 1.3 which
ships with WS03. The CM profile created from CMAK 1.3 can, however, be
installed on Win2000, winxp, win9x.

Hope this helps,
Thanks,
Dinesh.
 
Back
Top