Hi!

I’m having a weird issue while setting a static ip on my Windows 11 Desktop connected via ethernet, despite having done it for years without issue.

  1. I’m setting the static IP to 192.168.1.50 via network settings, along with the gateway and dns
  2. I will no longer be able to access any website via a browser
  3. However, I am still able to ping other devices on my network - and pinging www.google.com works

I read about, and see that you shouldn’t set an IP within the router’s DHCP range - which for me is uptil 192.168.1.1 - 192.168.1.253 (I cannot edit this, it’s an ISP router)

  1. I have tried a few different addresses that I know are not assigned to any other devices
  2. I had set 192.168.1.100 on my Raspberry Pi a few months ago, and that has been working without issue
  3. I noticed that if I set the IP on my Windows Desktop, the router will show the system - but with a different name - if it’s set to DHCP, then my router displays the correct device name.

The gateway and other settings are correct - and are the same I use on my Raspberry Pi.

Would appreciate any help!

  •  JoeB-   ( @JoeB-@alien.top ) BEnglish
    1•10 months ago

    …which for me is uptil 192.168.1.1 - 192.168.1.253 (I cannot edit this, it’s an ISP router)

    Are you certain that you cannot set the DHCP range on your ISP’s router? I suggest researching this option a bit further, including contacting your ISP tech support. I have never heard of an ISP-provided router not allowing customers to change the DHC range.

    Other options include:

    1. disabling the DHCP server on your ISP-provided router and enabling the DHCP server on your Pi-hole with a limited DHCP range as needed, or
    2. replace the ISP-provided router with your own router, which could save money if the ISP charges a monthly rental fee.
    •  csmiler   ( @csmiler@alien.top ) OPBEnglish
      1•10 months ago

      Yes - it throws a message about insufficient privileges and won’t let me edit, absolutely insane that they block this.

      1. Might have to consider this, not sure if it will let me disable DHCP - but I was also planning to stop using Pi Hole since it hasn’t been as efficient as I expected.
      2. From what I’ve read, I won’t be able to. It’s also strange since it seems like DHCP is being handled by the ONT and not the router
  •  Psynthesis   ( @Psynthesis@beehaw.org ) English
    1•10 months ago

    If you can’t change your DHCP pool, can you reserve the IP you want for the device in the router? You should be able to at least do that. That doesn’t answer the question as to why you are having problems, but it will get you going, and if you can’t change the pool, will prevent the router trying to assign something else to that ip. If you reserve in your router, be sure to change the setting back to DHCP in your windows device. Sounds like either another device is picking up that IP or your settings are off. If you want to stick with setting on your device, have you tried retyping everything in the network settings? What I mean is, completely delete every field, ip, subnet, gateway, dns, and retype. Verify it’s accurate. Then open cmd as admin, then release/renew and reboot or at least flush dns. It’s pretty easy for your brain to overlook an incorrect setting, when it wants to see the correct one. Happens to me all the time, lol.