I installed firmware version 220.127.116.11 a couple weeks ago after seeing in the release notes that the port forwarding bug where clients would get 'no route to host' was resolved (one of the original posts found here: https://supportforums.cisco.com/message/3512354).
After installing the firmware and confirming it's running I've seen no improvement. I still must reboot my router 2-3 times daily so clients can access the ports that are defined in the port forwarding module.
Please take another look at this - the issue is not resolved and as far as I can tell it hasn't even been improved. Please also let me know of any beta firmwares - anything to put this issue to bed. It's been going on far too long.
When you upgraded the firmware from 18.104.22.168 to 22.214.171.124 did you perform a full factory reset using the hardware reset button on the back of the router? If you have not performed a hard reset of the RV110W after upgrading to v126.96.36.199, it is strongly recommended that you reset the device by holding down the reset button for 10 seconds to ensure the device is completely reset. This will ensure the configuration is erased and you are working from the default config based on the new 188.8.131.52 firmware image. We have tested the RV110W against this issue and we have routers running for the last 30+ days with port forwarding working correctly. If you cannot get it working consistently after the hard reset then please open a case with the SBSC TAC so we can begin the process of getting all of you network topology and router information. Please keep us posted on your progress.
Instead of configuring port forwarding rules, configure Access Rules. Once the setting has saved you will see your new rule under port forwarding.
Cisco SBSC Network Engineer
I'm also having this problem, even after upgrading to 184.108.40.206. I lose Remote Management at the same time, so I always have to call the site to have someone restart the router.
I'm trying the Access Rules approach now. The lack of response from chchapma to the last post makes me think it took care of things for him. I'm wondering if it will cure the Remote Management failure also?
What port are you using for remote management? If you are using a non-standard port for remote management this could cause a problem. Typically the routers are managed on 443, 60443, 80, or 8080. If are using one of the 4 ports previously mentioned and are still having problems, I would suggest calling 1.866.606.1866 to open a support ticket.
Cisco SBSC Network Engineer
Yes, I generally use a different port to reduce exposure to port
scanning. Is this related to the port-forwarding bug?
Is anyone from Cisco actually working on this ? I'm fed up with rebooting the router every hour, and doing so for the last 2 months is not helping me being any less frustrated. I would really appreciate if someone at least replied to a post in over a year. And no, access rules are not a resolution to a fix you implemented in the router and is not working like it should. I did not buy this router to change rdp ports on 25 workstations. It's really a shame because everything else on the router is working perfectly and i'm really happy with it....just let people know you're either working on it or can't fix it so we can return the faulty gear and move to something that actually works.
From my previous post from 5/7/12:
"When you upgraded the firmware from 220.127.116.11 to 18.104.22.168 did you perform a full factory reset using the hardware reset button on the back of the router? If you have not performed a hard reset of the RV110W after upgrading to v22.214.171.124, it is strongly recommended that you reset the device by holding down the reset button for 10 seconds to ensure the device is completely reset. This will ensure the configuration is erased and you are working from the default config based on the new 126.96.36.199 firmware image. We have tested the RV110W against this issue and we have routers running for the last 30+ days with port forwarding working correctly. If you cannot get it working consistently after the hard reset then please open a case with the SBSC TAC so we can begin the process of getting all of you network topology and router information. Please keep us posted on your progress."
Actually I did a hard reset *before* the firmware upgrade. Following the upgrade I restored the configuration from a backup file.
Additionally, using a defined Access Rule without the corresponding Port Forward results in no port forwarding at all. Use of both together has had me running for 2+ weeks now. Promising, but not yet conclusive.
Yes i did perform a full factory reset using the button at the back of the device. Tried to define access rules (which don't allow me to configure different external ports to same internal ones), and it doesnt work either. I'm planning on replacing the router with a linksys WRT160N with dd-wrt firmware which allows me do what i want and works like it should.
Recently tried the 110W again (it was the only box I had available).
A hardware reset, followed by simple configuration with static IP and 5 port forwarding rules - ran for 4 days before SMTP communication on port 25 stopped. A reboot bought it back to life.
Back in its box, again.
Following up: I have had two boxes running for a month with no problem. One is as described above with 188.8.131.52, but the other still has 184.108.40.206 with the same configuration that gave me trouble in the first unit. The one common change I made to the two was to change the remote management port from a high port to 443. Seems like the non-standard remote management port uses port forwarding internally, and triggers the firmware bug somehow.
Further followup - a few days ago the problem occurred on the 220.127.116.11 system. So it was some 6-7 weeks between problems.
These two installations were the pilot locations for a larger rollout. Unfortunately they have failed the pilot test and I now have to find a suitable alternate.
Have you talked to Cisco and are they in works on a firmware update for this model. I have issues with being able to get email inbound and remote management working with 18.104.22.168 and have done a factory reset after reconfiguring. It seems my device needs rebooted every 6 weeks and nothing appears in the logs. I am about to just tell my client ASA5505 is the way to go. Small Business support has already replaced the unit and i am convinced it is a bug in the firmware. I do have about 4 other clients with these devices and no problems and they also run SBS 2008 and 2011 servers.
Cisco seems to be of the opinion that there is no problem with their product.
I have been dragging my feet on a number of installations because I'd really like to use this router, but I just can't trust it yet. I have 7 of them out there, and honestly only one is giving me trouble. That one happens to be behind a DSL modem, the others are on T1 lines. So I'm tempted to blame it on DSL somehow, except that it takes a router reset to recover. Resetting the DSL modem does nothing.
I had opportunity to install another RV110W in a DSL system about a month ago, and so far no problem, but it's too soon to draw a conclusion. The new one is AT&T DSL, the older one is Frontier (previously Verizon). I'm waiting and watching on that one.
We are using port forwarding for running a security cameras.
I configured everything as you recommend it this post, but it will work from an hour to two days, then fails. (until reboot)
When will the new RV110W firmware be released?
I know it's been a while, but I decided to follow the suggestion to call 1.866.606.1866 and open a support ticket (I held off because frankly, my expectations are low).
When I get to the point of being transferred to a person, I get a error message telling me "The number was not recognized". What do I need to do to open a support ticket?
Dear mr.Blake Wright,
Thanks a lot for your tip, even if there is not exactly like you said ))
When I tried to create Access Rule device offered to create Service first. And after creating Service and Access Rule I didn't "see my new rule under port forwarding" - I had to create it there too.
Anyway, to make working port forwarding, you must follow these three steps:
1) create Service, describing used port range and type of traffic;
2) create Access Rule that allow traffic for this Service;
3) create Port Forwarding Rule for each IP and port you need.
And, imho, it's better to reboot device after all of that
Is Cisco ever going to fix their firmware? We had two of these ship from the reseller with the latest firmware already installed. After a couple days the port forwarding fails. Solution is to reboot. Cisco support has been very difficult to deal with and they seam to think that this is not a problem.
I have the same problem with this router. We did the firmware update, then factory reset and rebuilt our configuration. I still find the port forwarding failing every couple of days - in fact this morning, it failed twice within a few hours.
This is unacceptable. There is obviously a problem with this model and its firmware. Do I have to buy a different brand of product to fix this issue?
Technology Service of Long Island
I do face the same problem with four of these same devices, each one sits behind a ViaSat satellite modem and I also
need to reboot them 2-3 times daily so clients can access the ports that are defined in the port forwarding module.
Its really annoyning when something so basic as port forwarding its not a standard for all expensive Cisco products
I have the same exact issue and have performed all troubleshooting steps from this forum. Still, the router needs a reboot every week.
I followed every piece of advice, every possible remedy, every fix I could find, and it still kept losing the configuration. I was at a point where I was getting phone calls from my end user nearly every day that he couldn't access his network remotely, and the cause was broken port forwarding. I would reboot the router remotely (I have a different remote access tool), and it would all start working again.
I wound up replacing the router with a different brand. Guess what - it's worked flawlessly for about a month now.
The RV110W is just not a very good router. Simple enough.
Technology Service of Long Island
At this pace I may end up eating router price and replce with something else (and never use it again, probalby would go back to using DD-WRT firmware with homegrade routers). However, I've put in some changes just now trying to find where the programmers F**k up is. So far my debugging process:
- Made all the port labels match b\w Access rules and Firewall
- Removed redundant port forwards b\w Single and port Range
- Removed all Logging from Access rules
I'll let everyone know if there are any changes.
Similar issue. The router continues to do NAT translation and allows outbound and inbound traffic. The PROBLEM is:
Port Forwarding Rules fail randomly. In my case the failure occurs almost every 50-60 days in operation. The only solution is to reboot the box, then everything bis back to normal. This is now December 2013 and I notice Cisco has not put out any additional firmware to correct this issue?
Cisco: You cant ONLY provide support to people who buy your top of the line equipment. Those are the same people who encourage customers to put small business products in too, and when we see them fail miserably, it then makes us questions your top line equipment for use in our client networks. I would encourage you to provide a full resolution to this issue, for the sake of people who use your equipment on a regular basis.
Hi, if anyone meet this issue, please open a case to L2 support who will deliver you a new firmware. The port forwarding codes are redesigned in the new firmware. Thanks.
Do you have a way to contact Cisco Product Support?
The Cisco website says "1-866-606-1866 Small Business Support Center", but that number is not in service.
Depending upon your region, you can use one of the contact information listed in the below link.
You may need to provide entitlement information when you contact Cisco support to open a Service Request.
Hope this helps.