NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jerm1777
May 26, 2026Aspirant
RS700 DHCP Issues with newest firmware
I purchased an RS700 back in February and on the previous firmware I had the slow Wi-Fi issue and once I would login to the web UI and re-apply the Wi-Fi settings it fixed everything and seemed to be...
jerm1777
May 27, 2026Aspirant
The LAN is configured like this:
IP Address - 10.31.5.1
Subnet Mask - 255.255.255.0
DHCP Starting address - 10.31.5.2
DHCP Ending address - 10.31.5.254
I do have 5 reservations ranging from 10.31.5.101 to 10.31.5.105. Two of those are printers, two cameras, and my Reolink hub which is plugged in via ethernet. I have had this LAN setup on other routers without issue in the past including a Netgear R7000.
This whole issue happened after a fresh reset before I even set any of this up though using 192.168.1.1 for the IP and 192.168.1.2 to 192.168.1.254 as the range with no reservations setup.
FURRYe38
May 27, 2026Guru - Experienced User
Please try to see if the 192.168.1.1 or a 10.0.0.1 IP address string works and let us know the results.
You might contact NG support and open a support ticket.
If I can get some time, I'll try your IP address configuration on mine and see if I can reproduce anything.
Where and when did you first start using 10.31.5.1 subnet?
I normally use IP address pool range .100 to .200 on my RS700.
Printers, NAS, controllers and a few cameras are all set for static IP addresses ON these devices out side of this pool range. Leave inside the pool for Dynamic and IP address reservations. Which is standard practice.
I've not see any issues with this configuration. Been using this for past 20 years with zero issues.
- jerm1777May 27, 2026Aspirant
The default 192.168.1.1 address string does not work either even without any reservations setup. I mentioned that in the last line of the post you replied to. It does the same thing. I had it setup like that most of the day Monday over several reboots and every time I had to mess with it for an hour to get things to connect again by reapplying Wi-Fi settings. After it did the same thing with that subnet I decided to pop in my 10.31.5.1 subnet since I ruled that out being the issue. I have used the 10.31.5.1 address string for around 15 years in all of my past routers including my old Netgear R7000. The numbers signify something and that is how I came up with it years ago.
I never had a problem setting up reservations inside the pool range, but I always kept them higher up in the range. I can try setting them outside the range and making my pool smaller. I just don't think that will fix the problem either since it does it with the default pool with no reservations set to begin with.
I would contact support and open a ticket, but I am past the 90 days of free support.
- FURRYe38May 27, 2026Guru - Experienced User
And I presume you have your prior router that still works with that configuration?
Possible that your RS router maybe faulty.
Can try a 30-30-30 reset and see if this clears the issue or not. First try 192.168.1.1. If not, router would need to be checked by NG.
I'll try your configuration on my RS700.
- jerm1777May 27, 2026Aspirant
I do not have my prior router as I just sold it a few weeks ago. It was an Amplifi Alien and it worked flawlessly with that same configuration.
I can try a 30-30-30 reset and setup again when I get a chance. Oddly enough though this issue didn't happen until I updated to the newest firmware. I did have the slow Wi-Fi speeds on the previous firmware which I had to go into Wi-Fi setup after a reboot and apply the Wi-Fi settings to get the speeds back. Monday I also tried manually reloading the previous firmware and after rebooting I ran into the same DHCP issue so not sure it is firmware related. Until I updated to the newest firmware I had a pretty long uptime of probably at least a month and a half so something could have maybe failed in the router and a reboot triggered it. It's just odd that after messing with settings for a while I can get it stabilized and it's solid until the router is rebooted.