A static IP fails when the address sits outside the router's subnet, collides with a DHCP-assigned device, or uses a wrong subnet mask or gateway. Fix it by reserving the address outside the DHCP pool, matching the LAN subnet exactly, and setting a reachable gateway plus valid DNS servers.
Symptoms
- Device shows "limited connectivity" or an APIPA address (169.254.x.x) despite manual configuration.
- Ping to the default gateway times out or returns "destination host unreachable".
- Two devices intermittently lose the network with a Windows "IP address conflict detected" balloon.
- Local file shares and printers work, but internet browsing fails or DNS never resolves.
- Router web UI drops the client shortly after applying the static settings.
Common Causes
IP outside the LAN subnet
The chosen address does not belong to the router's LAN range. A device set to 192.168.2.50 on a 192.168.1.0/24 network cannot reach the gateway at all.
Overlap with the DHCP pool
The static address falls inside the range the router hands out automatically. Sooner or later DHCP leases the same address to a laptop or phone and a conflict follows.
Wrong subnet mask
Mixing /24 (255.255.255.0) with /23 or /16 on the same segment breaks unicast routing. The device thinks remote hosts are local, so ARP fails instead of forwarding to the gateway.
Unreachable or wrong default gateway
A typo like 192.168.1.11 instead of 192.168.1.1, or a gateway on a different subnet, kills all traffic beyond the local LAN even though ping to neighbours still works.
Missing or invalid DNS
Manual IPv4 configuration requires manual DNS. Leaving the fields blank or pointing at an internal server that is offline produces "page cannot be found" while ping by IP still succeeds.
Step-by-Step Fix
- Confirm the current LAN subnet and DHCP range on the router
Log in to the router's admin page and note the LAN IP, subnet mask, and the DHCP start/end addresses. You need these three values before you assign anything. Write them down; guessing is what causes most static IP problems in the first place. - Pick an address outside the DHCP pool but inside the subnet
If the router is 192.168.1.1/24 and DHCP serves .100 to .200, choose something like 192.168.1.20. Never reuse the router's own address. For servers and printers, group them into a predictable block (for example .10 to .30) so future you can find them. - Enter IP, mask, gateway, and DNS on the client
On Windows, open ncpa.cpl, right-click the adapter, choose Properties, then IPv4, Properties, and select "Use the following IP address". On macOS, use System Settings, Network, Details, TCP/IP, Configure IPv4: Manually. Fill every field, including two DNS servers such as 1.1.1.1 and 9.9.9.9. - Verify the configuration from the command line
Run ipconfig /all on Windows or ifconfig / ipconfig getifaddr en0 on macOS and confirm the values applied. Then ping the gateway, ping 1.1.1.1, and finally ping a hostname like cloudflare.com. Each stage that fails points to a specific layer: gateway, routing, or DNS. - Resolve address conflicts with arp and a ping sweep
If Windows warns about a duplicate address, run arp -a to list MAC-to-IP mappings, then ping the suspect address from a different device and check arp again. The offending MAC tells you which piece of hardware also claims the address. Either move it or reserve the IP in DHCP so it stops competing. - Reserve the address in DHCP instead of setting it on the client
On most SOHO routers and on Windows Server / pfSense, a DHCP reservation binds a specific MAC to a specific IP. The device still requests DHCP, but always receives the same address. This avoids client-side misconfiguration and survives OS reinstalls without touching network settings again. - Check firewall, VLAN, and switch port settings
Managed switches with port-security or 802.1X may block a device whose MAC-IP pairing changes. If the static IP is on a different VLAN than the gateway, tagging must match. Temporarily disable the host firewall and any endpoint protection network filter to isolate whether the problem is layer 2 or layer 3. - Flush caches and confirm end-to-end connectivity
Run ipconfig /flushdns and netsh int ip reset on Windows, or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS. Reboot the device once, then re-test browsing, printing, and remote access. A clean cache prevents stale ARP or DNS entries from masking a working fix.
Quick diagnosis by symptom
| Symptom | Likely cause | First action |
|---|---|---|
| APIPA address 169.254.x.x | DHCP fallback triggered, static not applied | Re-check adapter properties, confirm "Use the following IP" is selected |
| Ping gateway fails | IP outside subnet or wrong mask | Match LAN subnet, set mask to 255.255.255.0 for /24 |
| Ping IPs works, names do not | Missing or wrong DNS | Add 1.1.1.1 and 9.9.9.9 as DNS servers |
| Windows conflict warning | Another device holds the same IP | Run arp -a, move device or add DHCP reservation |
| Works locally, no internet | Wrong or unreachable gateway | Set gateway to the router's LAN IP |
| Drops after a few minutes | IP inside DHCP pool, later re-leased | Move static IP outside the DHCP range |
Prevention
- Document every static IP in a simple spreadsheet with hostname, MAC, purpose, and owner.
- Prefer DHCP reservations over client-side static entries whenever the router supports them.
- Split the /24 into zones: routers, servers, printers, DHCP pool, guest, and stick to it.
- Review the reservation list quarterly and remove decommissioned devices to free addresses.
FAQ
Should I set a static IP on the device or use a DHCP reservation?
Use a DHCP reservation whenever the router or DHCP server supports it. The device still boots with DHCP, so a reinstall or move to another network keeps working, but it always receives the same address. Client-side static IPs are only better for devices that must come up before DHCP responds, such as the DHCP server itself or an out-of-band management interface.
What subnet mask should I use for a home or small office network?
For almost every home and small office, 255.255.255.0 (a /24) is correct because that is what the router hands out by default. Only change it if you have deliberately expanded the LAN to a /23 or larger. Mixing masks on the same segment causes silent breakage: some hosts reach the gateway, others do not, depending on which side of the boundary the target address falls.
Why does my static IP work for local devices but not the internet?
Local traffic only needs a correct IP and mask, so file shares and printers keep working. Internet traffic needs a reachable default gateway and functional DNS. If either is missing or wrong, browsing fails while LAN pings succeed. Verify the gateway matches the router's LAN address exactly, then confirm DNS with nslookup or by pinging a hostname.
Need help mapping your network and locking down static assignments? Contact our IT support team for a configuration review.