I haven't heard anything back regarding this issue. I have done further testing and found the following. When I change the policy tab from "Obtain Topology Automatically" to manually adding networks only the first network listed will work.<br>
<br>For example, I added three networks, 172.16.0.0, 172.19.0.0, and 192.168.38.0. I can ping devices existing in whichever network is listed first in the policy tab. The other two networks timeout.<br><br>When I re-check obtain topology automatically then the same thing happens, it detects all the networks and adds the routes but only the first one will work.<br>
<br>Still struggling with this problem and would desperately like to get this VPN to work on windows 7 x64. Any help would be greatly appreciated.<br><br>Thanks,<br><br>Chris<br><br><div class="gmail_quote">On Wed, Aug 5, 2009 at 11:08 AM, Chris Yates <span dir="ltr"><<a href="mailto:chris.a.yates@gmail.com">chris.a.yates@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br><br>I just started using this VPN client. I have two main issues.<br><br>1) I am unable to access a couple networks which work fine when using the cisco VPN client. These are two class B networks which routes are setup on my cisco ISR. I checked that both the cisco vpn client and shrew are creating the static routes when connecting to the VPN. However, I can't ping anything in those networks while using shrew. The main difference is that I'm using cisco vpn client on a 32 bit windows xp install and shrew on a 64 bit windows 7 install. Any ideas why this might be happening?<br>
<br>2) Is there a way to save my password and have shrew automatically connect on bootup? I am always connected to this VPN when the computer is on.<br><br>Thanks!<br><br>-<br><font color="#888888">Chris<br><input type="hidden"><input type="hidden"><div>
</div>
</font></blockquote></div><br>