WRV54G VPN Configuration - Remote Access to Internal Network

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by gerhardb, Apr 13, 2005.

  1. gerhardb

    gerhardb Guest


    I've got a WRV54G Router and I'm having problems configuring the darn thing to allow a VPN connection.

    All I want to do it connect to the VPN gateway (WRV54G) using the QuickVPN client so that I can remote access a few PC's at the company.

    (Small business... web access is provided via the WRG54G and a cable modem.)

    Is there a quick setup FAQ or something for the 2.3.x firmware and the QuickVPN client?

    The documentation stinks, and I'm wondering what the problem is... it basically doesn't allow a complete connection.

    I get to these responses when attempting to connect from a remote location:

    1) Connecting
    2) Activating Policy
    3) Verifing Network (stays on this for a while)


    "Info: The remote gateway is not responding. You will now be disconnected, please try again later."

    4) Deactivating Policy
    5) Disconnecting from the Server

    Any thoughts?


    PS IS there are reason DDNS never works on the WRV54G
  2. dumbo

    dumbo Network Guru Member

    I had smilar problems, follow these steps:

    1. Make sure you use latest firmware I use 2.38
    2. Reset your router to factory defaults and add VPN accounts.
    3. On your PC turn off firewall.
    4. Make sure IPsec service is enabled with Manual startup. You can look at control panel->administravite tools->services->IPSec Properties to change.
    5. Also make sure your router has an associated host name - default "linksys" - 192....->setup->router page. Mine has linksys domain and some host name.

    This is all I can think of. Let us know.
  3. Niwotian60

    Niwotian60 Network Guru Member

    I've had the same problem since I bought a WRV54G a few weeks ago. I have tried the 2.37 and (beta) 2.37.9 firmware without luck. Where can I get the 2.38 firmware? Neither this site nor Linksys' home page shows it.

    For the first poster: have you looked in your QuickVPN subdirectory to see if you have any error logs? I get a file named "wget_error.txt with the following information (I replaced specific address and name information with angle brackets <>) :

    --20:07:44--  https://<username>:*password*@<ipaddress>/StartConnection.htm?version=1?IP=<internal NAT IP address>?USER=<username>
               => `C://Program Files//Linksys//Linksys VPN Client//vpnserver.conf'
    Connecting to <external router IP>:443... connected.
    HTTP request sent, awaiting response... 
    20:07:48 ERROR -1: Malformed status line.
    It appears that I'm getting a connection but then failing on some subsequent HTTP handshake. I found another reference to this problem with the suggested solution of putting a host and domain name in my router setup, but I already had this in place.
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Here's a post I put on another site that has helped a few people making quickvpn connections.
    > I think I have found a pretty good "6 step" process for configuring the
    > quickvpn client. Folks I've shared it with so far seem to be having pretty
    > good success. I realize some of you may have seen this in the previous
    > email but here it is again:
    > 1) Disable pptp and L2tp
    > 2) Disable all vpn port forwarding (500, 1701, 1723, 4500) to cut down on background process interference
    > 3) Disable all vpn settings (tunnel, gateway, IKE)
    > 4) Make sure quickvpn is the "only" client loaded on your machine
    > 5) Enable Ipsec
    > 6) Check under services (if you're running on a windows platform) and make sure Ipsec is running

    > These are just the general ground rules to start out with. I'm attaching
    > the screenshots I recorded while I was testing the connection on Dave
    >Warner's wrv54g. These shots are of my router and the configuration it was in when I connected to Dave's router using quickvpn over wi-fi (yes,
    > quickvpn does NAT-T). Don't let anyone bullsh*t you, quickvpn connects.
    > One last thing to consider is if you're getting "verifying network," check
    > your mtu setting. At times, you have to lower it to avoid fragmentation of
    > the data packets.
    > As always, what's outlined is just a "baseline." As you start having
    > success, start varying your configuration.
  5. DocLarge

    DocLarge Super Moderator Staff Member Member

  6. coolbizs

    coolbizs Guest

    RE: The remote gateway is not responding.

    I've using WRV54G for a while and QuickVPN is such a bliss. Since then I can access my home network anywhere in the world :)

    Recently, I upgraded my work PC from Windows XP to Windows 2003 Server Standard Ed. (I'm a developer and my group decided to built application on the same platform as the web server). Since then, my Quick VPN started failing w/ the error: "The remote gateway is not responding. You will now be disconnected, please try again later.". I was scratching my head (almost bald now - just kidding) for the past weeks looking for solution.

    Just today I realized that during the upgrade, I added a new NIC to be on the gig network and that is the only thing different from my Windows XP env. Long and behold, I disabled the second NIC and now Quick VPN is working again.

    Just wanna share the experience.
    -Cool Bizs
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice