NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New RBR750 / RBS750 Firmware Version 4.6.3.16 Released
Security Fixes:
Fixes security vulnerabilities.
For more information about security vulnerabilities, visit https://www.netgear.com/about/security.
Bug Fixes:
Fixes the issue where the s...
Rebooting the router has no effect. I get the same situation. I can give fixed IP addresses to some devices on the network but not most of the IOT devices, there’s simply not that option. I can literally watch the attached devices page update as certain devices get a 192.168 IP and then go to no IP address assigned with the 169.254 address. Even those I told the Orbi to give a fixed address to. It sees them, but with a 169.254 address. Why wouldn’t it assign them a proper address if it can see them?! It’s quite strange. I spent hours on this tonight. I went back to my old Gryphon which I used to have problems with and that just worked. I simply don’t have time to troubleshoot for hours like this - this needs to work as I work from home most days and it was working for a year until the FW that added parental controls got pushed. I guess I know now not to recommend the Orbi to all my tech friends since Netgear screwed it up with this forced update. (Note, I don’t recommend Gryphon either for several reasons - I suspect I’ll end up going to Ubiquity as at least they sell commercial WiFi)
TSpoonEars wrote:
Rebooting the router has no effect. I get the same situation. I can give fixed IP addresses to some devices on the network but not most of the IOT devices, there’s simply not that option. I can literally watch the attached devices page update as certain devices get a 192.168 IP and then go to no IP address assigned with the 169.254 address. Even those I told the Orbi to give a fixed address to. It sees them, but with a 169.254 address. Why wouldn’t it assign them a proper address if it can see them?! It’s quite strange. I spent hours on this tonight. I went back to my old Gryphon which I used to have problems with and that just worked. I simply don’t have time to troubleshoot for hours like this - this needs to work as I work from home most days and it was working for a year until the FW that added parental controls got pushed. I guess I know now not to recommend the Orbi to all my tech friends since Netgear screwed it up with this forced update. (Note, I don’t recommend Gryphon either for several reasons - I suspect I’ll end up going to Ubiquity as at least they sell commercial WiFi)
It does sound a lot like the DHCP server is not assigning IP addresses but I thought those devices wouldn't show up in the devices list so maybe you have a slightly different problem.
There's no doubt in my mind the DHCP server is broken.
I spent more than an hour rebooting one time and evenutually gave up and setup my NAS as a DHCP server and things have been fairly good for me since then with the .16 firmware.
Even the initial affinity of devices to the main router seems to have settled down for me.
I sould also add the DHCP server problem is not a new problem. When I switched back to an RBR50 (becuase of the firmware problem) I also saw it once, it's not nearly as pronounced on the 50 series. Note that I hadn't seen it before on the 50 series but the number of devices I have now has grown to 60 to 70 and that's nowhere near what I had the time before that when I was using the 50 series. I'm convinced it's related to the number of devices and the volume of concurrent requests to the DHCP server.