NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR500 DHCP issue
I've had this router for 4 months now and it works fine most of the time. Once in a while I'll notice that some LAN devices become unresponsive, when I look into the issue it turns out that they have...
Boga the forum post you referenced in the NetDuma community sounds the same except mine occurs without a reboot and just happens after a certain amount of time lapses
This may have been suggested before, but have you tried installing this hotfix firmware?
https://kb.netgear.com/000060127/XR500-Firmware-Version-2-3-2-32
I just downgraded to V2.3.2.22 that was mentioned as being successful in the Netduma community post. Will reply if it occurs again.
Has this firmware version worked for people? Im also having this issue on the evenings but, its only affected apples devices( most devices in the house are apple )
I believe the wrong link was given for the hotfix firmware
This is the correct link
New XR500 hotfix firmware for drop outs - DumaOS on NETGEAR Nighthawk Support - Netduma Forum
It has been over a month since I have downgraded to V2.3.2.22 and everything is working it should. Hopefully this not only helps others with the same issue but it will be fixed in an upcoming patch.
Well I'm glad it's working for you! I'll make sure to tell the devs so we can figure out what it was the caused the problem.
Running that hotfix version and it didn't fix anything
D'oh...
Well i've responded to you on this thread: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/XR500-drops-internet/m-p/1762610#M11258
Haha Thats my bad. I wasn't aware it was moderated by the same people until I had already raised the issues. I think we are in discussion about this over 3 forums now LOL
No problem. Sometimes I don't realize i'm talking to the same person over email, chat and forums and then i'm thinking "wow this problem has happened to like 3 people at once, how weird"
- Well I thought I give the latest firmware (*.50) a shot and within 8 hours the same issue occurred and all connections were dropped. Can someone look into this as I’d like to stay up to date on a $300 router that now seems way overpriced?
What is the Mfr and model# of the ISP modem the NG router is connected too?
Has a factory reset and setup from scratch been performed since last update?
Try v32 version of FW?
I'd contact support and file a support ticket. Ask about a RMA:
https://www.netgear.com/mynetgear/registration/login.aspx
GooniesNvrSayDi wrote:
Well I thought I give the latest firmware (*.50) a shot and within 8 hours the same issue occurred and all connections were dropped. Can someone look into this as I’d like to stay up to date on a $300 router that now seems way overpriced?Firmware version 2.3.2.40 and 2.3.2.32 were tried and yielded the same results. Only 2.3.2.22 and earlier work. I have fiber internet and the ONT is Adtran 401 micro(the one without voice). Factory resets have been applied with various FW versions to no avail.
Is this your ONT?
https://portal.adtran.com/web/page/portal/Adtran/product/1287786G1
I see it's been discontinued and replaced with a new model. Maybe soemthing to try though not sure if this would effect what your seeing. Anthing is possible.
I would try NG support and ask for help on this. I would send them your debug logs for review. Maybe they can find where the problem is happening in later version of FW. Make not of earlier version is working. Ask about an RMA to see if a new router does the same thing or not.
GooniesNvrSayDi wrote:Firmware version 2.3.2.40 and 2.3.2.32 were tried and yielded the same results. Only 2.3.2.22 and earlier work. I have fiber internet and the ONT is Adtran 401 micro(the one without voice). Factory resets have been applied with various FW versions to no avail.
- How many devices do you have? Would it be practical to give all the devices added to the router a reserved IP and then disable DHCP completel to see if it helps. Furry suggestion is a good idea as well.
- I have more than 15 devices. Assigning a static IP to each would likely solve the symptom but not the problem and for a $300 router I shouldn’t have to work around an issue such as DHCP that is been solved for decades.
- I can totally appreciate that, it's not ideal at all. It is clearly something that we need to look into and fix but I couldn't reliably say when that might be so I'm trying to look for workarounds that will help in the meantime.
