We have a couple of customers seeking to use QuickVPN to allow their employees to connect to RV0x2's (one is a 42, the other an 82). We ensured both had the current firmware (1.3.12.6-tm for the 42, 1.3.98-tm for the 82). Created a test user account then proceeded to install QuickVPN 1.2.11 downloaded yesterday from the Cisco web site. We installed first on a Vista Ultimate SP1 (fully patched through March 2009's update cycle). The client installs fine then returns the error:
Failed to establish a connection.
This could be caused by one of the following:
1. Incorrect Password (I've checked, rechecked, and checked again, it's right)
2. No valid IP for the network card. (What network card is it talking about? The NIC on this computer allows ful LAN and Internet access so it obviously has a valid IP)
3. Incorrect server address. (One location has a server that has RDP enabled through the RV082 and I can copy/paste the address into mstsc.exe and connect with no problems so the address is correct).
4. Windows Vista with Windows Firewall disabled, which disabled IPSec service. (The Windows Firewall service on this Vista box is running as is the IPSec Policy Agent. Also, regardless of the Windows Firewall state, the Cisco VPN client works perfectly so I'm not convinced the statement that IPSec can't work if the WF is disabled unless the Cisco VPN v5 client uses a different protocol.)
5. Local IP address conflicts with the subnet of the remote VPN Server. (the local subnet is 192.168.100.0/24, the remote is 192.168.1.0/24 so no conflict here)
So we moved on to a XP Pro SP2 box. Again, we setup the same connection using the same QuickVPN software downloaded earlier yesterday. On the XP Box we received the following errors:
1. Incorrect Password (I've checked, rechecked, and checked again, it's right).
2. No valid IP for the network card. (What network card is it talking about? The NIC on this computer allows ful LAN and Internet access so it obviously has a valid IP).
3. Incorrect server address. (One location has a server that has RDP enabled through the RV082 and I can copy/paste the address into mstsc.exe and connect with no problems so the address is correct).
4. You may need to dsiable your Windows Firewall (Tried that, made no difference).
5. Local IP address conflicts with the subnet of the remote VPN Server. (the local subnet is 192.168.100.0/24, the remote is 192.168.1.0/24 so no conflict here).
We then tested the Cisco VPN v5.0.05 client on this XP Pro SP2 box and was able to instantly connect to remote Cisco ASA VPN hosts with no problem as we were with the Vista box.
So then I called Cisco Small Business TAC support for VARs. I gave them the SN of one of the devices and was told that since it was out of hardware warranty that support wasn't really able to help us. Huh? VARs can't get support for products we've recommended? We weren't looking to have a device replaced, only find out what QuickVPN, a product that has a less than stellar history, won't work on any system we try. Cisco has changed a long time policy with no way to renew support services like buying SmartNet contracts (which I'm not opposed at all to recommending to customers) to ensure continued access to support. I highly recommend that Cisco reconsider supporting VARs lest we start recommending customers buy products from a different vendor.
In the end, does anyone have any suggestions on why the Cisco VPN works and the QuickVPN won't? Honestly, I'm back to wishing that these products supported PPTP up to the max connections becuase I never have any problems with PPTP, but the limits on PPTP on these prevents me from using that as the solution.
Thanks...
