Supply route to VPN clients

My office LAN (192.168.42.0/24) is connected to a remote site
(192.168.43.0/24) through a VPN connection.
We also have a VPN server (Windows 2003) in the main LAN to allow our users
access to our network.
When I connect to the VPN server from home (Windows XP), I get a valid IP
address (192.168.42.X) and everything works fine, but I can't access the
remote site, because my Windows doesn't know how to reach the
192.168.43.0/24 subnet: it only knows about the 192.168.42.0/24 one.
If I manually add a route, telling it to reach the remote site through the
VPN connection to the main LAN (ROUTE ADD 192.168.43.0 MASK 255.255.255.0
192.168.42.X), everything is ok; but I need to do this manually each time I
connect to the office. Is there any way to make my RRAS server automatically
supply this route to its clients when they connect?
Thanks

Massimo

"Massimo" <(E-Mail Removed)> ha scritto nel messaggio
news:ODDnu%(E-Mail Removed)

> My office LAN (192.168.42.0/24) is connected to a remote site
> (192.168.43.0/24) through a VPN connection.
> We also have a VPN server (Windows 2003) in the main LAN to allow our
> users access to our network.
> When I connect to the VPN server from home (Windows XP), I get a valid IP
> address (192.168.42.X) and everything works fine, but I can't access the
> remote site, because my Windows doesn't know how to reach the
> 192.168.43.0/24 subnet: it only knows about the 192.168.42.0/24 one.
> If I manually add a route, telling it to reach the remote site through the
> VPN connection to the main LAN (ROUTE ADD 192.168.43.0 MASK 255.255.255.0
> 192.168.42.X), everything is ok; but I need to do this manually each time
> I connect to the office. Is there any way to make my RRAS server
> automatically supply this route to its clients when they connect?

Any thoughts on this?

Massimo

You may want to do this on VPN server. If I remember correctly, IP
routing>static routes.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Massimo" <(E-Mail Removed)> wrote in message
news:ODDnu%(E-Mail Removed)...
> My office LAN (192.168.42.0/24) is connected to a remote site
> (192.168.43.0/24) through a VPN connection.
> We also have a VPN server (Windows 2003) in the main LAN to allow our
> users
> access to our network.
> When I connect to the VPN server from home (Windows XP), I get a valid IP
> address (192.168.42.X) and everything works fine, but I can't access the
> remote site, because my Windows doesn't know how to reach the
> 192.168.43.0/24 subnet: it only knows about the 192.168.42.0/24 one.
> If I manually add a route, telling it to reach the remote site through the
> VPN connection to the main LAN (ROUTE ADD 192.168.43.0 MASK 255.255.255.0
> 192.168.42.X), everything is ok; but I need to do this manually each time
> I
> connect to the office. Is there any way to make my RRAS server
> automatically
> supply this route to its clients when they connect?
> Thanks
>
> Massimo
>

dido robert,

all you have to do is do it on the vpn server since the clients are using
the vpn server as their gateway.


"Massimo" <(E-Mail Removed)> wrote in message
news:ODDnu%(E-Mail Removed)...
> My office LAN (192.168.42.0/24) is connected to a remote site
> (192.168.43.0/24) through a VPN connection.
> We also have a VPN server (Windows 2003) in the main LAN to allow our
users
> access to our network.
> When I connect to the VPN server from home (Windows XP), I get a valid IP
> address (192.168.42.X) and everything works fine, but I can't access the
> remote site, because my Windows doesn't know how to reach the
> 192.168.43.0/24 subnet: it only knows about the 192.168.42.0/24 one.
> If I manually add a route, telling it to reach the remote site through the
> VPN connection to the main LAN (ROUTE ADD 192.168.43.0 MASK 255.255.255.0
> 192.168.42.X), everything is ok; but I need to do this manually each time
I
> connect to the office. Is there any way to make my RRAS server
automatically
> supply this route to its clients when they connect?
> Thanks
>
> Massimo
>

"Robert L [MS-MVP]" <(E-Mail Removed)> ha scritto nel messaggio
news:(E-Mail Removed)

> You may want to do this on VPN server. If I remember correctly, IP
> routing>static routes.

No, those are the static routes for the server itself... and, anyway, a
route to the remote LAN is already specified there.

Massimo

"Jimmy Boy" <(E-Mail Removed)> ha scritto nel messaggio
news:%(E-Mail Removed)

> all you have to do is do it on the vpn server since the clients are using
> the vpn server as their gateway.

Unfortunately, that's not the case: a VPN client doesn't use the VPN server
as its default gateway, since it has to continue reaching the Internet when
the VPN is up. A VPN client uses the server as gateway only for the LAN
accessed through the VPN, i.e., in this case, 192.168.42.0/24. I want to
tell clients they should use the VPN server as gateway for 192.168.43.0/24
also.

Massimo

"Massimo" <(E-Mail Removed)> ha scritto nel messaggio
news:ODDnu%(E-Mail Removed)

> Is there any way to make my RRAS server
> automatically supply this route to its clients when they connect?

I found a workaround: I used the option for specifying the static route on
the DHCP server used by RRAS to supply addresses to clients; now that route
is also supplied to all of the LAN clients, but I don't think this is a
problem.
Anyway, is there a way to make the RRAS server supply the route to its
client without setting it on the DHCP server?

Massimo