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

QUICK VPN WITH ROUTER!! HELP!!

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by spaniola, May 31, 2005.

  1. spaniola

    spaniola Network Guru Member

    Ok, please someone help me with this! I will paypal you $10.00 if you can get me up in running.

    I am having the dreaded Verifying network issue with Quickvpn when using any connection with any cable/dsl router.

    Has anyone used a public wireless system, or shared router type connection with Quickvpn and had it work?

    If i plug the cable modem directly into the computer quick vpn works fine, however if i use a router i stay at verifying network.

    THanks
     
  2. DocLarge

    DocLarge Super Moderator Staff Member Member

    Nick,

    I'm assuming your connecting to a WRV54G/RV series router from a WRV54G/RV series router, right? If so (or not), the following information still applies.

    You'll get the "Verifiying Network" hang for following reasons:

    1) The quickvpn client is not the only vpn client loaded on the client machine.

    2) MTU on the WRV54G you are connecting to isn't set at "auto" and/or the packets being sent from the client computer are too large (should this be the case, download "DrTCP" and set the MTU of the client's NIC to 1458). Additionally, it doesn't hurt to check and see if the MTU on the client router is set at "auto" also.

    3) You are trying to connect through a dialup or ISDN connection.
    NOTE: I have never been able to connect from a dialup/ISDN connection with quickvpn. More power to those who can.

    4) The firewall software on your computer is registering the "ACK" conversation from the distant and your laptop as an "Invalid ICMP Type." In this instance you can either "shut down" the firewall for the session or, as I've done, uninstalled my firewall software (NIS 2004) and quickvpn, then reinstalled both (Norton first followed by quickvpn). After that, launch quickvpn, and once Norton detects it, it establishes all the proper rules to allow it to pass through the firewall. Hopefully your firewall software should do the same.

    In the case of #4, I never caught this until I noticed after reloading one of my computers, I had to drop the firewall on one of them to access "the same damn share" as the others, but I didn't have to bring the firewall down on any of the others except that one particular machine.

    5) IPSEC Passthru is not enabled on the client/distant end router.

    Your problem seems "oh so familiar" but I'm betting I'm in the right neighborhood...

    Peronally, I've been able to use quickvpn "wirelessly" at local hotspots and wifi cafe's with no problem. It sucks that I have to turn my firewall on the laptop off, but that's mostly due to the firewall policies of the wifi router the establishment uses.

    Doc

    P.S.,

    should this be the answer, keep the money. If you get a consistent quickvpn connection, you'll buy the quickvpn 50 client user license like I just did. It feels "good" looking at 50 possible connections (it just loaded it today).
     
  3. Yohann

    Yohann Guest

    QuickVPN Verifying Network solution (for me)

    I was having the same problem (stuck at "verifying network" then disconnect) but none of the suggestions listed here helped. Here's what did the trick for me:

    I had 2 network cards in the computer, the 1st one was not connected to anything, 2nd one was used for all network and Internet access. *Apparently* QuickVPN was trying to use both network cards for different parts of the connection process. What tipped me off was the output from IPSEC.EXE (in the QuickVPN directory) that listed the IP address of my unplugged card:

    (...)
    MyTunnel : (wrong ip address here)
    MyNet : (wrong ip address here)/255.255.255.255
    (...)

    After I removed the binding between TCP/IP and my unused network card, QuickVPN connected instantly.

    Hope this helps
     
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Thanks for the input, Yohann. I'll make sure to include them into a new revision of the quickvpn rules.

    The quickvpn rules were written under the assumption that the most "basic" settings are "at a minimum" properly configured, namely a good tcp/ip connection (internet access).

    If someone puts "two" NIC's in and can't get a quickvpn connection, the rules can't be held accountable for "not" working, this would be more of a "hardware" problem initially. Once you take care of that, then the efficiency of quickvpn comes into play :) :)

    Doc
     
  5. shock_wdr

    shock_wdr Guest

    - Make sure that you have set the computer under DMZ.
    - No firewalls enabled
    - Make sure that the router LAN IP Address of the router does not match the remote router's IP Address
     

Share This Page