I own a Linksys WRVS4400 and have used it for sometime with the QuickVPN client. I have now added two computers running Windows 7, a 32bit and 64bit version. I am running the latest versions of firmware and QuickVPN software but can not get it to connect in Windows7. The software will load but hangs at "Verifying Network" before it times out. I realize that I am not the only person with this issue and am a little concerned that Cisco does not offer a version that is Windows 7 compatible. This is a critical issue and may cause me to investigate other hardware options.
Is it possible to use a third party client to connect to the router though QuickVPN? Is there possibly a beta version of a new Cisco client that may work with Windows 7?
Any help or guidance would be greatly appreciated.
Thank you for visiting the Cisco Community Forum,
If everything has been working correctly until the installation of Windows 7, it may be related to the Windows firewall blocking ICMP requests directed at that PC.
Here is a quote on allowing PING to the PC:
"Control Panel --> System and security --> Windows Firewall --> Advanced settings --> Inbound rules --> New rule --> custom rule
in Protocol and ports: Protocol: ICMPv4
on the same panel go to customize, choose "Specific ICMP types", check the box "echo request"
next... next... and save it." http://social.answers.microsoft.com/Forums/en-US/w7network/thread/5aff5f8d-f138-4c9a-8646-5b3a99f1cae6
I raelly appreciate your quick response to my question. I went through the steps to create the new rule on my Windows 7 PC. I am able to ping my domain as I was always able to. When I open the QuickVPN client (v22.214.171.124) it will be connecting but always hangs at "Verifying Network". Should this version work with Windows 7? Looking at other posts such as https://www.myciscocommunity.com/message/20474;jsessionid=C06B7E323D68B806A665A070F2790101.node0 it seems that the client may not work.
I am using Norton Internet Security 2010 for my software firewall, not the native firewall in Windows 7. Can you recommend what I need to set up in NIS 2010?
This had been working fine from my XP laptop, but since installing Win7 on the laptop, I get the same problem described here. The router shows it as connected, but the client Win7 laptop is hung on "Verifying Network". Then "the remote gateway it not responding. Do you want to wait." If you say yes, it continues to hang on "verifying network".
As far as your situation at the moment, Cisco does not support Windows 7 with the quickvpn utility. Have you tried the fix that was posted previously to your post and give that an opportunity to work. At the moment I don't have an ETA on when windows 7 will be supported with the quickvpn utility.
Yeah i apologize, but as of yet we don't have the quickVPN working with windows 7. We are waiting for the design team to release the firmware. Sorry for the inconvenience.
Check the forums or the cisco site for an update. I am sure someone will state something on the forum about the release.
What is the ETA on when it WILL be working? I really need it to be working before January 2010!!! Is there a possibility of having an updated firmware for the RVS4000 router (and all other small business routers) that works with the native Windows 7 VPN networking?
I'm bumping this to get an update. I have Win7 64 bit and can't even run the installer for QuickVPN. This is my last app that's causing me to hold onto an XP VM for the sole purpose of being able to VPN to my home network.
Otherwise, can someone provide a workaround or alternative VPN app that I can use on Win7 to get into my 4400 VPN router?
Check out this posting as well. Well worth a look at using the native IPSec client in windows 7. Just wish I had a powerful enough PC that would accept windows 7 so i could validate the procedure in the posting below; Even though the posting mentions RV042, it sure is worth a go to try it for the WRVS4400N
Good to hear. For those who don't like to dig too much (since search doesn't find it), here is the direct link:
(cisco login still required)
Thanks, the link helped find it much easier.
Unfortuately, I installed it and have the exact same results as I did with 1.3x on Win7 Pro.
It seems to connect OK, but hangs on remote gateway not responding. The following comment is in the PDF that came with the download, however, I can't ignore it and use the connection. If I say "no", it disconnects, if I say "yes" and try to run a remote desktop session, it can't connect. This is exactly the situation with 1.3x. I have double checked my Norton Internet Security setting and it appears to be set to allow all. Any ideas on how to get this to work??
While a QuickVPN tunnel is connected, the following message may appear:
"Remote Gateway is not responding, do you want to wait?" This issue occurs
when the remote QuickVPN Server is not responding to the ping sent by the
QuickVPN Client. This issue may be caused by the remote QuickVPN Server
temporarily overloaded. Users can ignore the pop-up message as long as the
traffic continues to flow through the tunnel.
I can confirm also that QuickVPN 126.96.36.199 does not solve the problem on clean Windows 7 install.
Still get remote gateway does not respond while verifying network.
XP SP3 pc on the same network can connect just fine to remote RV042 (latest firmware). Windows firewall off on windows 7 pc.
Can someone at Cisco confirm that this is still a problem with the new version of QuickVPN?
I am running Norton Internet Security 2010; it takes over and doesn't allow turning on Windows firewall. This set up worked fine with XP.
Can you please provide instructions on what settings need to be changed in NIS to make QVPN work? I can't be the only person using NIS 2010. It seems to be set up to allow QVPN with a very wide open rule. It allows any direction in/out, any computer, allcommunications and any protocol. What more could we need to set??
Does QuickVPN work if you temporarily disable Norton?
From protocol perspective, QuickVPN makes use of SSL (TCP port 443 and 60443), IKE (UDP port 500 and 4500), ESP, and ICMP. You need to make sure the third-party firewall is not blocking any of the above.
QuickVPN Client also depend on several .exe programs (see attached screenshot) that are located in the QuickVPN install directory. The third-party security software also needs to trust them in order for QuickVPN to work.
I have the same problem with Norton Internet Security 2010. On Vista, I can turn the Windows firewall on at the same time as the Norton firewall is on and active. On Windows 7, Norton takes control of the Windows firewall and does not allow you to turn the Windows firewall on whether the Norton firewall in active or disabled. It would appear that Norton would have to be uninstalled to enable the Windows firewall.
With Vista, I can make a QuickVPN connection with the remote router when both the Windows firewall and the Norton firewall on. I am not able to make a connection with Windows 7. Most likely because I'm not able to turn the Windows firewall on. I really don't want to uninstall NIS 2010 just to make the VPN connection with Windows 7.
If QuickVPN Client is installed on Windows 7 before Norton Internet Security 2010 is installed, I found QuickVPN Client can work properly while NIS takes over Windows Firewall. Perhaps you could try uninstalling NIS and then re-installing it.
OK - I uninstalled Norton Internet Security 2010 and rebooted the Windows 7 PC. I then uninstalled QuickVPN 188.8.131.52 and reinstalled it. I verified that Windows firewall was ON and opened QuickVPN. QVPN tries to connect but then displays the message "Remote Gateway is not responding, do you want to wait?"
I'm not sure what to do at this point. I have not reinstalled NIS yet, I would like to make the connection without any type of internet security before reinstalling. I have successfully connected to the QVPN using a Vista 64 bit PC after trying with Windows 7 above.
Did you find that this worked once you turned on the Windows Firewall? I'm troubleshooting the problem with Symantec Endpoint Protection and after uninstall and starting the standard windows firewall QuickVPN still does not work with Windows 7. I wonder if there is a problem with the rules after SEP is installed but Would like to verify that someone got Windows 7 clean install to work with QuickVPN.
No did not get it to work.
I also now have a VISTA SP2 pc where NIS was uninstalled. This one also refuses to connect with the usual
"Remote Gateway is not responding, do you want to connect".
Tried NIS removal Tool.
VISTA firewall on and off.
XP pc's just works..
Firstly, sorry for my English.
I post this message here because in seeking a solution to the problem mentioned here. I found that the problem came from ipsecand I finally found a solution.
You must install the vpn client on windows XP export the ipsec configuration via ipsec.msc in quickvpnclient directory and import within windows seven client.
For me, it works, i hope this info will be useful.
While the current Cisco QuickVPN Client ver. 184.108.40.206 appears to be incompatible with Windows 7, a simple workaround to resolve this problem is to change the Compatibility mode for the Cisco QuickVPN Client in Windows 7.
To do this, follow these steps:
That should do it, and your Windows 7 clients should be able to connect. This problem specifically resolves the problem with the client under Windows 7 where the log file indicates the following errors after [STATUS] Verifying Network.
[WARNING]Failed to ping the LAN IP of the remote VPN Router!
[WARNING]Ping was blocked, which can be caused by an unexpected disconnect.
That's a very ingenuous solution! Were you able to do any analysis of the ipsec configuration to determine the key settings that are needed? I'll take a look at it and see if I can isolate the problem by looking at the changes from the imported configuration.
I forgot to mention that this solution works in XP mod and if only the strategy that has been imported from windows xp pc that itself has been connected once to the gateway. And I only exports FreeSwan strategy. I agree that it is a Ingenuous solution, but it works temporarly.
After looking a little more the ipsec configuration, I noticed that the security policy ipsec in firewall console was not enabled when the connexion is established. After enable this, everything works properly.