NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6900P will not respond to ping from internet
Sometimes I need my R6900P router to respond to ping from internet. So I temporarily check "respond to ping from internet" on Advanced/WAN Setup page. It worked fine on firmware ver V1.2.0.22_1.0.78. However, on any V1.3 firmware version since that, including the latest V1.3.1.26_10.1.3, the router will not respond regardless of that setting. A couple months ago I was able to reach tech support and they acknowledged there were issues, but it would be fixed on next update. It appears it is not fixed. Does anybody have any solutions to allow the router to respond?
I realize most people were having difficulty disableing this setting and no matter the setting the router appeared to always respond. So it appears that instead of fixing the switch, Netgear just permanently set it to disable.
Any ideas or solutions? Reason I need it to respond is that when I have uptime issues with my ISP, I use DSLReports monitor service to send pings to my router every 10 minutes or so and then send me a report as to the success rate. I use this to prove down time with ISP.
> [...] However, I have not tried updating, factory reset, and reprogram
> all setting from scratch. In reading many issues, it seems doing that
> usually does not solve the issue. [...]
It should never be needed, but when actual behavior disagrees with
apparent settings, it's worth a try. If you save your old settings, and
the settings reset doesn't help, then it should be easy to restore the
old settings.
> [...] When I revert to V1.2 above, the port forwarding starts working
> again with no other setting changes.
"ping" response and port forwarding are entirely different, but...
Sounds like a firmware bug (of which there is seldom a shortage), but
running the reset test is the most efficient way to determine whether
it's a waste of time.
Some of the folks here seem to recommend a reset to cure everything
from bad breath to cancer, and then insult people who are less
enthusiastic. It should cost no more than some wasted time, and you can
be pretty confident that someone will suggest/demand that you try it
before proceeding.
8 Replies
Some additional details on my above submitted issue. After trying the newer versions (any V1.3) and pinging the router not working, I revert back to the V1.2 I referenced above and it starts working again.
I have also discovered that with the V1.3 updates, port forwarding for access to my web cam has ceased working. I verified settings are what I had been using. I even deleted the entry and rentered it with no success. When I revert to V1.2 above, the port forwarding starts working again with no other setting changes.
Seems like with a lot of new security concerns, more secure updates are being supplied by Netgear that haven't been vetted with all settings/devices. However, I have not tried updating, factory reset, and reprogram all setting from scratch. In reading many issues, it seems doing that usually does not solve the issue. But each issue is unique. Do you recommend trying that - especially with a major version number change (1.2 to 1.3)?
> [...] However, I have not tried updating, factory reset, and reprogram
> all setting from scratch. In reading many issues, it seems doing that
> usually does not solve the issue. [...]
It should never be needed, but when actual behavior disagrees with
apparent settings, it's worth a try. If you save your old settings, and
the settings reset doesn't help, then it should be easy to restore the
old settings.
> [...] When I revert to V1.2 above, the port forwarding starts working
> again with no other setting changes.
"ping" response and port forwarding are entirely different, but...
Sounds like a firmware bug (of which there is seldom a shortage), but
running the reset test is the most efficient way to determine whether
it's a waste of time.
Some of the folks here seem to recommend a reset to cure everything
from bad breath to cancer, and then insult people who are less
enthusiastic. It should cost no more than some wasted time, and you can
be pretty confident that someone will suggest/demand that you try it
before proceeding.Thank you Antinode! I appreciate your directness in your response. Following your suggestion, I loaded the latest V1.3.1.26_10.1.3. Then did a factory reset, followed by reentering my custom settings. Now ping from the internet works, and my dlink web cam is accessible (via upnp) from the internet. However, the old Panasonic web cam access still wouldn't get through. Remembering your caution about "suspect everything, not just port forwarding", I tested just the router and found it did indeed forward. The problem was the AT&T Uverse modem in front of it. So I added a firewall rule in the modem to allow port 82 access, then the modem forwards it to the camera. Not sure why I didn't need that on the prior Netgear firmware. However, all is working now.
As a side note, after I tried the new firmware a couple days ago (and reverted back) it appeared the 5G wifi was intermittent - not working for hours, then mysteriously working. (I have seen multiple people experiencing this issue in other threads). After loading the new version and factory resetting - no 5G problems!
So while is may be a pain to reprogram all the custom settings, at least I get a very clean install that works! Thanks again for the encouragement.