RV215W not responding to outside connections

[catuo81]

The RV215W is not responding to the https port, the VNC port 5900 is also failing to respond. VPN still works, I will go in and reboot and it will work again. It works for 1 day and fails to connect again.

Latest Firmware is already install, I don't know what else to do.

Thanks for the sugestions.

Catuo

[Anwar Mangla]

Hi Glenn,

I have 3 RV215 devices and these become unconscious every once in a while and a reboot fixes the issue. I have Cisco Service Request 638634811 opened but I am not convinced that a hardware replacement will fix the issues I am having. I have a simple setup. ISP->Router->LAN

Thanks,

[Glenn Martin]

Thanks Anwar, I'll let you know how this investigation is going.

Glenn

[cleartech.aus]

We also have this problem with two RV215W units currently in use at 2 client sites. Cisco case SR 680213261. We have been backwards and forwards with Cisco support and still no fix. The problem we have is that both customers have Exchange servers onsite and once the port forwarding fails their mail stops being delivered. Fortunately we can see this as we have port monitoring checking their inbound mail and we get an alert when this happens. Sadly, we're just having to live with this problem at the moment and remotely reboot the router (via access to a device on the network as yes, you guessed it, the remote access port is also blocked). Would love it if Cisco actually decided to fix this problem rather than just ignoring it.

[Anwar Mangla]

Well, ours finally died today...Its not worth putting more time into it. I am deploying Ubiquiti Edge Routers going forward...

[Glenn Martin]

Hi Anwar: I'm being asked to get the RV215 configurations.. Can you please provide?

Thanks

Glenn

[ahmed.muratbegovic]

I have same issue, same model, latest firmware 1.3.0.7. I can't believe that this bug is 3 years old and you (CISCO team) didn't solve it yet. ??????WTF?????? Maybe I expect to much or what?       

[Glenn Martin]

Hello Ahmed: Is your configuration similar (Y|N). I'm re-escalating this to the support team to raise the issue. Do you have a support case open on this?

[cleartech.aus]

Glenn, we had a case open which has now closed (Cisco case SR 680213261) and have now managed to get onsite with both customers, factory reset the devices and re-flash the firmware but still no change - both devices intermittently stop forwarding traffic on all ports. We are close to just taking the hit on these and replacing them with (cheaper) 'other brand' devices that we know will work. The reason we went with Cisco in the first place was based on our experience with 800 series products.

[ahmed.muratbegovic]

ISP->Router->LAN and i am only using single port forwarding. No VPN or any extra functionality. I don't have case opened but like you can see in comments there was opened case for this but it's closed now and problem persist.

[BBHomeShop]

Hello, I have the same problem since a few months,  only reboot helps, I'm using only RDP port forwarding
has anyone tried downgrade firmware maybe this can solve the problem?

[Anwar Mangla]

We tossed all of these pieces of junk in the trash... Ubiquiti Edge Router Lite is working flawlessly....

[it]

Same here.  1.3.0.7 firmware.

Problem 1

Can't port forward any longer.

Problem 2

Changed the password to a very complex generated password using Lastpass generator, and the Rv215W has corrupted the password and I can't log in any longer.  So I can't reboot it, as site is remote.

Problem 3

DNS - I have had constant DNS resolution issues in my Server 2012 Primary domain Controller with second 2012 running RDP service.  I am not using the router as a secondary DNS, but I have constant dns cache corruptions on the Terminal Server.  Since one cannot nominate third party DNS servers on a PPPOE connection, one has to conclude that the 215 is causing the issue. After all - if it can't port forward, it's entirely feasible it can't properly pass DNS requests through either.

Like many of the other ex-users on here, I trusted the Cisco name.  BIG mistake.  After many many years of using Snapgear routers which were bulletproof at everything, I had a need for another router.  No Snapgear available any longer, so I chose this piece of rubbish.  It has made me look a fool in the eyes of the customer, something that has NEVER happened before in my 25 years as an IT consultant.

I'm not looking for Cisco help, because this whole topic clearly proves Cisco in unconcerned and unable to fix this device.

Just wanted to add my experience.  Pity I didn't find this before buying it, but as I said I trusted the name.

.