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 RBR50 router). So I put in an entry into the Address Reservation in an attempt to have the system associate a static IP to my PC. However, a day or so later, the IP of my PC changes (it was originally set up to obtain a reserved IP of 192.168.1.25) to something other than what the reservation was set up with. I have not rebooted my PC (it's always on as a file server) after setting up the Address Reservation.
I can't figure out why this is happening. This is a fairly basic feature (despite it being located in Advanced) and I'm surprised it is not working properly.
Any ideas? Thank you.
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.
53 Replies
Replies have been turned off for this discussion
Set that same IP address as static on the PC itself.
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.
And just for added info -- I rebooted a few times today and each time the ROUTER assigns a different IP. I haven't had the same IP assigned today despite the address reservation. Therefore, this is really a confirmation that the feature is not working as intended.
I agree with Mstrbig that one "sure fire" method is to (a) assign a static IP in the PC control panel (with the correct subnet mask, gateway, DNS server, etc.) and (b) make sure that this IP is NOT in the range of IP's that the Orbi DHCP server is giving out.
There are some definite issues with the way Orbi handles DHCP. For example, it appears to allow devices to renew an existing IP that is not the IP in the reservation table. Seems like "you already have it, so you can keep it." takes precedence over, "Hey Buddy. That IP does not belong to YOU." There have been other posts about errors in Orbi DHCP management.
That said, my Orbi correctly handles all of the devices that have assigned IP's. All of the devices use DHCP and once I got them on the correct IP they have stayed for months. Being attached to the router or satellite has never made a difference.
There have been issues come up when it turned out there was a second DHCP server in the network. This computer that is a "server", for example, is not doing DHCP is it? There are some odd-ball devices that do DHCP.
CrimpOn isn’t it a good (easier) practice to have a range of addresses that the router will not use/assign? Then, whatever address the user assigns to a device (from that router excluded range) will never create a conflict?
I think Linksys routers always came with such a range and I would pick fixed addresses from it without issues (without having to do anything on the router).
Or are the Orbit routers more intelligent and automatically recognize fixed addresses in devices and leaves them alone?That's probably a sensible methodology, but I'm not sure that the appliance should be forcing the user to do that, as there might be reasons why the user doesn't want to move a device's IP to another range. Maybe it took them a long time to get some other devices to interact with it, and they don't want to risk another slew of configuration changes they'd need if they changed it's address.
Also, I believe some DHCP daemons do the opposite of what the ORBI does, where manual IP assignments must be within the overall pool of IP's which the daemon is allowed to assign. So, for me, anyway, it's counter-intuitive.
This DHCP is rubbish.
The IP address reservations do not work. There is no stability (ie if a device had an IP address, and it was not resused elsewhere, then the device might not get the same IP address). If you edit the list of reservations you see that the list of existing reservations in the edit window differs from the list you see when you just click on the information page. What a complete p.o.s.
Then find something else that works for you or install a different router and use the Orbi in AP mode.
Haven't seen any DHCP issues when in router mode on mine. v16.
Sure I could find something else that works. But I paid for something that should already work. If Netgear will refund my purchase then I'll gladly return their hw/sw.
It works for you. Bravo. It doesn't work for me. Nor for many others according to this post.
