NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DHCP Server is buggy
Just a friendly message because it may help others. I'm using an RBR50 with 1 RBS50 sattelitte on firmware V2.3.1.60 ... I've been having a horrible time with the smart switches in my house (I have a...
I just noticed the new upgraded firmware (V2.3.5.30) and in the release notes is this fix:
[Bug Fixes] The client was not able to obtain an IP address when the router rebooted or the client renewed the IP address
I'll try to update over the weekend when I have some time, but this seems like a likely fix to my issue since my problem was that subsequent reboots of my large network always ened up with some devices unable to obtain an IP Address (with different numbers not working each time). I'll report back if this fixes it, but I'm hopeful.
What you are asking is impracticable. All of my IOT devices address already configured for my network ssid and are hardwired into my wall. They will connect as soon as the right network is available. Even if I create a new network and manually move them one by one which takes 2 to 3 minutes a device, a simple power outage will have then all join as once next time. The DHCP server must handle that many clients at once. My old rt n12 router with a smaller memory and slower CPU handles this just fine.
LIKEWISE if a factory reset is standard operating procedure for a firmware update then I should have been informed to do that when I first setup the router. also, I don't want to repeat the procedure you suggested for the next firmware update.
Like I said before my setup works great with the old routers dhcp service. Overall I like the orbi. It provides solid wifi coverage in my larger house. It does seem clunky from a software perspective, taking a long time to load its web interface and reboot. But I can live with it. My purpose for posting was less about getting a fix, and more about helping those who might be seeing similar issues. I do hope that NETGEAR takes notice and gets to fixing the bugs in thier software.
LIKEWISE if a factory reset is standard operating procedure for a firmware update then I should have been informed to do that when I first setup the router. also, I don't want to repeat the procedure you suggested for the next firmware update.
Like I said before my setup works great with the old routers dhcp service. Overall I like the orbi. It provides solid wifi coverage in my larger house. It does seem clunky from a software perspective, taking a long time to load its web interface and reboot. But I can live with it. My purpose for posting was less about getting a fix, and more about helping those who might be seeing similar issues. I do hope that NETGEAR takes notice and gets to fixing the bugs in thier software.
A factory reset normally isn't needed, however working with Orbi and others over the time, factory resets have given resolve to users problems. Mostly due to configuration issues and some with how new FW gets updated. A factory reset is a valid troubleshooting step and again, would need to be performed to prove your claim. Others have not posted about having this issue like you have. Most users have working systems and even while not having as many devices, Orbi seem to work well as does the DCHP server.
I have a friend whos Orbi has been setup since day one about two years ago. Has never seen a factory reset since I set it up. Other users are not so lucky. Orbi is an interesting system to say the least. Works well for some, not so much for others. Why some of us are here to help out and help find the real issue. Most of the time we can help resolve issues. It also takes participation of the users to listen and follow what some of us here help out with.
If you feel this is an issue, you would be best served by filing a support ticket here:
https://www.netgear.com/mynetgear/registration/login.aspx
This would better notify NG of the issue your seeing and again you'll need to prove to them that the system is working as designed with out a 2ndary router involved. There are debugging collection abilities with Orbi what would be useful to send to NG for review.
At any rate, good luck in your endevours.
- Fyi. I had already notified NETGEAR by opening a ticket before this post. My post was to notify others because no one was talking about this issue.
As far as proving things, I don't need to prove anything to anyone. If anyone is facing the problems I described above I recommend they try replacing the dhcp server to see if it helps!Also could be a possible issue with your network environment or maybe faulty HW. There many various network environments and HW that could be a cause. With out more investigation, hard to tell and cant' really point to only Orbi.
Most Orbi systems are working for Orbi users and DHCP is working for them. Mine as well.
Good Luck.
I just noticed the new upgraded firmware (V2.3.5.30) and in the release notes is this fix:
[Bug Fixes] The client was not able to obtain an IP address when the router rebooted or the client renewed the IP address
I'll try to update over the weekend when I have some time, but this seems like a likely fix to my issue since my problem was that subsequent reboots of my large network always ened up with some devices unable to obtain an IP Address (with different numbers not working each time). I'll report back if this fixes it, but I'm hopeful.