NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DHCP Address reservations ignored?
Hi all - In the router config I've reserved configured DHCP to reserve IP addresses for several of my devices. Some of the devices end up using their reserved addresses but some I cannot seem to get...
What FW version are you using?
What is the size of the default DHCP Address pool? If default, try setting the following size:
192.186.1.100 to .200. Then set up an IP address for your devices with in this new pool size. Select Add and Apply. Make sure the devices are set for auto obtain IP addressing. I would reboot the devices after changes are made on the router. After you hit apply, you might want to do a fully reboot then reboot all the rest of the devices.
You could try changing the network you're using. E.g., if you current network is 192.168.1.0, try using 192.186.10.0 (or .2.0 or whatever you want) instead, which will force all your connected devices to be issued new IPs (or you may have to power cycle some of them, or turn off and on their wifi), and may result in the Shield being properly issued its reserved address. If it works as intended, and you don't mind using a different network, then problem solved.
I had a smiliar issue which was down to misinterpretation of how the GUI works.
When you change the address and apply it you go back to the main address screen. You then need tosave the settings here. That second save may be the missing step? (Im going from memory here so excuse me if I am a bit vague)
You may also of course need to reboot the device in question
So I think my problem is resolved - I changed the DHCP pool address range to 192.168.1.100 - 200 as suggested in the first reply, changed all my reserved addresses to be within the new range and applying these changes I think caused the router to reboot itself or at least the wifi network went down briefly, and when it came back up every device seems to be using its assigned address. I'm gathering that changing the DHCP address range is what forced this to happen since just adding or editing reserved addresses did not when I had tried that earlier.
Glad the suggestioned worked. The default DHCP pool should work, however in most cases, the average home doesn't really need that large size of a pool. So you can reduce it. It also gives you room for some static IP address assigned devices on either side of the pool as well.
Enjoy. :smileywink:
MachThree wrote:
So I think my problem is resolved - I changed the DHCP pool address range to 192.168.1.100 - 200 as suggested in the first reply, changed all my reserved addresses to be within the new range and applying these changes I think caused the router to reboot itself or at least the wifi network went down briefly, and when it came back up every device seems to be using its assigned address. I'm gathering that changing the DHCP address range is what forced this to happen since just adding or editing reserved addresses did not when I had tried that earlier.
