NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 access lag
Firmware: V1.0.8.12-1.2.23 I have had this router for a couple of years and it has been running okay until the last FW update which made the router unusable? I was annoyed and had to spend a lot of...
Hi pendaws,
We’d greatly appreciate hearing your feedback letting us know if the information provided has helped resolve your issue or if you need further assistance.
Regards,
Blanca
Community Team
Although you can set up any IP Address normally one would use one that is Private Lan.
However, the DNS is trying to go to Ford I suspect, and hence your problem with PING...
Was this a new development though? That I don't understand?
It started happening about 3 weeks ago and has gotten worse. I like using that IP address range because it isn't a private one.
It has NEVER been an issue before and, the range of IP addresses can only be accessed after bypassing the IP address of the provider I use.
I have all my other machines using IP addresses using the range and can ping them with no problem, it is JUST the router that has the problem.
I really think this is a DNS issue caused by using addresses that are NOT private, and I assume the router using the same aa a registered Ford IP address?
Since it all worked before, well, that sort of points to the firmware update that failed and your recovery to an older firmware which you said wasn't easy. Possible some corruption internallly still exists.
It would seem you have a few choices here, and none may be likeable to you:
- Try to CLEAR the NVRAM (ERASE) under the ADVANCED tab, ADMINISTRATION, BACKUP SETTINGS, and then MANUALLY re-enter all settings.
- Do the same steps as above but do not re-enter the settings, but load a new copy of the firmware you are using by d/l'ing it again and installing. Then re-enter settings manually.
- Do the same steps as the 2nd option but instead of the present firmware using, get the latest firmware and then re-enter the settings manaully.
Since you had problem loading the latest firmware before I sort of suspect a partial install for some unknown reason and however you recovered was not really totally recovered causing your problems.
Well, I have temporarily fixed the issue. I put the cheap router that is given to us when we sign to the NBN, then I found that the issue has GONE away. It IS the router and I will make sure that I do more invetstigation when looking for a NEW router as this R7000 is questionable.
I don't buy the bit about private IP addresses as this FAILS the ping even when I remove it from the internet. It has been almost 12 months since the failed FW update and this has only happened within the last two weeks so, I doubt it is an issue.Thanks for your ideas and I am sorry I was not able to fix the issue simply and will have to look at purchasing a NEW router that has a better rewiew and backup. My last purchase of netgear hardware.
pendaws wrote:
It IS the router and I will make sure that I do more invetstigation when looking for a NEW router as this R7000 is questionable.
I don't buy the bit about private IP addresses as this FAILS the ping even when I remove it from the internet. It has been almost 12 months since the failed FW update and this has only happened within the last two weeks so, I doubt it is an issue.Regardless of the LAN TCP/IP subnet configuration, the connection to the router and it's connected devices should be rock solid - fully agree.
Of course it's not the world greatest idea to run a subnet owned by another organisation instead of the RFC1918 private IP addresses - doing will potentially prohibit connections to addresses on the same subnet "out there". Not sure what advantage you think you gain if doing so, But that's mostly unrelated.
