Fixed IP Addresses Not Working

Housey · 5 Sep 2016 at 14:50

I have set up a few devices on my home network with Fixed IP addresses but no matter how many times I reset the router, devices they are not using those IP addresses. Most are using DCHP to automate the IP addresses, but some devices need fixed IP's and it's becoming frustrating.

Thoughts?

ov_sjo · 5 Sep 2016 at 14:51

Private or public addresses?

Housey · 5 Sep 2016 at 14:54

Private, Netgear D7000

Housey · 5 Sep 2016 at 14:56

https://community.netgear.com/t5/DS...-Address-Reservation-not-Working/td-p/1088798

Seems I am not alone

bledd · 5 Sep 2016 at 14:58

How are they set as fixed, from within the devices or through a reservation by MAC address on the router?

I prefer to do it on the router side. Some routers require you to 'save' each config page and save the main config so it survives reboots.

I'm not familiar with your Netgear, best practice for reserving IPs on router is..

Say your current DHCP range is 192.168.1.2 to 192.168.1.254, edit it so the range is 192.168.1.50 to 192.168.1.254.

Any MAC reservations, give them IPs between .2 and .49 (this means thing else should ever try to snap up their IP).

-edit, I started typing this before you posted that

Don't want to read the whole thing, but check if the latest firmware has the issue.

DragonQ · 5 Sep 2016 at 15:07

Have you fixed the IP on both sides (router and clients)? I always do this anyway so that my devices can communicate even if the DHCP server is offline for whatever reason.

Housey · 5 Sep 2016 at 15:11

Thanks chaps, there is a firmware bug it would seem which Netgear are working to resolve. Gone back a release and it's now working as it should. Sorry for wasting your time!

Rroff · 5 Sep 2016 at 15:13

I've always just set the range 192.168.1.3 through 192.168.1.200 for DHCP range on the router (all my routers have allowed this so far) and then manually used 192.168.1.201 to 192.168.1.254 set as static IPs on the clients and everything has worked so far. (The last IP in the range is/can be used for broadcast uses so shouldn't be assigned to clients).

bledd · 5 Sep 2016 at 15:15

I set mine to 10.0.0.1 etc, so there's less to type

Rroff · 5 Sep 2016 at 15:19

I'd do that but every now and again you get hardware that is designed for 192.168.x.x and means extra messing about and/or the manufacturer overlooked that there are other valid private ranges and causes extra hassle :| probably not an issue most run into very often but with 2 dozen or more different devices passing through my network over a month it isn't completely rare.