NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
6old3nra1n
Aug 06, 2020Tutor
ORBI not properly associating static IP
Hello! I've been trying to use the Address Reservation feature under Advanced -> Setup -> LAN Setup. I have a PC that is hardwired (Ethernet, not wireless) to the RBS50 satellite (not the base RB...
- May 04, 2022
I know this is an old thread but I was having the same problem with reserved addresses not getting assigned. I tried the "trick" of changing the DHCP addresses from x.x.x.21 to x.x.x.254 TO x.x.x.21 to x.x.x.100.
Restarted the devices that were not getting the addresses I wanted and it all worked. I had tried restarting the devices prior to changing the auto assigned addresses range and it did not work at that time. Only after changing the range of the auto addresses.
I know enough to know that should not change the addresses I wanted reserved. Nothing was assigned in the >100 range in the first place. All I know is it solved my problem.
6old3nra1n
Aug 07, 2020Tutor
So you guys won't believe this -- I decided to change the range of the DHCP-assigned LAN IP addresses from [192.168.1.2 to 192.168.1.254] to [192.168.1.2 to 192.168.1.100].
In my previous address reservation attempts, I set the reserved IP to 192.168.1.25 ...26, 27, etc. Then I set it to something really far out within the IP range, namely 192.168.1.100. Still within the original range, and still within the new range.
So technically nothing should change, right? But wait, there's more! When I changed the range, clearly the router did "something" and reset all connections. I noticed that even my router page was no longer accessible (for the time being). So when I simply typed "ipconfig" (without releasing or renewing anything) into my PC, it showed 192.168.1.100!
It's almost as if changing the DHCP-assigned IP range caused the system to start from scratch (perhaps the DHCP table itself got rebuilt) and therefore assigned my PC the correct reserved IP address of 192.168.1.100.
The question now is -- if I change the address reservation to another IP or if I reserve another IP for another device, will it work? Or will I have to "reset" the DHCP by changing the IP range again... I'm scared to try.. haha..
I know this is an old thread but I was having the same problem with reserved addresses not getting assigned. I tried the "trick" of changing the DHCP addresses from x.x.x.21 to x.x.x.254 TO x.x.x.21 to x.x.x.100.
Restarted the devices that were not getting the addresses I wanted and it all worked. I had tried restarting the devices prior to changing the auto assigned addresses range and it did not work at that time. Only after changing the range of the auto addresses.
I know enough to know that should not change the addresses I wanted reserved. Nothing was assigned in the >100 range in the first place. All I know is it solved my problem.