07-21-2010 01:02 PM
I have a Cisco 877W DSL router w/wireless & wires LAN. We have it configured so we can VPN in using our remote Windows XP computers via the Cisco VPN dialer.
We now have computers running Windows 7 and the Cisco VPN dialer no longer works on that OS.
What is the new process/technology required for accessing our Cisco 877W DSL router from Windows 7 computers using VPN?
I am hearing we need to use Cisco AnyConnect as well as possibly upgrade the router's firmware.
A high-level list of things I need to do would be _greatly_ appreciated!
07-21-2010 01:44 PM
IPSec VPN Client version 5.0.6 does support Windows 7 (32-bit).
Here is the release notes for your reference:
Hope that helps.
07-21-2010 04:28 PM
Thank you for the quick reply. I failed to mention that we are using Windows 7 64 bit. What would be the right solution for that OS?
07-21-2010 05:01 PM
Try using shrewsoft client ( freeshare from shrew.net --- use the lastest version for 64 bit win 7 ). also you use the cisco client for 64 bit beta version.
thanks
manish
07-21-2010 05:44 PM
Thanks, Manish. We tried the Shrew VPN client, but could never get it to connect. Plus, we heard it
was pretty unstable.
We will get the Cisco for 64 bit beta client and see how that works.
07-21-2010 05:55 PM
Rolf ! i have been using Shrewsoft on 64 bit vista ( vista can you believe it .. ) , it works like a champ. anyways , if you are using pre-shared with x-auth i can explain how you can use it.
1> place ip address of the vpn server or fqdn on the vpn site configuration tab.
2> go into authentication tab :-
a> set auth method to mutual psk + x-auth.
b> local identity -- key identifier --- place your tunnel group name here.
c> remote identity -- ip address
d> credential -- tunnel group password.
3> check the phase two tab for proper DH group ( default is group 2 ).
or easier , just import the cisco client pcf file into the shrewsoft client.
hope it helps
manish
07-21-2010 07:10 PM
Manish, it seems when we tried the Shrew VPN, we were able to import the Cisco pcf file, but the connection hung up somhow on Phase Two. The client indicated it was connected, but no traffic would pass successfully, even a ping. I will go ahead and try it again, or look into the Cisco beta release.
Thanks for your help, and stay tuned...
07-22-2010 05:56 AM
i have previously seen issues with windows 7 clients when 3 des is used, i also read on some forums that on win 7 3 des in not enabled by default
just to rule out that option, could you please try configuring aes in phase 1 and phase 2 policies and give them highest priority
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: