NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR750 unable to assign IP addresses after reboot
Hi, every time I reboot or unplug my router to move it, all my devices will disconnect and will have an "unable to assign IP addresses" error. I have 48 devices and all of them will not connect. I wo...
I've had lots of problems with the DHCP server.
It has been worst on the AX routers (my 850 series) but I have also seen it (occasionally) on the 50 series.
The symptom is the DHCP server simply stops issuing IP addresses.
Excluding address .250 from the DHCP address range has improved the situation a "lot" but I'm not sure if this is the only problem with the DHCP server.
At least my Orbi is usable now, 😉
- Yes, I updated the firmware, rebooted and it messed up again. I tried to contact support and we go through the same troubleshooting on hard resetting. To them it's "fixed".
What version of FW is loaded on your system now?
What devices do you all have connected to the system?
Has a factory reset and setup from scratch been performed since last FW update? A complete pull of the power adapters for a period of time after the factory reset then walk thru the setup wizard and setup from scratch.
I recommend also changing the default DCHP IP address pool size to .100 thru .200 as well after the reset.Also enable ALG SIP on the router as well.
rayjai wrote:
Yes, I updated the firmware, rebooted and it messed up again. I tried to contact support and we go through the same troubleshooting on hard resetting. To them it's "fixed".I'm installing the new firmware later today. Will let you know if I have any issues.
I recommend also changing the default DCHP IP address pool size to .100 thru .200 as well after the reset.
Also enable ALG SIP on the router as well.
tucsontico wrote:
I'm installing the new firmware later today. Will let you know if I have any issues.
Just did the update to firmware 4.6.11.1_2.3.6. After a reboot and power down, I brought the RBR up first, allowed it to stabilize for 5-10 minutes. I checked the Guest Network. The RBR was not radiating the GN. I then powered up the nearest RBS. (My setup is a daisy-chain with 2 sats.) After it stabilized for 5-10 minutes, I checked and now the GN was radiating on the 2.4 gHz band. I powered up the second RBS and after stabilizing it was not radiating the GN. So the RBR and one sat are not radiating the GN. Only one sat is showing the GN being on even though it is NOT enabled. (BTW, I did not do a factory reset.)
To see if I could "fix" the GN issue, I enabled the GN at the RBR web GUI. I checked and all the RBR and RBSs were radiating the GN. I then disabled the GN. Now the GN is not radiating. However, I'm not convinced this will be a long term solution.
I have not seen any issues regarding assigning IP addresses. All my 42 devices have IP reservations and I never had any issues with the reservation not "sticking" or not being able to assign an IP address in the previous firmware or this version.
I have SIP ALG disabled and use .1-.60 for my DHCP pool. What is the rationale for enabling SIP ALG and changing the DHCP pool to .100-.200?
I am on V4.6.11.1_2.3.6.
After the reboot I had IP assignment issues. Even trying the reboot from restoring the configuration causes this.
I have Laptops, PC, phones, Consoles, Smart switches, smart home devices connected.
I have about 89 connected devices.
Darn! After about 36 hours of up time on the newest firmware (V4.6.11.1), my one sat began broadcasting the Guest Network again. 😫 I confirmed the GN is not enabled and it shows that on both the web-based GUI and in the ORBI app. I have not done a factory reset on any of my ORBI devices since the firmware update. It appears as only 1 sat is radiating the GN signal on the 2.4 gHz band.
I will try a factory reset of that RBS, then do a reconfiguration from scratch for just that sat. Cannot do that until after Thanksgiving. Will report results when completed. Wish me luck!
Perform a full factory reset on both router and satellite(s) then set up from scratch. Do not load any saved backup configuration files.
I recommend also changing the default DCHP IP address pool size to .100 thru .200 as well after the reset.
Also enable ALG SIP on the router as well.
rayjai wrote:
I am on V4.6.11.1_2.3.6.
After the reboot I had IP assignment issues. Even trying the reboot from restoring the configuration causes this.
I have Laptops, PC, phones, Consoles, Smart switches, smart home devices connected.
I have about 89 connected devices.
Someone said in the other FW build threads that they changed the SSID name in GN, enabled it. Let the system apply, then disabled GN again then this seem to help.
Let us know after the holidays. Enjoy Turkey day.😉
tucsontico wrote:
Darn! After about 36 hours of up time on the newest firmware (V4.6.11.1), my one sat began broadcasting the Guest Network again. 😫 I confirmed the GN is not enabled and it shows that on both the web-based GUI and in the ORBI app. I have not done a factory reset on any of my ORBI devices since the firmware update. It appears as only 1 sat is radiating the GN signal on the 2.4 gHz band.
I will try a factory reset of that RBS, then do a reconfiguration from scratch for just that sat. Cannot do that until after Thanksgiving. Will report results when completed. Wish me luck!
tucsontico wrote:
I will try a factory reset of that RBS, then do a reconfiguration from scratch for just that sat.
Factory Reset of a satellite is not nearly as involved as resetting the router. Chances are, when the satellite reboots, it will connect automatically to the router. Total time: under five minutes. There is nothing about a satellite to "configure" except for perhaps a custom name that has been assigned to the satellite in the Attached Devices display (which is for human interest only).
This did not work, Rebooted the router and it happened again.
Lo and behold, after doing nothing to my offending RBS, it stopped broadcasting the GN. No idea why it decided to do that. Of course, I have no idea why it started to radiate that signal in the first place. I did notice in the sat's web-GUI page the 2.4 GHz column "Wireless Mode" reports a speed of "Up to 240 Mbps". Previously, I believe that number was listed as "Up to 500 Mbps". I do have AX disabled for the 2.4 GHz band.
Still curious why furrye38 recommended enabling ALG SIP and reseting the DHCP range to .100-.200 for this latest firmware update. My system appears stable with 4 days of uptime. While I cannot prove it with data, it appears my web pages load a bit slower than before but that could be due to Black Friday server overloads!
NIce. Mysterious Orbi systems aren't they? LOL
Another poster mentioned they enabled SIP ALG on there system and seemed to work better. Normally on Orbi systems SIP is disabled. On Nighthawk routers it's enabled by default. Theres been information that SIP should be disabled for voice or video communications over the years however I've not seen any problems with having it enabled whatsoever. I think it may have been a troubleshooting step at some point for people seeing issues with Voice communication problems over the years. I Think there could have been other underlying factors as well besides having SIP enabled.
I've been using the smaller sized default DHCP IP address pool size for many years now. Got this from a competing router mfr that defaults there stuff to small sized pool instead of wide open. Most homes will never have 250 devices connected and having a small size pool for the router to work with, the router doesn't have to work at hard to deal with devices and IP address assignments. I've carried this over to my use of NG routers and has worked well for me and keeping NG stuff stable. Its always adjustable of course.
Be sure to save off a new backup config to file for safe keeping.
Remember you can disable Auto FW Updates now.
Yep. Never can tell what those spurious electrons will do! 😂
I will try enabling SIP ALG and see if there is any change. I already limit my DHCP pool to only 50 devices. I use XXX.XXX.X.1 thru .50. Never had an issue with DHCP assignments on either my original ORBI 50 or the current ORBI 750 using that scheme.
I also use IP reservations for every one of my 42 devices. It is my OCD showing through but I find it way easier to troubleshoot device connection issues if I do this. It also allows me to immediately notice if a "new" device has connected to my WiFi. (BTW, I do not use static IP addresses on the device side. It is very difficult/not possible on some devices to set this up.) While I cannot prove it, I believe folks having issues with DHCP assignments are overdriving their systems with too many devices. With 42 devices, I'm probably bumping up against the limit sometimes. When my current 750 gives up, I'll upgrade to the larger capacity 800 or 900 series.
Sounds like your system IS now working well and your not seeing any IP address assignment issues. Be sure to save off a new back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-SystemYa seeing problems in other NG router models and sometimes here on Orbi, wondering if there is a problem with using the wider IP address pool size. Been thinking there maybe some underlying issues with this kind of default configuration. Since I've been using the smaller pool size for years, I've not seen these issues to date or any oddities in this area. I may bring this up with NG and see what could be done. We know there are some other underlying issues at hand that need to be fixed. These could be causing extra problems as well.
I use this as a kind of a general rule for STATIC assigned devices, items that don't need much or any router management, devices that need some access but can be set and left alone and not accessed but occasionally, and devices that do have management pages that support input of static IP addresses. Devices like Printers, NAS, Cameras are some devices that don't need much and generally can be configured for Static IPs. I have 3 printers, 2 NAS and 3 cameras, all set for statics. Anytime I change out the home network router, I just make sure the incoming router has same network configuration and onces it's online, the static devices are automatically connected at there known IPs. No need for worry about them.
FURRYe38 wrote:Are any of you still seeing this issue with current versions of FW?
I'm not using the Orbis right now.
I'm pretty sure that I've seen this on all current firmware, including 4.6.9.11.
Have you seen this problem continue with the new FW?
raven_au wrote:
FURRYe38 wrote:
Are you using default DHCP IP address pool range?
What happens if you change that to .100 to .200 next time you use Orbi?
raven_au wrote:
I'm pretty sure that I've seen this on all current firmware, including 4.6.9.11.
I use .80 to .249 for the DHCP range.
FURRYe38 wrote:Have you seen this problem continue with the new FW?
raven_au wrote:
FURRYe38 wrote:Are you using default DHCP IP address pool range?
What happens if you change that to .100 to .200 next time you use Orbi?
raven_au wrote:I'm pretty sure that I've seen this on all current firmware, including 4.6.9.11.
I use .80 to .249 for the DHCP range.
I'm not using the Orbi right now.
I may put them back into use and check if v4.6.14.3 helps.
That version wasn't showing on the Netgear site when I posted the above.
I updated to V4.6.14.3 and it still doesn't work.
I had to restart my router today to move some things around and now nothing is connecting on wifi again.
I enabled SIP ALG and have set my range from 2 to 249.
I can't limit to 50 pool size for devices because I live in a multi family and we have about 125+ devices, not counting visitors.
