Network troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Home networking, router DHCP & static IP setup, Windows/macOS network issues, DNS & gateway configuration, ISP and LAN design

Fix “device won’t connect without DHCP” — static IP not working, DHCP server issues, gateway & DNS errors

Technician avatar Technician
Hi! We’ll get this device won’t connect without DHCP problem sorted and your network stable again.

First I need a quick picture of the setup:
• What kind of device is having the issue (Windows PC, Mac, printer, NAS, camera, console)?
• Does it work fine when the network adapter is set to “Obtain an IP address automatically (DHCP)”, but stop working as soon as you set a static IP?
• Have you changed any DHCP server settings on the router (turned DHCP off, added another router, or put something in bridge/AP mode)?
• When it fails without DHCP, what exactly do you see — no internet, unable to access the router, or can’t see other devices on the LAN?

With those details we can tell whether this is a static IP configuration error, a router DHCP issue, or an IP conflict on your network.
Customer
Windows 11 desktop on Ethernet. If I leave it on “Automatic (DHCP)” everything works instantly. But I wanted a fixed IP for port forwarding, so I set a static IP, subnet mask, gateway, and DNS. As soon as I switch to Manual, the PC shows “No internet” and I can’t even ping the router. If I flip it back to DHCP, it connects again. Same thing happened when I turned off DHCP on the router to “force” static IPs — most devices just stopped connecting.
Technician avatar Technician
That’s a very common situation: the device only connects when DHCP is enabled because DHCP hands out a correct IP address, subnet mask, default gateway, and DNS servers. When you switch to static IP, one of those values is wrong or missing, so the PC can’t talk to the router or internet.

Typical causes when a device won’t connect without DHCP:
• Static IP is in the wrong subnet (for example, router is 192.168.1.1 but device is set to 192.168.0.50).
• Default gateway not set to the router’s address.
• DNS servers left blank or mis-typed, causing “connected, no internet”.
• IP conflict with another device that’s still using DHCP in the same range.
• Router DHCP turned off while no other DHCP server exists on the network.

We’ll grab the working values that DHCP gives you now, then convert them into a correct static IP so the PC works both with and without DHCP.
Customer
When it’s on DHCP, ipconfig shows 192.168.1.23, subnet 255.255.255.0, gateway 192.168.1.1, DNS 192.168.1.1 and a secondary 1.1.1.1. For static I tried 192.168.1.50 with the same subnet and gateway, set DNS to 8.8.8.8 and 1.1.1.1. After that, Windows says “No internet” and I can’t open the router page. So I don’t think the subnet is wrong, but it only works on Automatic (DHCP).
Technician avatar Technician
Those values look mostly sane, so now we focus on details and conflicts.

Step A — Copy DHCP settings correctly, then test connectivity
1) Put the PC back on Automatic (DHCP) and confirm internet works.
2) In the router’s LAN or DHCP settings, note the DHCP range, e.g. 192.168.1.100–192.168.1.200.
3) For a static IP, choose an address outside that pool (for example 192.168.1.50 is fine if the pool starts at .100).
4) On the PC, set:
  • IP address: 192.168.1.50 (or another free address outside the pool)
  • Subnet mask: 255.255.255.0
  • Default gateway: 192.168.1.1 (router)
  • DNS servers: either 192.168.1.1 (router) or reliable public DNS like 1.1.1.1 / 8.8.8.8
5) Save, then run ipconfig /all and ping 192.168.1.1.

If you still can’t ping the gateway on static IP but DHCP works, it’s often because another device already uses that address or there’s a duplicate static IP somewhere. We can also let the router handle this with a DHCP reservation, which keeps DHCP enabled but gives your PC a fixed address.
Customer
I double-checked. The router’s DHCP pool is 192.168.1.10–192.168.1.200, so .50 is inside the pool, not outside. When I changed my static IP to 192.168.1.220, it started working again. But I’d rather not break other devices if I mess this up. Is there a safer way than manually assigning static IPs on every device?
Technician avatar Technician
Exactly — that explains why the device wouldn’t connect without DHCP. You picked an address that the DHCP server is also allowed to hand out, so you risk IP conflicts when some other device grabs 192.168.1.50 via DHCP.

The safer option is to keep DHCP enabled and let the router assign a “static” IP using a DHCP reservation (sometimes called “address reservation” or “static lease”).

Step B — Give the device a fixed IP while still using DHCP
• Leave your PC’s adapter on “Automatic (DHCP)” so it continues to request an address from the router.
• In the router’s DHCP/reservation settings, add the PC’s MAC address and choose an IP inside the DHCP pool or in a reserved area the router suggests.
• Save and reboot the PC or run ipconfig /release then ipconfig /renew so it gets the reserved IP.

From now on, the PC will always get the same IP, but your network still fully relies on the DHCP server, which avoids most “device only works on DHCP, fails on static IP” issues for regular home setups.
Customer
That sounds easier. I also tried turning DHCP off on the main router and letting my second router hand out addresses, but then half the Wi-Fi devices stopped connecting. Is it bad to have more than one DHCP server? I was trying to make the second router the main one for a different subnet.
Technician avatar Technician
Great question — this is where many DHCP vs static IP problems start.

On a simple home LAN you usually want:
• Exactly one DHCP server on each network segment (usually the main router).
• Any extra routers used as access points put into AP/bridge mode with their DHCP servers disabled.

If multiple routers are handing out IP addresses on the same subnet, every device can randomly get a different gateway or DNS server, which leads to symptoms like “some devices can’t get internet” or “device only connects when I flip back to DHCP on a specific router”.

If you really need a separate subnet or VLAN, that’s a different design. But for a typical home network, the fix is: keep DHCP on the main router, turn it off on secondary Wi-Fi devices, and avoid mixing multiple DHCP servers unless you know exactly what you’re doing.
Customer
Understood. I think I had both routers running DHCP at one point. One last question: I’ve got a network printer and a NAS that I do want to keep on fixed IPs. They also seem to behave weirdly if I switch them from DHCP to static — sometimes they disappear from the network. Should I use DHCP reservations there too instead of manual static IP?
Technician avatar Technician
Yes, for most home and small office networks, DHCP reservations are the sweet spot:

• The printer, NAS, cameras, and TVs stay on “Obtain an IP address automatically (DHCP)”, so they always get correct gateway and DNS from the router.
• In the router’s DHCP reservation page, you lock each device’s MAC address to a specific IP address that’s outside the general auto-assignment range or clearly marked as reserved.
• Your PCs, phones, and apps can still use those fixed IPs or hostnames for scanning, port forwarding, and mapping drives — but the devices themselves don’t break when you change networks or DNS settings.

This approach avoids the “device won’t connect without DHCP” trap while still giving you stable addresses for things that need them. Manual static IPs are still okay for advanced setups, but you need to be very careful with subnet, gateway, DNS, and conflicts.
Customer
Got it. I’ll switch the printer and NAS back to DHCP and create reservations in the router instead. For my desktop I’ll probably do the same and just use the reserved IP for port forwarding. Anything else I should change so this “only works with DHCP” situation doesn’t come back?
Technician avatar Technician
A few simple habits will keep your DHCP and static IP setup clean and prevent devices from dropping offline:

Step C — Make your DHCP-based network reliable
• Leave DHCP enabled on the main router and disabled on any additional access points or mesh nodes in bridge/AP mode.
• Take a screenshot or write down your router’s LAN IP, DHCP range, and reservations so you can quickly recreate them after a reset.
• If you must configure a manual static IP on a particular device, keep it outside the DHCP pool, set the gateway to the router’s IP, and use valid DNS servers.
• Avoid mixing multiple subnets on the same physical network unless you know how routing and VLANs are set up — that’s where many “device won’t connect without DHCP” mysteries start.
• Update router firmware so bugs in the DHCP server component are fixed and lease handling stays stable.

With that in place, you should be able to use both dynamic and static IP addressing without random connection failures.
Customer
That all makes sense. I’ve put the second router into AP mode, turned off its DHCP, and set up reservations for the desktop, printer, and NAS on the main router. Everything works on DHCP now, and I still have consistent IPs. Thanks for walking me through it.
Technician avatar Technician
You’re welcome — great job cleaning up the network.

Summary: When a device won’t connect without DHCP, the problem is almost always misconfigured static IP settings, a bad gateway or DNS, an IP conflict, or multiple/disabled DHCP servers. The easiest long-term fix is to keep DHCP on the main router, use DHCP reservations for devices that need fixed addresses, and only use manual static IPs when you’re sure about the subnet and gateway.

If you ever get stuck again — devices only working on “Automatic (DHCP)”, strange IP addresses, or intermittent access — you can open a chat with an expert and we’ll trace the IP configuration with you step by step.
Customer
Perfect, I understand the difference between DHCP and static IP a lot better now. Everything’s online and stable. Thanks again for the detailed help!
Technician avatar Technician
Any time! If a friend or coworker complains that their device only works with DHCP, static IP breaks internet, or their router’s DHCP settings are a mess, you can share this checklist — and if you’d like someone to click through the router and PC 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 without DHCP: put the device back on Automatic (DHCP) and note the working IP, subnet, gateway, and DNS. Keep a single DHCP server enabled on the main router. For devices that need a fixed address, create DHCP reservations instead of random static IPs, or choose a static IP outside the DHCP pool with the correct gateway and DNS so the device stays online even without DHCP changes.

Why devices stop connecting when DHCP is off (static IP, subnet, gateway, DNS)

Most device won’t connect without DHCP problems come down to how IP addresses are assigned on your network. A DHCP server automatically hands out an IP address, subnet mask, default gateway, and DNS servers that all live in the same subnet. When you turn DHCP off or switch a device to static IP without copying those values correctly, the device can’t reach the router or the internet even if the cable or Wi-Fi signal is fine.

Common mistakes include using a static IP in the wrong subnet, forgetting to set the default gateway, leaving DNS blank, or picking a static address that conflicts with the router’s DHCP address pool. In more complex homes with multiple routers or extenders, having more than one DHCP server on the same network can randomly break connectivity for some devices while others still work, which makes it feel like DHCP is “required” for certain clients.

How to check if DHCP or static IP is causing “no internet”

To quickly narrow down a DHCP vs static IP issue, start with a device that works. On a Windows PC or phone that connects fine, check the network details and write down the IP address, subnet mask, default gateway, and DNS servers that DHCP assigned. Then compare those values with any device that loses internet when you switch off DHCP or set a static IP.

If a device works instantly on “Automatic (DHCP)” but fails on Manual, the static settings don’t match what the DHCP server hands out, or there’s an address conflict. If multiple devices go offline only when you disable DHCP on the main router, you probably don’t have another functioning DHCP server, so those clients never get an IP at all. In both cases, the fix is to either restore DHCP and use DHCP reservations for consistency or very carefully configure static IPs with the correct subnet, gateway, and DNS.

Device won’t connect without DHCP — quick troubleshooting tips

Confirm the DHCP server and IP configuration before changing everything to static.

Fast path: put the device back on Automatic (DHCP) and confirm it works → check the router’s DHCP range, gateway, and DNS → make sure you have only one active DHCP server on the LAN → if you need fixed addresses, use DHCP reservations for PCs, printers, and NAS boxes → only use manual static IP addresses outside the DHCP pool with correct gateway and DNS. This turns a vague “device won’t connect without DHCP” error into a simple addressing and configuration checklist.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your router, operating system, and network layout, 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 without DHCP, static IP not working, DHCP server issues, and more.

Expert will respond in minutes

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

Save time & money

Stop guessing at IP settings and breaking your network. Get a clear step-by-step DHCP and static IP fix in chat and get every device back online quickly.

FAQ

Why does my device only work when DHCP is enabled?

If a device only works with DHCP, the DHCP server is giving it a correct IP address, subnet mask, gateway, and DNS. When you switch to a static IP or turn DHCP off, one of those values is wrong or missing, or there is an IP conflict, so the device can’t reach the router or internet.

Can I use static IP and still rely on DHCP?

Yes. Instead of configuring static IPs on every device, most routers let you create DHCP reservations. The device remains on “Obtain an IP address automatically”, but the DHCP server always gives it the same IP, along with correct gateway and DNS settings.

Is it OK to run more than one DHCP server at home?

Generally no. Running multiple DHCP servers on the same home network can cause devices to receive different gateways and DNS servers, or overlapping IPs, which leads to random connectivity issues. In most setups, you want one DHCP server on the main router and DHCP disabled on additional access points.

How do I safely assign a manual static IP?

Choose an IP outside the DHCP pool but in the same subnet as your router, set the default gateway to the router’s address, and configure valid DNS servers (router IP or reliable public DNS). Always check that no other device already uses that static IP.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.