NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBKE960 "Refused to Connect" after IP reservation changes
This is a report of a newly encountered issue with my Orbi RBKE963 (1 router + 2 satellites) running latest 7.2.7.15 firmware: After making IP reservation changes/additions and router rebooting, ...
Thanks for the clarification, FURRYe38!
I just made one quick change to the DHCP IP address pool range to be 192.168.0.2 to 192.168.0.199, which makes all my IP address reservations fall within the DHCP assignment range. A DHCP start address of 192.168.0.2 will even encompass the two Orbi satellites at 192.168.0.2 and 192.168.0.3.
The router has so far not gone into that mode of refusing connections. Even the Orbi phone app is happy now. I've added back the 80 or so address reservations and the router is still behaving properly.
Many thanks for this tip! I shall correct my understanding of how DHCP IP address assignment works.
The only thing left to do is to regain the active Netgear Armor subscription for this router...
Going through this thread, I believe that my issue is exactly what you have experienced. I went through a file I created that had my IP address listed and realized that I have a single device with a static IP address that falls within my DHCP range.
But reading through your message above, I'm a little confused. Did your RBS's have static IP addresses originally of 192.168.0.2 and 192.168.0.3 or were they dynamic?
The reason I ask is because you use the term 'IP address reservations'. I've always associated that term with static IP addresses.
You stated above that you changed your DHCP address pool range to be 192.168.0.2 to 192.168.0.199 so that your satellites are included. But if your satellites have static IP addresses, that would be an incorrect configuration.
So, are the satellite IP's static or dynamic?
Thanks in advance for your response.