NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AGAIN - URGENT - Auto-update repeatable failure killing nvram!!!
I now have a REPEATABLE failure from the auto-update to v2.7.3.22. I completely reset my config (1 RBR50 and 3 RBS50) to v2.5.1.16 yesterday with full firmware reload and factory reset. Last nig...
What happens if you factory reset the RBS and RBR with v22 loaded and setup from scratch then back a new back up config to file?
Factory reset is not a viable option for me at this time as I have a complex config with static DHCP and port forwarding that would be a complete pain to enter by hand. I do have some additional data, however. I have a repeatable scenarion 1. Firmware load and factory reset to v2.5.1.16 2. load parameters 3. come up with router only and go to update page on WebUI 4. v2.7.3.22 available 5. do update 6. nvram has junk THen Factory reset and firmware load v2.7.3.22 Come up and load old parameter file nvram OK and running difficult to absolutely confirm without telnet but look good Bottom line - something is not right doing auto-update with existing parameter file. Seems to support what others are saying too.
- Factory reset is not a viable option for me at this time as I have a complex config with static DHCP and port forwarding that would be a complete pain to enter by hand. I do have some additional data, however. I have a repeatable scenarion 1. Firmware load and factory reset to v2.5.1.16 2. load parameters 3. come up with router only and go to update page on WebUI 4. v2.7.3.22 available 5. do update 6. nvram has junk THen Factory reset and firmware load v2.7.3.22 Come up and load old parameter file nvram OK and running difficult to absolutely confirm without telnet but look good Bottom line - something is not right doing auto-update with existing parameter file. Seems to support what others are saying too.
Sorry post is hard to read and interface is not showing linefeed between steps. Hope you can decrypt.
Scott
A reset and set up from scratch would be needed to verify if from new configuration is reproducing this issue or not. We've seen historical experiences and post where older config files no longer work with newer versions of FW. A reset and a clean setup from scratch is needed to avoid this. Espeically on major version updates vs minor version updates.
Something to open a support ticket and let NG know about.
Good Luck.I am out of warranty so i can't open a support ticket.