NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware upgrade on an XR1000
How long does a firmware upgrade take
I have a XR1000 with firmware 1.0.0.64. Ethernet-connected desktop runs Win 10 that is up to date. I have approx. 20 wired devices and 10 wireless devices.
I was doing the update / upgrade with a ethernet-connected desktop. I have found out that getting support from Netgear is probably the last thing I ever want to attempt. They don't even begin to let you fully explain what has transpired. They (her) didn't even know that the newer firmware has different options and she refused to escalate me to another tech. Finally after 59 minutes. Yes, 59! I gracefully hung up on her and kept rebooting and the XR1000 finally came to life. Well half-life anyway. The next day I called in again and by chance got the same woman who claimed that she was a higher level person than the day before. After an enlighten conversation with her I decided that Netgear tech support really, really sucks!
I did purchase an extended warranty through Micro Center and will use it to obtain a TP-Link router if this piece of crap keeps failing. I have found out one thing for sure. NEVER reboot this model unless you want to manually reload every option and connected device as it doesn't remember anything from the previous setup. ALSO it loves to assign the same IP to a new device that has the same IP to a currently connected and working device on your network whether it is wired or wireless. I have had it stealth-assign as many as 3 IP's to a device. It is truly, very sadly, badly engineered.
Sorry to hear of your experience thus far!
As a member of the Netduma team I'm somewhat limited in how much advice I can offer on the NETGEAR settings, but with regards to the issue of losing settings on a reboot: How were you rebooting? Were you use the physical button on the back, pulling the cable out or rebooting through the interface?
If I recall correctly, a user who experienced a similar issue in the past reported that rebooting through the interface preventing this from happening again, so that might be worth bearing in mind should you want/need to reboot it again in future.