NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 Unable to Obtain IP Address after rebooting Obri - unable to reconnect to SSID after restart
RBR850 Unable to Obtain IP Address after rebooting / restarting Obri - Unable to reconnect to SSID after reboot / factory reset. Hello, I was having some trouble with my download speeds throu...
Hello,
The "Unable to Obtain IP Address" is the error that is displayed on the Samsung phone when attempting to connect to the production SSID. The current firmware of the Orbi is listed at the bottom of my original message ... 4.6.9.11.
The "modem" in front of the Orbi is a fiber to the door solution ... there is no model # on the fiber to ethernet converter but all it does is supply an IP to the router. A router is required for the fiber solution to work. The device cannot provide those services
This all happened after a simple reboot of the Orbi. I've read many other posts describing this same situation but no solutions. When certain devices attempt to connect to the SSID after reboot / factory refresh they are not able to connect. Either they say they were not able to obtain an IP address (both the hardwired PS5 and the Android Samsung give this error) or they simply do not connect. Is there a way to tell what is happen in the logs or something else that I might not be familiar with short of running a Wireshark on it?
Thanks!
Hello,
The "Unable to Obtain IP Address" is the error that is displayed on the Samsung phone when attempting to connect to the production SSID. The current firmware of the Orbi is listed at the bottom of my original message ... 4.6.9.11.
The "modem" in front of the Orbi is a fiber to the door solution ... there is no model # on the fiber to ethernet converter but all it does is supply an IP to the router. A router is required for the fiber solution to work. The device cannot provide those services
This all happened after a simple reboot of the Orbi. I've read many other posts describing this same situation but no solutions. When certain devices attempt to connect to the SSID after reboot / factory refresh they are not able to connect. Either they say they were not able to obtain an IP address (both the hardwired PS5 and the Android Samsung give this error) or they simply do not connect. Is there a way to tell what is happen in the logs or something else that I might not be familiar with short of running a Wireshark on it?
To answer the questions from the other persons post:
What is the size of your home? Sq Ft? 2,900 SQ
What is the distance between the router and satellite(s)? 30 feet or more is recommended in between RBR and RBS - 55 ft
️What channels are you using? Auto?
Any Wifi Neighbors near by? No
nothnagc wrote:
Hello,
To answer the questions from the other persons post:
What is the size of your home? Sq Ft? 2,900 SQ
What is the distance between the router and satellite(s)? 30 feet or more is recommended in between RBR and RBS - 55 ftHow many RBS do you have deployed? one or two?
️What channels are you using? Auto? Try setting manual channel 1 on 2.4Ghz and 40 channel on 5Ghz.
Any Wifi Neighbors near by? NoRecommend setting the default DHCP IP address pool range to the following after applying and a factory reset: 192.168.#.100 to 192.168.#.200
Also try and use the Forget this Network feature on the phone, then try to reconnect to the Orbi system.
Issue Resolved (root cause still unknown)
Here are the steps that resolved the issue.
1. Changed the DHCP scopes starting address to 192.168.1.100 (was 192.168.1.2)
2. Changed the DHCP scopes starting address back to 192.168.1.2
3. Problem clients were all able to re-attach to the default SSID (Devices Online jumped from 65 to 79)
Furrye38, after reading your message I decided to try the DHCP change that you suggested. After the initial configuration update to the DHCP scope there was no change. Several clients, wired and wireless, were still receiving the "Unable to Obtain IP Address" or "Failed to Obtain IP Address" or no error at all, they just could not connect to the default SSID since the initial reboot of the router. Since the update to the DHCP scope didn't work, I decided to revert the DHCP settings back to their original configuration. After this change, all of the troubled clients suddenly re-connected. The Devices Online jumped from 65 to 79. I'm not sure what the problem was but reconfiguring the DHCP service a couple of times did the trick. Maybe stopping and starting the service for the change did it, I'm just not sure.
Thanks for the suggestions and the help!
This maybe one cause, (Devices Online jumped from 65 to 79) This many devices coming online maybe bogging the system down when there all trying to connect at once thus maybe seeing these odd issues. I recommend setting the .100 thru .200 DCHP range. Also I recommend setting any devices that doesn't need much router management, items like printer, NAS, controllers, and cameras, set STATIC IP addresses on these devices that's out side of the DHCP IP address pool range. This may help alleviate the router having to rush to assign IPs for that many devices.
