1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

QuickVPN Client 1.2.11 released.

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Toxic, Jul 12, 2008.

  1. Toxic

    Toxic Administrator Staff Member

    QuickVPN Client v1.2.11 Release Note 7/1/2008

    Issues Fixed:

    1. Fixed a QuickVPN Connectivity issue, where QuickVPN Client running on Vista with a wireless LAN adapter cannot connect to a remote QuickVPN router.
    2. When QuickVPN Client fails to establish a tunnel with WRV200, the client will try to detect whether the Ping (ICMP) is blocked or the IKE negotiation (on UDP port 500 or 4500) is blocked, and log messages in the log.txt accordingly.
    Known Issues:

    1. QuickVPN Client v1.2.5 or newer, when running on Windows Vista, cannot connect to RVS4000 nor WRVS4400N when Vista is behind a Network Address Translation (NAT) device. The problem does not occur to QuickVPN Client running on Windows XP or 2000. This was caused by the change in Windows OS behavior. For more information, please see http://support.microsoft.com/kb/944335/en-us.
    2. Windows Firewall needs to be enabled on Windows Vista in order for QuickVPN Client to function properly. This is due to the fact that IPSec service on Vista is disabled when Windows Firewall is disabled. Some third-party firewall will disable the Windows Firewall, which will cause QuickVPN to fail.
    3. Users need to have the administrative rights in order to use QuickVPN Client. This is a constraint posed by the Windows operating systems.
    4. There is a known issue with Windows XP SP2 Firewall - ICMP packets are always dropped by the Firewall when the Firewall is enabled. The issue will cause the QuickVPN Client not being able to establish a tunnel with the remote QuickVPN Server successfully. Microsoft has released a patch to fix this issue. Once you install the patch, the issue should be resolved. http://support.microsoft.com/kb/889527/en-us
    5. QuickVPN tunnels do not pass NetBIOS broadcast packets. This may create a problem when users want to search computers by names or to browse the network neighborhood on Windows Explorer. Users can use a LMHOSTS file to work around this issue. More information can be found at http://www.microsoft.com/technet/pro....mspx?mfr=true
    QVPN is available at http://www.linksysinfo.org/forums/do...?do=file&id=18
     
  2. jaspurr77

    jaspurr77 LI Guru Member

    Still not working on my Vista SP1 system. Works fine wired, but will not connected with wireless. Hangs on 'activating policy' and asking if i want to wait over and over. This is the log file.....

    2008/07/21 23:27:08 [STATUS]OS Version: Windows Vista
    2008/07/21 23:27:08 [STATUS]Windows Firewall Domain Profile Settings: OFF
    2008/07/21 23:27:08 [STATUS]Windows Firewall Private Profile Settings: OFF
    2008/07/21 23:27:08 [STATUS]Windows Firewall Private Profile Settings: OFF
    2008/07/21 23:27:08 [STATUS]One network interface detected with IP address 192.168.1.101
    2008/07/21 23:27:08 [STATUS]Connecting...
    2008/07/21 23:27:08 [STATUS]Connecting to remote gateway with IP address: xx.xxx.xxx.xx
    2008/07/21 23:27:08 [WARNING]Server's certificate doesn't exist on your local computer.
    2008/07/21 23:28:19 [STATUS]Remote gateway was reached by https ...
    2008/07/21 23:28:19 [STATUS]Provisioning...
    2008/07/21 23:28:30 [STATUS]Tunnel is connected successfully.
    2008/07/21 23:28:30 [STATUS]Verifying Network...
    2008/07/21 23:28:36 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:28:39 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:28:42 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:28:45 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:28:48 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:28:53 [WARNING]IKE was blocked, which can be caused by a firewall blocking the UDP port 500 or 4500.
    2008/07/21 23:29:01 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:29:04 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:29:07 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:29:10 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:29:13 [WARNING]Failed to ping the remote VPN Router!
    2008/07/21 23:29:18 [WARNING]IKE was blocked, which can be caused by a firewall blocking the UDP port 500 or 4500.
    2008/07/21 23:30:42 [STATUS]Disconnecting...
    2008/07/21 23:30:47 [STATUS]Tunnel is disconnected successfully.
     
  3. samuel613

    samuel613 LI Guru Member

    Finally! It works on my Vista X64 machine using my Intel Wireless card with the latest QuickVPN (2.11?) to an RVS4000 with the 2.x beta firmware posted elsewhere on this site.

    Thanks.

    The funny thing is that QuickVPN said that it could not make the connection, and that I either entered the wrong password or have a conflicting IP, etc. BUT, when I randomly checked the router configuration page, it showed that I was connected. I first pinged the router (lan side IP), and to my surprise, it gave me a response. So I browsed to a known IP on the network, and I was in.

    I have waited almost a year for this function, but now, with Vista wireless capability to the VPN, and the web-filtering, IPS, and more, this is a really solid router for $125.
     
  4. jaspurr77

    jaspurr77 LI Guru Member

     
  5. samuel613

    samuel613 LI Guru Member

     
  6. keithscdc

    keithscdc LI Guru Member

    your are absolutely correct samuel613 most VPN's you have to pay extra, BUT when a company advertises that they can connect to a VPN on their router with their software and 18 months later still do not have a solution THAT IS WRONG
     
  7. Toxic

    Toxic Administrator Staff Member

    if it works via a wired connection the firewall will be enabled for the LAN adaptor. is the firewall for the wireless adaptor enabled?
     
  8. Toxic

    Toxic Administrator Staff Member

    what router and firmware version do you have ?
     
  9. samuel613

    samuel613 LI Guru Member

    I agree that it is a bit pathetic that a company with the resources of Cisco were not able to get their routers' advertised VPN capability to work with Vista for almost a year, and even after they finally did so, the client still (incorrectly) states that the connection failed.

    But, bottom line, it works now, every time. On XP or Vista, X86 or X64, free and easy. I am relieved it is finally working.
     
  10. aviczer

    aviczer Addicted to LI Member

    Related question: Will the QuickVPN Client v1.2.11 be able to connect to WRVS4400N running firmware V1.1.08? (I need to be able to VPN to the router from a laptop that sometimes is connected to the internet through a wire connection (wired local router)and sometimes is connected to the internet through a wireless connection (wireless local router)
     
  11. Digiview

    Digiview LI Guru Member

    a Vista sp1, QuickVPN 1.2.11, WRV200 1.38 issue -resolved

    Hey there all,

    This site has great useful info, thanks guys.

    I hope I'm not repeating anything said, However I had the same issue that Jaspurr77 had from 7.21.08, except no certificate issue from his log...

    Microsoft has a hotfix to download.
    http://support.microsoft.com/kb/957624/en-us

    I now connect just fine.

    Regards.
     

Share This Page