Can't Manually Assign IP via DHCP List

[MightyGeekMan]

All,
Here's my problem;

When I try to manually assign IPs to my devices, like my NAS, it doesn't stick. For example; I manually assign the NAS to 192.168.1.100 via its MAC address. But when I click APPLY nothing changes. It shows up in the "Manually Assigned IP around the DHCP list" correctly, but when I check the clients on the network map it is showing as 192.168.1.56. And I can't access the NAS unless I use the 192.168.1.56 IP. I've rebooted everything on the network a dozen times and nothing has worked. This was all working perfectly a week ago, but I had to change routers (same model, old one fell down go boom) and now the DHCP isn't working. I set it all up last time without any problems so I'm at a complete loss as to why this is happening now. I'd rather not do static IPs for my NAS, but if I can't figure out what I'm doing wrong I may have to.

Here's a bit more info:
I'm using an ASUS RT-AC66U.
Firmware: 3.0.0.4.378_9313
DHCP server is enabled.
Enable Manual Assignment is on.

Anyone have any ideas what's going on?

 

[netwrks]

Does the NAS already have a static IP by any chance?

 

[VANT]

or corrected mac adress is entered to dhcp/static ?

 

[MightyGeekMan]

All,
After a few more days of working on the problem I finally stumbled across the solution. I'm not sure if this works for all network configurations or just my own, but what I discovered was that the order in which I rebooted my network devices mattered.

Apparently, when I set up assigned IPs via the ASUS router it would configure itself properly but not actually reassign the devices to their new IPs. In order for that to happen, I first needed to completely reboot the router (unplug it from power and network) and THEN reboot each network connected device by turning them off and on again. Once I did that everything worked as it should. If I rebooted the network devices without first rebooting the router, they would retain their randomly generated IPs and not the ones I assigned via the DHCP list. That was the big issue for me. The order needed to be manually reboot the router and then reboot all network connected devices.

I hope no one else runs into this odd problem, but if they do I hope this helps.

 

[RMerlin]

This is normal. Clients won't ask for a new DHCP lease until their existing lease expires (or reaches half-life with some clients).

 

[MightyGeekMan]

This is normal. Clients won't ask for a new DHCP lease until their existing lease expires (or reaches half-life with some clients).

True, which is why everything should have worked when I rebooted my networked devices. However they didn't get the correct IPs assigned until AFTER I manually rebooted the router first, and THEN each networked device. No clue why, but rebooting in that order worked when rebooting the network devices alone did not.

 

[L&LD]

True, which is why everything should have worked when I rebooted my networked devices. However they didn't get the correct IPs assigned until AFTER I manually rebooted the router first, and THEN each networked device. No clue why, but rebooting in that order worked when rebooting the network devices alone did not.

A reboot may or may not work, but shutting down each device definitely will.