Hi, Matthew:
I only have 2.1.6 installed, and I can see a line:
ii : generating IPSEC security policies at REQUIRE level
in the log. Should I try 2.1.7 instead? Is it stable enough for daily use?
Thanks
RJX
Matthew Grooms wrote:
On 9/13/2010 7:26 AM, Jim R wrote:
Hi,:
I see there were some discussions on how to support this in the mailing
list, I'm wondering what is the support included in 2.1.6 release
version? I tried it, it seems the only way to make it work is to use the
include 0.0.0.0 policy trick, if I don't do this, the VPN connection can
be established, but I couldn't connect to any machine on the VPN.
VPN Client Version: 2.1.6-release
Windows OS Version: Win7 Pro x64
Gateway Make/Model: Cisco Systems, Inc./VPN 3000 Concentrator
Gateway OS Version: 4.1.5
Interesting. When you connect using the 2.1.7 version and look at the
debug level log output, what does the line say just before policy
generation? For example ...
ii : generating IPSEC security policies at UNIQUE level
If your connecting to a Cisco gateway, it should default to REQUIRE
level instead of shared. This should avoid the 0.0.0.0 policy trick
requirement.
-Matthew
_______________________________________________
vpn-help mailing list
[email protected]
http://lists.shrew.net/mailman/listinfo/vpn-help
