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

WRV54G - no WAN connection

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

  1. Wabiloo

    Wabiloo Guest

    In our office in London, which is part of a business center, we decided to replace our D-Link DI-804V VPN router as for some unidentified reason it seems to reboot itself every 27 minutes, loosing and reconnecting the internet connection each time.

    We bought a Linksys WRV54G a few days ago and I have been trying to install it ever since, and failed.

    I set it up with the same details as the D-Link one (Same WAN IP, Mask, Gateway, DNS servers), disabled the firewall, static routes and port forwarding and physically connected it to the LAN switch and to the WAN cable taken off the D-Link router)

    Most functions seem to work, ie. all computers receive a DHCP-allocated address and all computers on the local network can talk to each other happily.

    However, we just cannot get an Internet connection. From any machine, I can ping the LAN IP of the router (, its WAN IP ( but that’s it. Any address beyond that returns a “Destination net unreachable†error. If I put the D-Link router back on, it works fine. Linksys back on and again, no internet connection, although the router itself says (in its web-based status page) that the internet is connected, and the WAN Link/Transfer LED on the router is happily green.

    I upgraded the firmware to 2.37EU but that didn't solve the problem.

    I tried this router at home, and connected it to my DSL line and had no problem there, with the exact same settings (apart from the WAN IP and gateway obviously). Internet connection was working fine from any machine on the home LAN.

    Do you have any idea what the problem could be. Could it be a hardware problem between our router and the business center one?

    Any help would be greatly appreciated.
  2. TazUk

    TazUk Network Guru Member

    What does the WAN side connect to, an ADSL modem/router, cable modem????
  3. Guyfromhe

    Guyfromhe Network Guru Member

    the wanport may be maclocked by your isp?
    try mac spoofing...
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    In addition to what the fellas have already suggested (and if you already haven't done so), try nbtstat -R for a purge and an ipconfig /flushdns. I realize you've yet to really make a connection, but sometimes, a good 'ole clean out paves the way.

    Off the cuff, are there any previous entries in your switch (I assume it's managed) that referred to the Dlink (possibly)? If not already done, try clearing those too...

  5. Gurumaster

    Gurumaster Guest

    Same WAN Connectivity Trouble During VPN Tunnel Connection

    I am having the same trouble with WAN connectivity while a VPN tunnel is established. No Internet access for LAN users, No DMZ Hardware activity and No activity to the other VPN other than Pinging (Hence, nearly useless VPN).

    I have contact Linksys 8 times now, Voice Support Level 1 and Level 2/Online Support/Customer Service Form.
    They have been completely unable to offer any suggestions other than to adjust the MTU size to various levels down to 1100 (didn't help).

    The router is 3 days old and new (not refurbished).

    I have several other Vpn connected successfully using other brands and various models of routers. The problem is definitely with the WRV54G.

    I had this same trouble with Firmware 2.37.1 and the Beta 2.38 that Linksys emailed to me yesterday.

    Any suggestions?

    Thank you for any help.
  6. DocLarge

    DocLarge Super Moderator Staff Member Member

    You might have to reload your firmware.

    When I've had a web page load badly, in conjunction with running a few other things at the same time, I've seen it "personally" where I've been able to connect to any internet site I desire "yet" not be able to enter the web interface directly (, etc...). Because I had an internet connection, I could enter the router via the internet, but not locally.

    After nbtstat -r, ipconfig /flushdns, etc... for about 15 or 20 mins, I was forced to reset the router. This is just an inherent glitch that happens once in a blue moon, and I think you have something similar going on right now.

    Unless you can find another fix, you might be better off taking the 15 mins to do a reload of your firmware...

    If you do reload, use 2.38. I'm running that right now and "everything" works (yes, that includes the quickvpn tunnels also).


Share This Page