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

WRV54G Dynamic VPN Problems

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Fishy4tU, Jul 15, 2004.

  1. Fishy4tU

    Fishy4tU Guest

    Hello, I'm having trouble setting up this VPN with this router and i've exchanged it about 5 times already from bestbuy because I thought my unit is defective. I am using the 2.25.2 firmware and the Linksys tech support aren't that great and I haven't gotten any e-mails that i've sent them back. Here are my configerations, I have a dynDNS account and have a static address set up through the routher's ddns option.

    IPSec Passthrough: Enabled
    PPTP Passthrough: Enabled
    L2TP Passthrough: Enabled

    Tunnel Entry: Tunnel 1
    VPN TUnnel: Enabled
    VPN Gateway: Disabled
    Tunnel Name: SSH

    Local Secure Group: Subnet
    IP Address:

    Remote Secure Group: Any
    Remote Secure Gateway: Any

    Encryption: DES
    Authentication: MD5

    Key Exchange Method: Auto(IKE)
    PFS: Enabled
    Pre-Shared Key: ****
    Key Lifetime: 3600

    Here's the trippy part that's giving me the problems
    Status: Hostname Resolution Failed
    Shoulden't this say Waiting for connection? I have changed a lot of this around and gone through 5 units and I can not get it to say Waiting for connection. I bought a BEFSX41 to see if it was my configeration problem and the vpn on that router either says disconnected or connected, and when I tried on that router, it works. With this router, this Hostname Resolution Failed message is driving me nuts. Did I mess up the configeration? Another question is for Local Secure Group, I can also choose this "Host" option. Would that work the same as the Subnet? Thanks, Any help would be appriciated.
  2. JonAlthoff

    JonAlthoff Network Guru Member

    I'm not sure if you are still looking for an answer. I'm waiting for an overhaul of the firmware to fix multiple problems.
  3. JonAlthoff

    JonAlthoff Network Guru Member

    I was able to solve the problem by going to Administration and rebooting the router. I think someone suggested a problem with the DNS built into the router.

Share This Page