NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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...
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.
Why would setting a static IP on the PC itself be necessary? Should the IP assignment that's router-based be enough? As in, the assignment comes from the router only, no other place. So when the IP changes to a different IP, that's based on what the router did, not any other device or source. The PC certainly didn't change the IP itself.
I don't think this feature is working properly on the router. I've had dozens of routers beforehand and all of them handled static IP assignments correctly WITHOUT having to assign a static IP on the computer/laptop itself.
6old3nra1n wrote:Why would setting a static IP on the PC itself be necessary? Should the IP assignment that's router-based be enough? As in, the assignment comes from the router only, no other place. So when the IP changes to a different IP, that's based on what the router did, not any other device or source. The PC certainly didn't change the IP itself.
I don't think this feature is working properly on the router. I've had dozens of routers beforehand and all of them handled static IP assignments correctly WITHOUT having to assign a static IP on the computer/laptop itself.
I did not say it was necessary. I just offered 1 solution. Sometimes I find it better to try a solution rather than dwell on a problem.
A Windows system will assign an automatic private IP in the 169.x.x.x range because it cannot find the DHCP server. Many things can cause this. Most of the time the only way to correct it is to flush DNS, turn off and restart the PC and more. One fix is to input a static IP address for that PC and reserve it in the router. Problem solved. I mention this because sometimes DHCP servers have issues too.