[vpn-help] VPN client causing "next token code" mode on RSA appliance

[Colin Bowern]

The company I am connecting to is using the Cisco VPN Client 5.0.07.0440 which is no longer supported and recently stopped working on my Windows 8 installation. I am working on the trial of Shrew Soft VPN Client 2.2.2 to find a workaround to get IPSec VPN on Windows 8.
Since using the Shrew Soft client I have experienced several times where I am unable to connect with the client returning a user authorization failed message.  Working with the VPN admins we have determined that the client is triggering my user profile to go into "Next Token Code" mode with the RSA appliance.  The workaround is to use the Cisco client to connect and satisfy the next token code request, then disconnect and connect once the token code cycles.  It seems that the Shrew Soft client does not recognize the next token code request.
Here are the details of the VPN:Cisco ASA 5510RSA SecurID Appliance 3.0 (running latest code)
My token is an RSA SecurID SID800
Not sure if this is a bug or not but with five days left in the trial I'd like to get a sense of where this stands before I make a decision to commit to purchasing the Shrew Soft client.
Thanks,Colin 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.shrew.net/pipermail/vpn-help/attachments/20130726/bc1a3d59/attachment.html>