All devices connect normally on the first attempt.
When using Pi-Hole DHCP, my Windows 10 PC and laptop that have static IPs set frequently report “No Internet, secured” on startup or return from sleep, and are not given IP addresses until they disconnect and reconnect to the network.
When this happens, the affected computers don’t appear to be being assigned IPs at all, according to ipconfig. They are completely unable to connect to the internet in this state, and it is fixed (and they are given the correct IPs) after disconnecting and reconnecting. The issue also disappears when going back to the router’s built-in DHCP; this is specific to when Pi-Hole DHCP is in use. (My ISP’s router doesn’t support using custom DNS, so I have to use Pi-Hole’s DHCP in order to make devices like my Roku stick use it.)
Possibly relevant notes:
- The msftncsi domains are whitelisted.
- The static IPs are within DHCP range (should they be set outside of it?)
- My ISP is AT&T; I’m using their BGW210-700 modem/router with its DHCP disabled. The modem appears to have a second MAC address that keeps showing up as DHCPDISCOVER lines in the logs, I blocked it because it never actually successfully sets an IP just to reduce logspam (if there’s a way to remove the ‘ignored’ lines please tell me); removing this has no effect on the wi-fi connection failure issue.
- There are other devices on the wi-fi including Windows laptops with no static IP, and an Android phone with a static IP, and none of these are affected; only the two Windows 10 computers with static IPs.
- I have a 5GHz and 2.4GHz wireless network, but the affected devices only connect to the 5GHz network (so differing 5G/2G MACs aren’t an issue), and other devices on the 5GHz are unaffected.