Can connect but can't ping computers

[graton]

Hi guys, I installed Winroute Pro 4.2.5 on my new Windows 2000 server and everything works just great. Except for my router-to-router vpn. I set up a persistent dialup connection in Win's RRAS with a static route to the remote network. I can connect to the remote vpn router and ping the address given by their DHCP, but I can't ping any other computer on the remote network. If I disable Winroute and connect the vpn, I can ping computers at our Montreal office. As soon as I enable Winroute and connect the vpn, I can't ping anything except the DHCP address attributed to the dialup interface. Running "route print" from the command prompt shows an unexact gateway for the remote network static route (well, it seems unexact to me). I set up port mapping for TCP port 1723 and GRE (pptp) for my pptp server (Winroute system also). No packet filters for pptp. I can connect a vpn client to my vpn router and can connect also the client to the Montreal's vpn router.

 

[Ntr0P]

Can you describe the "unexact" route?

Also, do the routers provide any kind of logging that might shed some light like denied traffic or anything else useful?

 

[graton]

I added a static route for remote network 192.168.0.0 on my vpn interface.
When I run route print, this is what I get:
192.160.0.0, 255.255.255.0, 10.1.20.22, 192.168.0.22
192.160.0.22, 255.255.255.255, 127.0.0.1, 127.0.0.1
192.160.0.255, 255.255.255.255, 192.168.0.22, 192.168.0.22

192.168.0.22 is the ip address given to my vpn interface by the remote DHCP server and I can ping this address

10.1.20.22, 255.255.255.255, 192.168.0.22, 192.168.0.22
this is the address my DHCP server gave to the remote vpn interface

If I look in the RRAS routing table:
192.160.0.0, 255.255.255.0, 0.0.0.0, vpn interface
192.160.0.22, 255.255.255.255,127.0.0.1, Loopback interface
192.160.0.255, 255.255.255.255, 0.0.0.0, vpn interface

10.1.20.22, 255.255.255.255, 0.0.0.0, vpn interface