Windows 7 wont allow correct static IP

[SomeUserName]

7 windows wont let me set static IP on Laptop or desktop but it works fop all mobile devices. I have empty IPs. As in I want my laptop on 192.168.1.3 but it wont find and external IP and then when I do the winfix instead of giving it an exteranl IP address and keeping my 1.4 setting it sets it to 192.168.1.11. I don not want a buch of empty IPs. I want them in number order. So why does the ;aptop keep making it 192.168.1.11 when nothing is using 192.168.1.3 on the latop wireless and 192.168.1.4 on the laptop wired conection which is what I want. Wind0ze shouldnt be skipping a bunch of IPs at the lower level to use a higher one. Why would it pick 1.11? I dont even have 11 deviced. The highest IP that should be used is 192.168.1.8 and no high unless I get a new device.

Yesteday I had my desktop working on 192.168.1.2 but this morning I woke up with no internet connection. Did the winfix and it changed the IP from 192.168.1.2 to 192.168.1.12. Again with the desktop why is it choosing a nuber that is so high. If I dont own 11 devices then that OBVIOUSLY means I dont own 12 deviced and dont need to go as high as 1.12. Again my IPs should not be higher that 1.8 for my 7 devices and the gatewas using 1.1. Gateway on 1.1 + 7 devices = 1.8

HOW can I set it so the desktop LAN is 1.2 and the LAptop is 1.4 on the wireless and 1.3 on the wired if I plug it in and not have windows change the IPs to what it tthinks is best.

Ive been fighting with this for over 18 hours now. ALmosta full day.

 

[SomeUserName]

This is how I need to get this set up:

Gateway - 192.168.1.1 -- Working

Desktop LAN - 192.168.1.2 -- NOT WORKING - Changes IP to 1.12 <----These should not be changing
Laptop LAN - 192.168.1.3 -- NOT WORKING - Changes IP to 1.10 <----These should not be changing
Laptop Wifi - 192.168.1.4 -- NOT WORKING - Changes IP to 1.11 <----These should not be changing

Printer Wifi - 192.168.1.5 --Working
Wireless IP security cam - 192.168.1.6 -- Working
Android Phone 5g wifi - 192.168.1.7 -- Working
Android Phone 2.4Ghz wifi -- 192.168.1.8 -- Working

There should be nothing above 192.168.1.8 but the computers are making it so there is.

 

[doctore]

First and foremost, Windows does not assign IP addresses on a network. This is done by a DHCP server, usually on your router. Second, the DHCP server assigns the IPs at random, using a pool of available IP addresses. Unless you need static IP for an application, port forwarding, etc. - it makes no difference whether your host ID is .2 or .37

If you need the IPs to be in some order, for whatever reason, you should disable the DHCP and manually assign static IPs to each and every networked device.

 

[SomeUserName]

I think this is fixed. I hate when I i fix something but have no clue WHY the fix worked but what I did was unplug everything.

First turned on the router and then the desktop. Static is working on router and desktop.

Turned on the laptop with wifi and wired disabled and set the static IPs in there but something still was not working. Then I did something to get them both working but I could not connect to any other public routers because the wifi static IP was for *MY* router. So I put the LAN to the static of 1.3 and the wifi card to obtain automatically so basically 1.4 is now an open IP and 1.5 continues on statically with my printer. Since everything has been unplugged and replugged in one by one it seems working. I can connect to other routers now and for the few few tests I ran when I switched between wifi and LAn and also other routers when I came back to my router its now grabbing the open 1.4 IP which is what I wanted it to do statically.

Also I forgot a tablet computer I have so that has been assigned to 1.9 and is WORKING.

So this **seems** fixed now but what a pain in the ass this one was.

(The reason behind all this was last week remote desktop worked fine and then yesterday I went to use it and I got the 3 reason error message. Well before my DESKTOP computer was set to 1.3 which is what was in the router port fwd setting but sometime recently I guess my computer switched to 1.2 leaving the port fwd in the router at 1.3. I spent hours trying to figure out why it wouldn't connect including resetting all my firewall settings and doing the RDP setup manually but still no luck. THEN I spotted my computer IP was 1.2 while it was still 1.3 in the router. changed the router to 1.2 and it all started working again. (Also after the computer switched itself to 1.2 I was not able to connect with no-ip.org either)

So I am setting up my entire network statically except for 192.168.1.4 which Im keeping open for when I want to pull the wire from my laptop and go wifi while sitting around a fire in the back yard at night. This way I know EXACTLY where to find each device and dont have to worry about the IP switching)

(Also I am aware that if my laptop is plugged in and using 1.3 for LAN and the laptop wifi is off and I connect something else to the router it is going to grab the open 1.4 if the laptop isnt using it unless I first set the IP statically in the new device to 1.10 before connecting it OR turn on the laptop wifi so it grabs the IP first and THEN connect the new device and if I am correct then it should grab the NEXT unused ip at 1.10 which is one above my tablet at 1.9.)

 

[Tranquil Hegemo]

Can't you just assign static DHCP reservations for all of the seven\eight devices that you have using the mac address to define the ip address you want them to pick up and alter the non-static DHCP reservations to start at 192.168.1.10? It is how I would do it to achieve what you are looking to do.

The other option would be to alter where the non-static DHCP reservations start as outlined above and manually define the ip addresses for devices that you want them to have but it then (potentially) gives issues with the ip address that the wireless card gets assigned as it will be outside the range that you want it to be in.

 

[doctore]

You are looking at it the wrong way - it's not your computer that "grabs" an IP address, instead your computer is assigned an IP address. This is important because:

It's generally not a good idea to have both DHCP and static IPs, unless you change the DHCP pool to one section of the available host IDs on a network and assign static addresses from the remainder. For example, you should change your DHCP range on your router to assign IPs from 192.168.1.100 to 192.168.1.150 and use the 192.168.1.2 - 192.168.1.99 range for static IP addresses. In doing this you will avoid IP conflicts, because your DHCP could potentially assign to one computer an IP already in use by another.

You can navigate to 192.168.1.1 and log in to your router's setup page, where you can find the DHCP information and change the pool of IP addresses it uses to assign.

 

[SomeUserName]

OK before I go onto the next step and clear all my manually input static info from network and sharing center, I THINK and I HOPE I got this now. Networking confuses the hell out of me

The 254 I changed to 20 because there is no way that I will ever have 254 devices on here. Its a long shot that Ill ever even have 20 but regardless.

Does this look correct and can I clear all the static information I set for each device in Network and sharing center back to obtain automatically?

(EDIT: Since this post I have changed the ENDING IP address from 1.20 down to 1.15)

 

[Tranquil Hegemo]

You need it the other way around if you still want to maintain the ip addresses that you have. What you are changing is where the lowest ip address that DHCP will automatically assigned starts at so set the Starting IP Address to 192.168.1.20 and set the Ending IP Address back to 192.168.1.254. That gives you the ip address range 192.168.1.2 through to 192.168.1.19 to use as statically assigned DHCP addresses for your desktop pc, laptop pc etc. and leaves some overhead as well in case you need it. The rest - 192.168.1.20 through to 192.168.1.254 are assigned by DHCP as requested by other devices.

Hope that helps.

 

[SomeUserName]

YES I DO BELIEVE IT DOES!!! Along with what you say as well as right below Ending IP and above Address reservation theres a aqua"ish" colored line separating the 2 sections so use router as DHCP and Address reservation each are their OWN section.

So in other words to keep it the same way I have it now I would just set to the STARTING IP to 1.15 and anything above that will be assigned automatically up yo 254. But I *MAY* change down to 20.

So as it stands right now I have room for 7 more static devices and 5 random/temporary devices if I change it to the ending IP down to 20. But at this moment its set back to 254.

Now that I have the DHCP and address reservations set, it is now safe to set all my devices back to automatically obtain IP in network and sharing center?

 

[Tranquil Hegemo]

YES I DO BELIEVE IT DOES!!! Along with what you say as well as right below Ending IP and above Address reservation theres a aqua"ish" colored line separating the 2 sections so use router as DHCP and Address reservation each are their OWN section.

They are indeed - what you are doing is telling the DHCP pool to start at 1.15 and end at 1.254 so should I turn up at your house and ask to connect to your wifi then I would be assigned 1.15 as my ip address via DHCP (assuming that nothing else had that address already).

So in other words to keep it the same way I have it now I would just set to the STARTING IP to 1.15 and anything above that will be assigned automatically up yo 254. But I *MAY* change down to 20.

You can do that - I would just leave it at 254 and be done with it but it is highly unlikely to make any difference moving it down to 1.20

So as it stands right now I have room for 7 more static devices and 5 random/temporary devices if I change it to the ending IP down to 20. But at this moment its set back to 254.

Not quite - if you move the ending address down to .20 then you will have 7 more static devices on 1.2 - 1.14 and then the 5 randomly assigned ones on 1.15 - 1.20 and then 234 more potential static devices on 1.21 - 1.254.

Confused yet?

Now that I have the DHCP and address reservations set, it is now safe to set all my devices back to automatically obtain IP in network and sharing center?

Try one device and see what happens first and should that work as expected then try another would be my advice.

 

[SomeUserName]

I think I understand.

-Leaving it at .254 would let anything above .15 be randomly assigned

-Ending at .20 would not let any more be randomly assigned above .20 but the potential statics above that from .21 to .254 could only be used if I set it myself because I only allowed the randoms from .15 - .20

So I see 3 sections now:
1 - Static Assigned IP
2 - DHCP assigned
3 - POTENTIAL static IP.

If I wanted to eliminate the "potential" section, that is when I would want to put the Ending IP back to 254 to allow random assignments of all.

My hope was to not allow anything on above 1.20 to connect (security-network congestion reasons) but it sounds like thats not how things work and since I dont think I will ever have more than 15 static devices I'm going to leave the Ending IP at .254 as I don't need to "leave room" for over 200 more potential devices that will never connect here let alone need to statically.

Its hard for someone not in networking to put in words but I think I understand what you are trying to explain.


I've also now removed all the manual setting in Network and sharing centers IPv4 settings and put it back to automatically obtain and all devices seem to be working as they should.

 

[Tranquil Hegemo]

There is always a way of doing something but it is not going to be easy to explain and it is not going to achieve much more than what you have set up and by all accounts is currently working for you so better off leaving it as is to be honest. As the old saying goes "if it ain't broke then don't fix it".

From a security standpoint - make sure that you have a decent strong password on your router and you will probably be OK - if someone really wants to connect to your router then they will find a way to do so but make it difficult and they will probably go elsewhere.

 

[doctore]

I think I understand.

-Leaving it at .254 would let anything above .15 be randomly assigned

-Ending at .20 would not let any more be randomly assigned above .20 but the potential statics above that from .21 to .254 could only be used if I set it myself because I only allowed the randoms from .15 - .20

You got the gist of it.

My hope was to not allow anything on above 1.20 to connect (security-network congestion reasons) but it sounds like thats not how things work and since I dont think I will ever have more than 15 static devices I'm going to leave the Ending IP at .254 as I don't need to "leave room" for over 200 more potential devices that will never connect here let alone need to statically.

You can certainly have only 14 available IPs on your network. All you have to do is subnet it, i.e. change the subnet mask to 255.255.255.240 that will break your network into 16 subnets and you'll have 14 hosts on each. The first subnet will be from 192.168.1.1 to 192.168.1.14 and with the exception of your default gateway at 192.168.1.1 - you can assign the rest of them to other devices. Once all remaining 13 IPs are assigned - there is no more room for any other to connect.