I didn't attempt much trouble shooting as I'd spent an afternoon working to track down why SA's were not being created. The Kasperski thing was a last ditch attempt really. The only troubleshooting I tried was to remove the NDIS binding reboot and reinstall 2.1.6beta4. When that didn't fix it I removed the AV software and the tunnel started passing traffic on the next reboot. I couldn't find any warnings in the Kasperski software about blocking any traffic. On install it did warn about a suspicious driver install. I selected the ignore this threat options and the install continued.
"Date: Thu, 11 Feb 2010 17:18:21 +0000 From: Dave Roberts <[email protected]> Subject: Re: [vpn-help] vpn-help Digest, Vol 41, Issue 18 To: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" If you re-install or "repair" Kaspersky after installing Shrew, it will work. Date: Thu, 11 Feb 2010 10:40:56 -0600 From: "MATT PIERCE" <[email protected]> Subject: [vpn-help] Kasperski AV 2010 causes connection issue To: <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" I had an issue on a client system where Kasperski AV 2010 causes issues with a client connection. The system I worked with was Win7 X64 Home Premium. The tunnel would connect but would not create SA's. Routes and interfaces were all good. The Kasperski software adds NDIS6 driver bindings. I removed those and rebooted but was unable to pass traffic. Removing Kasperski fixed the issue. It's possible that the network protection component could be removed but I wasn't able to test that." _______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help
