0

I have a gateway<->gateway IPSEC VPN running between 2 offices and the first gateway (BiPAC 7404VGO) will also host PPTP VPN connections as well.

I need to be able to route PPTP traffic with a destination to the second gateway through the gateway VPN to services in that second network.

At this stage no routing occurs when trying to access the second office subnet from the PPTP VPN.

All clients are using Windows XP or above and there is an SBS2003 server on the first subnet attached to the first gateway. At this point I have a choice of using SBS2003 PPTP termination or router PPTP termination for incoming client connections. At the moment I have the router as the PPTP endpoint.

I suspect that where it is falling down is the routing on the client itself. I think I need to let each client know when they connect that they need to send traffic for the second subnet through the PPTP VPN so it can be routed to that subnet. I don't want to use the PPTP connection as the default gateway as this would have large performance issues.

Is there a way to dynamically allocate a static route on the client when they establish a PPTP connection to the router (or SBS server) so traffic can be routed correctly?

1
Contributor
1
Reply
4
Views
6 Years
Discussion Span
Last Post by heals1ic
0

Update -

Further to this I have manually added a routing entry into the clients routing table and can now reach the second subnet.

route add 192.168.2.0 mask 255.255.255.0 192.168.0.35 metric 2

I need this routing table entry to update in each client when they connect with PPTP. Not always will the gateway be 192.168.0.35 as this is issued by DHCP from the SBS 2003 server so this would be hard to batch.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.