How do I fix “No DHCP Server Was Found”?

General
1

My device suddenly stopped getting an IP address and now shows the error “No DHCP Server Was Found.” I’ve restarted the modem, router, and computer, but it still won’t connect to the internet. I need help figuring out whether this is a router DHCP issue, network settings problem, or something wrong with my ISP connection.

2

This means your device asked for an IP address and got no reply.

Work through it in this order.

  1. Check link lights.
    If the PC port on the router is dark or blinking weird, swap the Ethernet cable. Try a different router port too. Bad cable is common.

  2. Test DHCP on another device.
    Plug in a laptop or phone over Wi-Fi. If nothing gets an IP, the router DHCP service is the likely fail point.

  3. Set your adapter back to automatic.
    On Windows, open Network Adapter settings, IPv4, then make sure both IP address and DNS are set to obtain automatically. If you see an old static IP, remove it.

  4. Renew from Command Prompt.
    Run:
    ipconfig /release
    ipconfig /renew
    ipconfig /all

If you get a 169.254.x.x address, DHCP still failed.

  1. Restart the network stack.
    Run:
    netsh int ip reset
    netsh winsock reset
    Then reboot. Old TCP/IP config gets borked sometimes.

  2. Log into the router.
    Look for DHCP Server, LAN Setup, or Address Pool. Make sure DHCP is enabled. Most home routers hand out something like 192.168.1.100 to 192.168.1.200.

  3. Check if the pool is full.
    If the range is tiny, new devices get nothing. Expand it.

  4. Update or reset the router.
    If DHCP died after a power flicker or firmware bug, rebooting wont always fix it. Firmware update helps. Factory reset is the last step.

  5. Temporary test.
    Set a manual IP on your PC, like 192.168.1.50, subnet 255.255.255.0, gateway 192.168.1.1, DNS 8.8.8.8. If local network starts working, DHCP is almost for sure the issue.

If your modem is also a router, and your own router is behind it, check both boxes. I’ve seen people reboot the wrong one for 20 minuts and get nowhere.

3

One thing I’d add to what @voyageurdubois said: don’t assume it’s actually a DHCP problem just because Windows says so. That message can also show up if the network adapter itself is half-dead or the driver got corrupted.

A few diffrent checks:

  • Open Device Manager and look at the NIC. If it has a warning icon, reinstall or update the driver.
  • Disable/enable the adapter manually. Sounds dumb, fixes stuff anyway.
  • Boot into Safe Mode with Networking. If DHCP works there, some VPN, firewall, or security suite is probably hijacking the stack.
  • Check MAC filtering or access control in the router. I’ve seen routers silently refuse new leases because the device wasn’t allowed.
  • If this is Wi-Fi, forget the network and reconnect. Bad saved profile = weird behavior.
  • Try a Linux live USB if you can. If Linux also gets no IP, that points away from Windows and toward hardware/router.

I kinda disagree with jumping straight to factory reset on the router. That’s useful, sure, but it’s annoying and often not the first thing I’d nuke unless you’ve ruled out the adapter/driver side.

Also, if your PC says “media disconnected” in ipconfig /all, stop chasing DHCP for a sec. That means layer 1/2 problem first, not lease handing.

4

I’d check one thing people skip: whether DHCP is actually enabled on the router LAN side. @voyageurdubois covered the client side well, but if the router’s DHCP service got turned off after a firmware update, reset glitch, or ISP box/router double-NAT change, every device will throw the same error.

Quick isolation test:

  • Give your PC a manual IP temporarily.
  • Example: if router is 192.168.1.1, set PC to 192.168.1.50, subnet 255.255.255.0, gateway 192.168.1.1, DNS 1.1.1.1 and 8.8.8.8
  • If you can now open the router admin page, DHCP itself is likely the broken part
  • If manual IP still cannot reach router, think cabling, switch port, Wi-Fi auth, or router LAN failure

Also check for this weird one: two DHCP servers fighting each other. Happens if modem/router combo and your own router are both handing out leases, or neither is because one got put into bridge/AP mode.

A couple of useful commands:

  • ipconfig /release
  • ipconfig /renew
  • arp -a
  • ping 192.168.1.1

If arp -a never learns the router MAC, that points lower than DHCP.

Pros for ': can improve readability if you’re organizing your troubleshooting notes or guide.
Cons for ': not really relevant unless you’re documenting the fix, so I wouldn’t force it here.