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, ...
The two RBSE960 satellites have no functional issues being given 192.168.0.2 & 192.168.0.3 reservations while the router is 192.168.0.1. I've had this configuration for years. I always thought that IP reservations should have addresses that don't fall within the router's DHCP IP assignment range, to avoid confusing the DHCP server, and I've never had any issues with the Orbi configured this way. All my IP address reservations (~90) have been using 192.168.0.4 to 192.168.0.99 for a long time, but this issue of the router refusing connections has been observed very recently.
I'm losing admin access only to the RBRE960 router after adding more address reservations. The two satellites still respond to the browser at their respective IP addresses, but the router would persistently refuse connections to its 192.168.0.1 address.
I just restored router admin access via a hard reset and restoring from backup, but it would seem that rebooting the router can sometimes cause it to refuse connections afterwards. It's either that or the act of adding a bunch more IP address reservations.
All router/satellite functionality appear normal, except for the router's refusal of connections. Once this is triggered the admin ability of the router is completely lost, and I have to resort to hard reset to regain it.
No, ALL IP address reservations, per standard networking practice, something I went to school for, all should be with IN the DHCP IP address pool range. If you have a short pool range, then anything out side of this pool range is used for STATIC IP addressed devices, meaning that if you configure a devices for a static IP address in the device itself, this IP address needs to be OUTSIDE of the DHCP IP address pool range. Never with in it.
If you can get back in to the RBR, then you'll need to factory reset the router and setup from scratch, set your new IP address pool range then set RBS or any devices with IP address reservation INSIDE the IP address POOL. NOT outside of it. I've been using this configuration for going on 20 years now. Has not failed on any router system I've set up.
