Can't ping each other in a demand dial VPN

Chicago Area Laptop for rent: $35 per day plus $10 for additional day

Can’t ping each other in a Demand Dial VPN

Remote router no the return static route

Q1: I have a pressing networking issue, and I've tried everything to get it running.

The end result must be that computers on the local network can access a server via TCP which is located in a remote network which is running a PPTP server.

The solution I can see without destroying the existing network is to drop a new box running RRAS into the network, use demand dial to connect to the remote VPN, and route LAN traffic over that box.

Here's a picture of my current setup

Local LAN
192.168.1.0/24
______|_______________________
| | |
Router RRAS Box Test Client
192.168.1.1 192.168.1.3 192.168.1.103
| | GW: 192.168.1.1
Internet Remote Site
x.x.x.x 192.168.0.0/24
|
Remote Server
192.168.0.3

Currently I have the setup I've mentioned above, and have setup a static route on the LAN Router (192.168.1.1)
192.168.0.0/24 --> 192.168.1.3

From the RRAS server I can ping devices on the 192.168.0.0 network

The problem I'm having is when I do a ping from the test client I get no response, when I do a trace route I get the path

192.168.1.1
|
192.168.1.3
|
*********

From my perspective it looks like the traffic is getting sent to the server, but is not passing.

The server is a fresh install, stock config, no domain and I've simply followed the wizard to setup the demand dial VPN.

Never having done this before I've reached the end of my knowledge and am in need of an expert.

Please let me know if you have a potential solution.

Thank you,

Lee

Another note,

The default gateway of the RRAS box is the 192.168.1.1 router.

Not sure if that matters, but it is the preferable configuration.

A1: Sounds like routing issue. have you enabled the IP routing? this troubleshooting may help,

routing issues on VPN
Can't access the remote network from VPN clients ...
http;//www.chicagotech.net/routingissuesonvpn.htm

Q2: I agree, it looks to be a routing issue. It definitely looks like it cannot route between the virtual WAN adapter and the local LAN adapter.

"Enable IP routing" is checked. I've seen that document in my searches, and I've tried their recommendations. Unless I'm missing something obvious.

I'd love to attach some screen shots for you guys, is there a way with this forum, or do I need to post them on a web-site and link to them?

A2: Posting the routing table here may help.

Q3: The problem was that the routing table on the remote server was lacking the return static route.