Cisco routing:(sound of hair being pulled out

[YONNYYOHNSON]

I cannot get to my WAN route 10.229.0.0 on a VPN tunnel. Ping fails and traceroute stops at the Cisco router.

The Cisco router is the network Gateway and traceroute stops at the VPN. Example:
TACMain#traceroute ip 10.229.66.97

Type escape sequence to abort.
Tracing the route to 10.229.66.97

1 10.10.10.9 4 msec 0 msec 4 msec
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *


When I add a route to my PC pointing to the VPN, it works.

C:\>ping 10.229.66.97

Pinging 10.229.66.97 with 32 bytes of data:

Reply from 10.229.66.97: bytes=32 time=118ms TTL=124
Reply from 10.229.66.97: bytes=32 time=110ms TTL=124
Reply from 10.229.66.97: bytes=32 time=107ms TTL=124

Ping statistics for 10.229.66.97:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 107ms, Maximum = 118ms, Average = 111ms

Here is the Cisco routing info
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.10.10.8 permanent
ip route 10.0.0.0 255.0.0.0 FastEthernet0/0 permanent
ip route 10.229.0.0 255.255.0.0 10.10.10.9 permanent
ip route 10.229.66.0 255.255.255.0 10.10.10.9 permanent

I was told that the Cisco will route to the more specific route first but it isn't happening.

[Cellus]

You probably need to change the weight/metric in the appropriate entry in the routing table so as to "force" it to use the route you want.