NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Upgraded XR500 to V2.3.2.130 and shortly after all LAN ports not connecting to my devices
Hello, I recently purchased the XR500 a few weeks ago, upgraded FW to .114 and everything was working well. Then FW V2.3.2.130 was released so I upgraded and again everything seemed to be operati...
Hey Matt, thanks for detail!
Are you able to get to the DumaOS interface when using a device connected via ethernet?
What lights are illuminated on the XR500 and what colour are they?
Did you factory reset the XR500 after installing the latest firmware?
Hi Liam,
Thank you for your quick response.
The lights were lit white on the modem for 2/4 connected devices (the other two may have been offline from inactivity).
I did not attempt to connect to DumaOS interface via ethernet cable, nor did I perform a factory reset as I didn't want to loose my configurations for device names and QoS. Is a factory reset required after upgrading firmware?
I went through my xbox troubleshooting and it said the router may not be assigning an IP via DCHP and to try to give it a static IP. I gave that a shot and after clicking apply 3 times in the LAN setup menu it actually connected. I then gave the other 3 LAN devices a static IP as well and sure enough they connected. I then removed the 3 LAN devices from static to automatic and they were still able to connect. Not sure why that seemed to kick it into gear...
Regards,
Matt
We do reccommend a factory reset after upgrading firmware just because it's good for clearing out anything that could've been left over from the previous firmware. It's not always essential though.
It sounds as though the DHCP server is having trouble on the XR, though it's odd it only seems to be affecting wired devices.
It wouldn't be a bad idea to reserve IPs for these devices anyway, while we investigate DHCP issues with the XR routers. If you still have problems after that, please do let us know also.
I did a factory reset yesterday and all seems to be working okay now using dynamic IPs for the LAN devices. I'll post if the problem surfaces again.
Though it was strange, after I did the factory reset the QoS BW allocation had allocated a higher percent of BW to one device and the traffic prioritization was set for 2 devices that were not the previous two devices I had set. The open ports were the same as I had previously set. After a factory reset I would have assumed the BW distribution to be uniform and there to be no devices under traffic prioritization. Seems somehow there was still some retained info left over and it got assigned to the incorrect devices. I did the factory reset via router console, not the physical button on the router.
- Interesting, as we have changed those areas it may be they weren't added to be cleared by a reset, I'll pass this onto the team to investigate, thanks for the report!
