10-17-2015 10:32 AM
I started playing with VLANs and wanted to see about limiting administrative access to certain VLANs. I ended up locking myself out.
I tried rebooting while holding the reset button for 10+ seconds, but the router would either keep the red Diag LED on while blinking green OR boot as normal.
In both cases I couldn't access the web interface (regardless of what static IPs I set for myself). The device also continues to hand out IPs as if there are still VLANs (192.168.3.x, instead of the expected 192.168.1.x).
10-17-2015 10:34 AM
"Blinking green" was referring to the power LED.
10-24-2015 10:36 AM
Anyone?
10-27-2015 11:43 AM
Thanks for contacting Cisco,
You should be able to factory reset the device by holding the reset button in for 30 seconds.
IF you continue to have issue, please give the Small Business Support Center a call at 866.606.1866.
Best Regards,
12-13-2017 09:37 AM
@antiantagonist1 wrote:
I started playing with VLANs and wanted to see about limiting administrative access to certain VLANs. I ended up locking myself out.
I tried rebooting while holding the reset button for 10+ seconds, but the router would either keep the red Diag LED on while blinking green OR boot as normal.
In both cases I couldn't access the web interface (regardless of what static IPs I set for myself). The device also continues to hand out IPs as if there are still VLANs (192.168.3.x, instead of the expected 192.168.1.x).
@antiantagonist1 wrote:
I started playing with VLANs and wanted to see about limiting administrative access to certain VLANs. I ended up locking myself out.
I tried rebooting while holding the reset button for 10+ seconds, but the router would either keep the red Diag LED on while blinking green OR boot as normal.
In both cases I couldn't access the web interface (regardless of what static IPs I set for myself). The device also continues to hand out IPs as if there are still VLANs (192.168.3.x, instead of the expected 192.168.1.x).
@antiantagonist1 wrote:
I started playing with VLANs and wanted to see about limiting administrative access to certain VLANs. I ended up locking myself out.
I tried rebooting while holding the reset button for 10+ seconds, but the router would either keep the red Diag LED on while blinking green OR boot as normal.
In both cases I couldn't access the web interface (regardless of what static IPs I set for myself). The device also continues to hand out IPs as if there are still VLANs (192.168.3.x, instead of the expected 192.168.1.x).
12-18-2017 01:54 AM
Actions taken: · Tried different browsers, computers and cables. · downloaded Nmap to check open ports, 8007 was open · Tried to access GUI with 192.168.1.1:8007 · GUI is accessible. Download Nmap and check open ports to access GUI Nmap - Zenmap GUI soft for port check https://nmap.org/zenmap/
192.168.1.1:8007 Scanning 192.168.1.1 [1000 ports] Discovered open port 80/tcp on 192.168.1.1 Discovered open port 53/tcp on 192.168.1.1 Discovered open port 1723/tcp on 192.168.1.1 Discovered open port 443/tcp on 192.168.1.1 Discovered open port 8443/tcp on 192.168.1.1 Discovered open port 8000/tcp on 192.168.1.1 Discovered open port 8008/tcp on 192.168.1.1 Discovered open port 8007/tcp on 192.168.1.1 <---- acessed by this port 192.168.1.1:8007
try using all open port after scanning that soft
12-28-2017 11:46 PM
12-28-2017 09:21 AM
I have exactly the same problem! I cannot access to the web interface anymore - no matter with which browser. Also neither the hard-reset or the access with port 8007 works.
Luckily the device is still working (with the default settings?!) but I cannot gain access to it with the web interface anymore. I have the feeling, that the hard-reset by pressing the Reset button for >10 seconds does not reset to factory defaults.
12-29-2017 01:41 PM
12-29-2017 10:11 PM
12-30-2017 02:08 AM
01-10-2018 07:56 AM
You will have to do a tftp recovery. You may need to do it with an older firmware file. Some firmware versions they have released were bad. For example in some of the older versions after a couple weeks of operation the device would stop allowing logins until you power cycled it. In some older versions of firmware there were security holes. (those have been removed from the site I believe)
Just recently I found that I had trouble with version 1.4.2.17 maintaining VPNs however version 1.4.2.15 is stable.
One thing that I think helps to keep these stable is to firmware update them then login and do a factory reset then re-input the configuration again. In a large network of these I have learned never to remote upgrade them. Instead upgrade a spare, then rectory reset it and set it up again then swap it out with the device in the field.
02-22-2019 10:00 AM
If you're accessing from the LAN side:
If you're going to try port 8007, try using HTTP and NOT HTTPS. The former works, the latter doesn't seem to. Firmware 1.4.2.19/20.
01-01-2025 06:27 AM
Everyone, Realize I'm late to this thread. I had the same problem and was totally distraught worked many hours on it, Replaced the Router with something to get by until I could get another RV320. Tried everything I could find on Forums. Loading Firmware from TFTP, Resets, you name it. I finally opened the Router "Violates Warranty -- Mine was out of Warranty anyway" Found battery on the board and removed it. Let it set overnight. Replaced the battery and re-assembled. Wha-La able to access Web Mgmt.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide