NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Tylerleepart
Mar 11, 2020Aspirant
XR500 Reset Loop
I came home from work today to find that my brand new (less than a week old) XR500 had factory reset itself, wiping hours of setup. Luckily, I documented everything, so I proceeded to redo the setu...
Tylerleepart
Mar 11, 2020Aspirant
So, I got the XR500 to stop looping on me by doing a hard reset. However, now I'm fighting another issue.
If I do an IP reservation for a wired device, the router refuses to give that device an IP, unless I static it on the device side. Wireless is fine.
At this point, I'm simply blown away how this router can be so good, and so terrible at the same time.
If I do an IP reservation for a wired device, the router refuses to give that device an IP, unless I static it on the device side. Wireless is fine.
At this point, I'm simply blown away how this router can be so good, and so terrible at the same time.
- Netduma-FraserMar 11, 2020NetDuma PartnerHow have you been doing the reboot? - Unplugging, button in the back or from the interface? If you reboot using a method you haven't done does it still reset? When you're doing an IP reservation are you giving it a different IP to what it has already? If so then you would need to either release/renew the IP on the device or reboot it in order for it to take the new IP - that would be the same with any router. If you give it the same IP then there shouldn't be an issue.
- TylerleepartMar 11, 2020AspirantWhen I was rebooting I tried; reboot within the software, reboot by cycling the power switch, and reboot by pulling the power cord.
Either way, it seemed to be fixed now.
As far as the IP, I am giving it a different IP. In have tried rebooting the device, the router, and both.
It refuses to assign an IP if the wired device is in the reservation table. The device times out and assigns itself a 169.245.x.x internal IP.
By doing a search on the forum, it seems this is a common problem. It looks like downgrading to 2.3.2.22 is the solution. I'll try this later.- Netduma-FraserMar 12, 2020NetDuma PartnerOkay weird, glad its fixed now. I've not once seen an issue where setting the LAN IP causes the device not to connect. Could you take a screenshot of the IP you're trying to set prior to applying please?