RV082 becoming unreliable??

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by SmallOffice, Apr 6, 2008.

  1. SmallOffice

    SmallOffice Network Guru Member

    I have been using the RV082 for the past several years without any issues. Just recently, it seems to be freezing once a week. (Cannot connect to the router via HTTP and problems connecting to some mail/web servers.)

    When I (hard) reset the router everything seems to be working. I cannot recall any changes to my router/network recently. This seems to be a new problem.

    I am running Firmware Version 1.3.5. Any thoughts on how to diagnose? The system log does not seem to have any useful entries.

    BTW, I have been considering replacing the RV082 with the Netgear ProSafe Dual WAN Gigabit Firewall FVS336G in order to take advantage of the simple SSL VPN.

    Any suggestions?

  2. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    I had one client where that was happening...I did a reset to factory defaults....was already on the latest firmware. They were also using the content filtering...which I disabled. Been smooth since.
  3. SmallOffice

    SmallOffice Network Guru Member

    I can try this...

    So the basic procedure is to:

    1) Backup settings
    2) Reset to factory default
    3) Restore settings


    I am not using anything fancy on this router. Just using the vpn functionality.

  4. ccb056

    ccb056 Network Guru Member

    I wouldnt save a backup file of the settings; I would just remember them/write them down.

    Do a factory reset.

    Then manually enter in the settings.

    If you do it the other way you may be bringing garbage back into the system.
  5. djcanfield

    djcanfield Addicted to LI Member

    RV082 Lockups

    We have had similar problems with two RV082 routers. We are using these as simple routers that we embed in an instrument to connect various pieces together. We use them out of the box with all the default settings, no VPN. We have now seen cases where routers running v 1.3.2 firmware have "locked up". When they do this the red Diag light comes on, and the Windows computer connected to the router reports that the cable was disconnected. The reset button does not work—the router must be power cycled and then all is well.

    Is there a known cause for this? We have seen this happen when there was *no* IP traffic at all-- I.E. the WAN ports router were not connected and the hardware devices on the subnet side were completely idle.

    Is there a preferred version of firmware? We have only seen this problem on two routers, both running 1.3.2. Other routers have been running, and for about two years with no such problems. Other routers have also been running 1.3.2 for months without issue, but when I searched the formus I found another complaint of 1.3.2 locking up.

    Any advice is *greatly* appreciated, since we embed this router in our instrument, it will be hard to switch to a different one.
  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