[vpn-help] Please Help Test Possible Cisco Interoperability Improvements ...

[James Rudd]

Hi Matthew,
 I just tried 2.1.6 beta 3 on Windows 7 x64 and it has allowed me to
connect and stay connected to our Cisco VPN for the first time.
(Unfortunately I do not know what type of Cisco is used)
I used the default settings, and did not try out workaround #1,
suggesting that the connection problems I have had with previous
versions were caused by either the version or firewall check.

Thanks for great work,
 James


On Thu, Dec 17, 2009 at 7:28 PM, VPN Client Product Support
<vpn-help at lists.shrew.net> wrote:

> 2) The Cisco gateway utilizes client "application version" access rules
> that only allow specific versions of the client to connect. The Shrew
> Soft VPN Client wasn't reporting version information, so gateways that
> enforced this check would force a disconnect after authentication.
>
> SOLUTION: Beginning with 2.1.6 Beta 2, the Shrew Soft VPN client will
> send an application version identical to the Cisco VPN client version
> 4.8.01 which is the latest 4.x version. If that version of the Cisco VPN
> client is allowed to connect, so will the Shrew Soft VPN client.
>
> 3) The Cisco gateway utilizes client "firewall type" access rules that
> only allow VPN Clients that enforce local firewall security policies to
> connect. The Shrew Soft VPN Client wasn't reporting a firewall type, so
> any gateway that enforced this check would force a disconnect after
> authentication.
>
> SOLUTION: Beginning with 2.1.6 Beta 2, the Shrew Soft VPN client will
> send an unknown firewall type. This should allow the client to connect
> although we don't actually enforce the firewall policies. I'm still
> struggling with the ethical implications of this change so don't be
> surprised if I revert this change before the final release.