NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Overtkill
Dec 15, 2025Aspirant
DHCP assignment issues on RS700 are not fixed
Trial Firmware for me too please. DHCP assignment issues on RS700 are not fixed with the October release 1.0.9.16_2.0.106. Options also seems skimpy in the configuration settings.
Thanks!!
8 Replies
- CrimpOnGuru - Experienced User
Overtkill wrote:
Options also seems skimpy in the configuration settings
That could use more explanation.
- FURRYe38Guru - Experienced User
What brand and model# ISP Modem or ONT do you have?
What DHCP assignement issue are you seeing?
On the RBRs web page?
What devices are you setting up with IP address reservations? IF any?
Any conflicts in IP address between two devcies or more?
Trial FW is for WAN side issues with ONT systems.
- FURRYe38Guru - Experienced User
Any progress and feedback on this?
Overtkill wrote:
DHCP assignment issues on RS700 are not fixed with the October release 1.0.9.16_2.0.106.
- OvertkillAspirant
My answer is directed solely at the Netgear Rep. on these forums.
Seems like a DHCP issue on the LAN side (Where's the lease time setting for this router??). Every week without fail, PC's will boot up with no Internet access through the RS700, requiring another reboot of each PC. Ethernet on my PC, which has seen this issue, is an Intel i226-V wired adapter on the motherboard. No issues with 2 older Netgear routers tried. RS700 has been updated to current firmware in October (1.0.9.16_2.0.106), reset and reconfigured several times as well. No changes. Adding machines (PC) to a reservation doesn't help. Devices on my LAN are mainly streaming, 2 phones and a tablet, 1 XBox (almost never used) and of course, several hand built PC's. Which are all on reservations at this point. No address conflicts exist at all. I am an admin BTW.
ONT is a Calix, 711, possibly a 712 series. I would have to open the box outside. No issues there either. I have tested connectivity separately with a laptop to the Ethernet cable, and found no issues on that side. Issue remains with the router. Cable also tests good and excellent quality on the link across the wire from my closet to the outside. (Cat-7 Analyzer tested.) PC's tested with another router while being bumped offline, connectivity works when another router (AX12) is dropped into the RS700's place. I used the same configuration on both, and the RS700 started working again after a reboot.
I've had my share of buggy routers from Netgear over the past number of years. The last one would overheat out of the box (AX12), thus failing at random and requiring a secondary fan blowing on the router constantly to keep it cool enough to operate. Same behavior with the replacement I received. So I bought this RS700 to replace the last one, figuring the Flagship model might work as expected. Which still has this issue regardless of the firmware I have tried to date. If this isn't resolved, I'll likely jump ship with Netgear as a brand. I am tired of buying EXPENSIVE buggy routers. And I have been a loyal customer for over 25 years, installing many switches and routers for customers as well. Some of us expect better hardware for our money.
- CrimpOnGuru - Experienced User
The default DHCP lease on every Netgear router I have tested has been 86,400 seconds (one day).
Overtkill wrote:
Every week without fail, PC's will boot up with no Internet access through the RS700
Does "boot up" mean:
- Power on (a cold start), or
- Wake from Sleep?
The reason I ask is I once had a Ethernet connected laptop that I would simply close the lid on rather than power off. When I opened the lid, it would start up but have no internet. "Damn Buggy Router"!!! So I set up Wireshark to capture traffic on the Ethernet adapter. When the lid was opened, the laptop sent a DHCP Query. The Netgear router responded with an offer. The laptop sent another query. Router sent another offer. This went on indefinitely. No matter how many DHCP offers the router made, the laptop never accepted one. The only solution was to either (a) reboot the laptop, or (b) use the Windows Troubleshooter to get connected. Annoying. A few months later, a Windows software update happened and the problem disappeared.
p.s. if you capture the DHCP offer from the router, that will clearly show the length of the lease time.