[Vpn-help] Routing problem

[Matthew Butt]

Not sure if this helps at all.. if I try and ping an IP at the end of the tunnel,  I get an unreachable error, then the next responses are from my normal internet connection (10.5.1.31 is the IP given to me by VPN).  Some IPs removed for security...

D:\>ping aa.bb.cc.dd

Pinging aa.bb.cc.dd with 32 bytes of data:
Reply from 10.5.1.31: Destination host unreachable.
Reply from 68.216.216.169: TTL expired in transit.
Reply from 68.216.216.169: TTL expired in transit.
Reply from 68.216.216.169: TTL expired in transit.

So it looks like the routes are working, but the traffic just isn't travelling.  Anyone have any ideas?

Many thanks,

Matt


------------------------------------------------------------------------

From: Matthew Butt 
Sent: Wednesday, October 28, 2009 12:04 PM
To: 'vpn-help at lists.shrew.net'
Subject: Routing problem

I'm trying to get Shrew working from a Win 7 Ultimate x64 install under VMWare ESXi to a Cisco VPN server.  Currently using Shrew 2.1.5-RC4 but this seems to happen on all versions I have tried.

I'm importing an existing PCF and connection happens fine.  The link appears to stay up with no errors in the trace logs and I'm seeing DPD responses..  However, I am not able to contact any machines on the other end of the link, by either IP or name.  The firewall rules tab in the trace util show the correct routing has been setup, but a tracert sends the data down my public internet connection, not down the VPN system.

I've also tried disabling "obtain network topology" and adding the routes manually, but still no luck.

I'm happy to provide any logfiles required.. where can I start trying to fix this problem?

Many thanks,

Matt