Network troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Home networking, Wi-Fi routers, modems, Windows/macOS internet issues, DNS & IP configuration, ISP setup

Fix device won’t connect with static IP — no internet, wrong gateway, DNS or subnet mask

Technician avatar Technician
Hi! We’ll get your device that won’t connect with a static IP back online. I just need a quick picture of how you’ve set the static IP address so we can target the right fix.

Does the device (PC, camera, printer, NAS, etc.) get internet when you leave it on automatic/DHCP, and only lose internet after you set a manual IP? What kind of router are you using, and what IP, subnet mask, default gateway, and DNS servers did you type in on the device?

Finally, when it’s using the static IP, do you see errors like “No internet”, “Unidentified network”, or can’t even ping the router?
Customer
It’s exactly that. On my Windows 11 PC, if I leave it on “Obtain an IP address automatically” it connects to Wi-Fi and internet just fine. But I want a static IP for port forwarding and remote desktop. As soon as I set a static IP, the status changes to “No internet, secured”.

I set the IP to 192.168.1.50, subnet mask 255.255.255.0, gateway 192.168.1.1, DNS to 8.8.8.8 and 1.1.1.1. The router is a TP-Link Archer. Other devices are fine on DHCP, only this PC won’t connect with static IP.
Technician avatar Technician
Got it, that helps. When a device loses internet after setting a static IP, it’s almost always a configuration mismatch rather than a bad router.

Typical causes when a static IP is not working:
• The IP is on the wrong subnet compared to the router’s LAN (for example 192.168.1.x while the router is 192.168.0.x).
• The default gateway is missing or set to the wrong address, so your traffic never leaves the local network.
• The subnet mask doesn’t match the router’s LAN (e.g. 255.255.0.0 instead of 255.255.255.0).
• Incorrect or unreachable DNS servers — you can sometimes ping IPs but websites still fail.
• An IP address conflict where the static IP overlaps with the router’s DHCP range or another device.

First we’ll read the working DHCP settings on your PC and copy them as a baseline, then I’ll show you how to choose a static IP address that’s in the correct range with the right gateway and DNS so the device connects again.
Customer
On automatic settings, ipconfig shows:
• IPv4 address: 192.168.0.23
• Subnet mask: 255.255.255.0
• Default gateway: 192.168.0.1
• DNS servers: 192.168.0.1 and 8.8.8.8.

So my router is actually 192.168.0.1, not 192.168.1.1. I guess that’s already a mismatch. I changed to static 192.168.1.50 because I thought any private IP was fine. After that I get No internet and can’t open web pages.
Technician avatar Technician
That explains it perfectly. Your static IP configuration was on a different network (192.168.1.x) than your router (192.168.0.x), so the PC couldn’t reach the default gateway or internet.

Step A — Mirror the working network, then pick a safe static IP
1) Switch the adapter back to Obtain an IP address automatically and confirm the internet works on DHCP.
2) Note the router’s IP (default gateway) and subnet mask. In your case those are 192.168.0.1 and 255.255.255.0.
3) Log into the router and check the DHCP range. A common range is 192.168.0.100 – 192.168.0.199. We’ll choose a static IP outside that range but still on the same subnet, for example 192.168.0.210.
4) Now set the PC to use a static IP:
  • IP address: 192.168.0.210
  • Subnet mask: 255.255.255.0
  • Default gateway: 192.168.0.1 (router’s LAN IP)
  • Preferred DNS: 192.168.0.1 (or your ISP DNS)
  • Alternate DNS: 8.8.8.8 or 1.1.1.1.
5) After applying, open Command Prompt and run ping 192.168.0.1. If you can’t ping the gateway, the device still isn’t on the right network. If you can, we’ll test external connectivity next.

Once the IP, subnet mask and default gateway line up with the router’s LAN, your device should stop saying “device won’t connect with static IP” and at least be able to talk to the router.
Customer
I changed it to 192.168.0.210 with the same mask and gateway as you suggested. Now I can ping the router just fine, and ping 8.8.8.8 also works. But websites still don’t load unless I type the IP address. So with the static IP I clearly have connectivity, just not name resolution. Windows still shows “Connected, internet” but browsers say “DNS address could not be found”.
Technician avatar Technician
Great troubleshooting — if you can ping 8.8.8.8 but not google.com, the static IP DNS settings are the only thing still off.

Step B — Fix DNS when device won’t connect with static IP
1) In the IPv4 properties where you set the static IP, make sure “Use the following DNS server addresses” is filled in correctly. For a home router, a safe combo is:
  • Preferred DNS: your router IP (192.168.0.1)
  • Alternate DNS: 8.8.8.8 or 1.1.1.1.
2) Click OK to save, then open Command Prompt as admin and run:
  • ipconfig /flushdns
  • ipconfig /registerdns
3) Disable and re-enable the network adapter or quickly toggle Wi-Fi off/on.
4) Test ping google.com and browse a few sites.

On Windows, a device won’t connect with static IP fairly often because people only copy the IP and gateway and forget to fill in DNS servers. Once those match what DHCP was handing out, the static configuration behaves the same as the automatic one, just with a fixed address.
Customer
Updating the DNS fixed it — the PC now works with the static IP address and internet is fine. Thanks!

I have another related issue though. A Wi-Fi security camera shipped with a hard-coded static IP of 192.168.1.64. My router is still on 192.168.0.x, so the camera app often says “device offline” or “cannot connect to camera with static IP”. It only works if I temporarily change the router LAN to 192.168.1.1, which breaks everything else.
Technician avatar Technician
That camera is running into the same core problem: its static IP is on the wrong subnet for the rest of your network, so your phone and PC can’t reach it unless you move the whole LAN.

Step C — Fix IoT / camera that only works with a static IP
• Temporarily connect one laptop directly to the router and change the router to 192.168.1.1 only long enough to reach the camera’s web UI or app.
• In the camera’s network settings, change it from “static IP” to “DHCP” if possible. Let it grab a working 192.168.0.x address from the router.
• Alternatively, set a static IP that matches your real LAN: for example, IP 192.168.0.220, mask 255.255.255.0, gateway and DNS 192.168.0.1.
• Change the router back to 192.168.0.1 and confirm you can ping and view the camera from a PC or phone on the same Wi-Fi.

Long-term, the easiest way to keep a device at the same IP without breaking the internet is to use a DHCP reservation on the router instead of setting the IP manually on the device. You bind the camera’s MAC address to an IP (say 192.168.0.220), so it always gets the same address but still uses valid gateway and DNS automatically.
Customer
I see. I set the camera to static 192.168.0.150, but I just checked and my router’s DHCP range is 192.168.0.100–192.168.0.199. Sometimes the router gives that IP to a phone too, and then one of them drops. So I guess I’ve created an IP conflict with static IP and DHCP.
Technician avatar Technician
Exactly — that’s a classic reason a device won’t connect with static IP and keeps vanishing from the network.

Step D — Avoid IP conflicts between static IP and DHCP
1) In the router, either:
  • Shrink the DHCP range (for example to 192.168.0.20–192.168.0.150) and use higher addresses like 192.168.0.201–254 for manual static IPs, or
  • Leave all clients on DHCP and create address reservations for key devices (PC, NAS, printer, camera).
2) If you keep using static IP on devices, make a simple list with:
  • Device name → IP address → MAC → location.
3) Any time you see “duplicate IP address detected” or random drops, check if a static IP overlaps with the DHCP pool or another manual assignment.

Once each device has a unique IP on the correct subnet, “no internet after setting static IP” and disappearing cameras are much less likely to come back.
Customer
That clears up a lot. One last thing: my work laptop seems to have a static IP configuration for the office. When I bring it home, it sometimes won’t connect at all — no DHCP, no internet, it just keeps saying “limited connectivity”. I can’t change most of the settings because IT has them locked. Anything simple I can try?
Technician avatar Technician
Corporate laptops are often locked to a particular static IP or VPN profile, so they behave oddly on home Wi-Fi.

A few safe things you can try (that usually don’t violate policy):
• On Windows, check the adapter’s Alternate Configuration tab — some companies allow a “User configured” profile there with obtain IP automatically for home networks.
• Disable any “use this connection only for resources on its network” options in VPN clients so your internet doesn’t break when the VPN is off.
• If nothing is editable and the laptop still won’t connect with static IP outside the office, it’s best to open a ticket with IT and explain you need it to use DHCP on home networks.

For your own devices though (PCs, cameras, printers), now you know how to set a working static IP address that has the correct gateway, subnet mask, and DNS so they stay online reliably.
Customer
Makes sense. I’ll leave the work laptop to IT and just use my own PC for remote access. With your steps, the static IP on my PC and camera both work now and there’s no “no internet” message anymore.
Technician avatar Technician
Awesome — glad we got your static IP setup cleaned up.

Summary: When a device won’t connect with static IP, first confirm it works on DHCP, then match the router’s LAN network (IP range and subnet), set the default gateway to the router, fill in valid DNS servers, and avoid IP conflicts with the DHCP pool. If you ever get stuck again — “no internet after setting static IP”, “unidentified network”, or random drops — you can open a chat with an expert and we’ll walk through the exact settings with you.
Customer
Perfect. Everything is stable and port forwarding works too. Thanks for the detailed static IP help!
Technician avatar Technician
Any time! If a friend or coworker complains that their device only works on DHCP or “no internet after setting static IP”, you can share this checklist — and if you’d like someone to click through the IP, gateway, and DNS settings with you in real time, just start a chat with an expert and we’ll take it from there.

Quick answer: the accepted fix

Accepted fix when a device won’t connect with static IP: confirm the device works on automatic/DHCP, then choose a static IP on the same subnet as the router but outside the DHCP range, set the default gateway to the router’s IP, use a correct subnet mask, and configure working DNS servers so “no internet with static IP” clears on all devices.


Why devices stop working with static IP (gateway, subnet, DNS, IP conflicts)

Most home “device won’t connect with static IP” problems boil down to four values: IP address, subnet mask, default gateway, and DNS servers. If any one of these doesn’t match what your router expects, you can get “No internet” even though the cable or Wi-Fi connection looks fine. Setting a static IP on the wrong subnet or reusing an address from the router’s DHCP pool can also create invisible IP conflicts that make devices drop offline randomly.

Think of the path as device → router (default gateway) → ISP → internet. If the device can’t reach the router IP, the default gateway or subnet mask is wrong. If it can reach the router and ping outside IPs like 8.8.8.8 but websites fail, the static DNS configuration is wrong. If everything works on DHCP but fails as soon as you set a manual address, the static IP is probably outside the correct range or already in use.

How to check if the problem is static IP, router, or device

To quickly narrow down a static IP not working issue, start simple:

First, put the device back on obtain IP automatically (DHCP). If the internet works there, your router and ISP are fine. Note the working IP, mask, gateway, and DNS. Then re-apply a static IP in the same subnet, just outside the DHCP range. If the router has internet but the device doesn’t, test ping <router IP> and ping 8.8.8.8 to see whether the problem is gateway reachability or DNS resolution. If all devices break whenever you change to static addressing on the router itself, the issue is likely with the router’s WAN static IP or ISP configuration rather than the client.

Device won’t connect with static IP — quick troubleshooting tips

Confirm DHCP works first, then fix the static IP, gateway, subnet mask, and DNS.

Fast path: check that the device gets online with automatic/DHCP → write down the working IP, default gateway, and DNS servers → choose a static IP on the same network but outside the router’s DHCP pool → set the correct subnet mask (usually 255.255.255.0 in home networks) → set the gateway to the router’s LAN IP → use the router or a public service as DNS. Keeping a simple IP plan and using DHCP reservations for critical devices helps avoid future “no internet after setting static IP” problems.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your router model, ISP, and devices, please consult a verified expert on Whizz-Tech before making decisions.


Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts for device won’t connect with static IP, no internet after manual IP, IP conflict, and other networking headaches.

Expert will respond in minutes

We match you with a networking specialist who knows DHCP vs static IP, default gateways, DNS configuration, and router setup for all major brands (Netgear, TP-Link, ASUS, Linksys and more).

Save time & money

Stop guessing at static IP settings and breaking your internet. Get a clear step-by-step IP, gateway & DNS fix in chat and get back online quickly.

FAQ

Why does my device lose internet when I set a static IP?

Most of the time a device loses internet with a static IP because one of four values is wrong: IP, subnet mask, default gateway, or DNS servers. If the IP is on a different subnet than the router, or the gateway is not set to the router’s LAN address, the device can’t reach the internet. If DNS is wrong, it can reach IPs but not websites. Matching what DHCP gives you is the fastest way to find the correct values.

How do I fix “No internet” after setting a static IP on Windows?

On Windows, first switch back to DHCP and run ipconfig /all to see the working IP configuration. Then re-enable static IP and use the same subnet, gateway, and DNS, choosing an address outside the router’s DHCP pool. Finally, run ipconfig /flushdns and ipconfig /renew, toggle the adapter off/on, and test pinging the gateway, then an external IP, then a website name.

What should I use for default gateway and DNS with a static IP?

In a typical home network, the default gateway should be your router’s LAN IP (for example 192.168.0.1 or 192.168.1.1). For DNS servers, you can usually use the router’s IP as the primary DNS and a public DNS like 8.8.8.8 or 1.1.1.1 as secondary. Using random or blank values for gateway and DNS is a common reason a device won’t connect with static IP.

Is it better to use static IP or DHCP reservation?

For most home users, a DHCP reservation on the router is easier and safer than configuring a static IP on each device. The router always hands out the same IP to a device based on its MAC address, so it stays consistent for port forwarding and remote access, but you avoid typos in gateway, subnet mask, and DNS that can cause “no internet with static IP” errors.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant