DHCP Is Not Enabled for Ethernet? 7 Fixes That Work

You plug in your Ethernet cable, the internet doesn't work, and Windows Diagnostics throws the cryptic error "DHCP is not enabled for Ethernet." Before you panic or call your ISP, know this: 9 out of 10 times, this is a simple settings issue you can fix in under 5 minutes. The error essentially means your network adapter isn't receiving an automatic IP address assignment from your router, so your computer has no valid way to communicate with the network. In this guide, I'll walk you through seven proven fixes—covering Windows 10/11, macOS, Linux, and router-side issues—so you can get back online without a support ticket.

---

What Does "DHCP Is Not Enabled for Ethernet" Mean?

DHCP (Dynamic Host Configuration Protocol) is the behind-the-scenes system that automatically assigns your device an IP address when it joins a network. When you see the "DHCP is not enabled for Ethernet" error, it means your Ethernet adapter is either configured with a static IP address or the DHCP client isn't running—so your computer can't obtain the network credentials it needs to go online.

How DHCP Works: A Simple Analogy

Think of DHCP as a librarian at a busy library. When you walk in (plug in your Ethernet cable), the librarian assigns you a unique library card (IP address) so you can borrow books (data) from the shelves. Without that card, you're just standing in the doorway—you can see the books, but you can't take any home.

Now imagine someone previously gave you a permanent library card with a number that's already in use. That's what happens when a static IP configuration is left over from an old setup. The librarian can't assign you a new card because your old one is conflicting with the system. The fix? Throw away the old card and let the librarian issue you a fresh one automatically.

Why Does This Error Happen? 4 Common Causes

Through years of troubleshooting network issues, I've found that this error almost always traces back to one of four culprits:

• Cause 1: Manual static IP configuration left over from previous setup. Maybe you set a static IP for port forwarding or a home server project and forgot to switch it back. This is the most common cause I see.
• Cause 2: DHCP Client service is disabled or stopped in Windows. Sometimes Windows updates or third-party "optimizer" tools silently disable this critical service.
• Cause 3: Outdated or corrupted network adapter drivers. A driver that's out of sync with your OS can break the DHCP handshake entirely.
• Cause 4: Router-side DHCP server is disabled or malfunctioning. Less common, but it happens—especially after a power surge or firmware update gone wrong.

---

How to Enable DHCP for Ethernet on Windows 10 and 11

Let's start with the fixes that resolve the majority of cases. I've ordered these from simplest to most involved, so work through them in sequence.

Method 1: Change Network Adapter Properties (GUI)

This is the first thing I try whenever a client calls with this error. It's quick, non-destructive, and fixes the problem about 60% of the time.

1. Open Control Panel and navigate to Network and Sharing Center.
2. Click Change adapter settings on the left sidebar.
3. Right-click your Ethernet adapter and select Properties.
4. In the list, find Internet Protocol Version 4 (TCP/IPv4) and double-click it.
5. Select both Obtain an IP address automatically and Obtain DNS server address automatically.
6. Click OK on both windows, then restart your PC.

That's it. If your adapter was set to a static IP, this switches it back to DHCP mode. In my experience, this resolves the issue instantly for most users.

Method 2: Restart the DHCP Client Service

If Method 1 didn't work, the DHCP Client service itself might be stopped. Here's how to check:

1. Press Win + R, type services.msc, and hit Enter.
2. Scroll down to DHCP Client in the list.
3. Right-click it and select Properties.
4. Set Startup type to Automatic.
5. If the service isn't running, click Start.
6. Click Apply and OK, then restart your PC.

I've seen third-party "system cleaner" tools disable this service thinking it's unnecessary. It's not—Windows relies on it for all automatic network configuration.

Method 3: Reset Network Configurations via Command Prompt

When the GUI methods fail, the command line is your friend. This approach resets your network stack at a deeper level.

1. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
2. Run these commands in order, pressing Enter after each:

ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh int ip reset
netsh winsock reset

1. Restart your computer.

The netsh int ip reset command is particularly powerful—it rewrites the entire TCP/IP stack registry entries. I've used this to fix issues that survived multiple driver reinstalls. Just be aware that it resets all network adapters, so you'll need to reconfigure any VPN connections afterward.

Method 4: Update or Reinstall Network Adapter Drivers

Outdated drivers are a sneaky cause of DHCP failures. Windows Update doesn't always catch the latest versions, especially for Ethernet adapters from smaller manufacturers.

1. Press Win + X and select Device Manager.
2. Expand Network adapters.
3. Right-click your Ethernet adapter (it usually has "Ethernet," "Gigabit," or "Realtek" in the name) and select Update driver.
4. Choose Search automatically for drivers. If Windows finds nothing, try:
5. Right-click the adapter again and select Uninstall device. Check "Delete the driver software for this device" if prompted.
6. Restart your PC—Windows will reinstall the driver automatically.

For advanced users: if the automatic reinstall doesn't work, visit your motherboard or laptop manufacturer's website and download the latest Ethernet driver manually. I've fixed stubborn cases with Intel and Realtek adapters this way.

---

Fixing DHCP Issues on macOS, Linux, and Router Settings

Windows isn't the only OS that hits this wall. Here's how to handle the same error on other platforms.

macOS: Renew DHCP Lease in System Settings

macOS is usually more forgiving with DHCP, but it can still get stuck with a stale lease.

1. Open System Settings and go to Network.
2. Select Ethernet on the left.
3. Click Details next to your connection.
4. Click the TCP/IP tab.
5. Click Renew DHCP Lease.

If that doesn't work, delete the network service entirely: click the minus button under the service list, then re-add Ethernet by clicking the plus button. This forces macOS to rebuild the network configuration from scratch.

Linux (Ubuntu/Debian): Enable DHCP via Command Line

Linux users have the most control—and the most room for error. Here's the clean way to enable DHCP:

1. Open a terminal and edit your netplan config:

sudo nano /etc/netplan/01-netcfg.yaml

1. Make sure your Ethernet interface (usually eth0 or enp3s0) has dhcp4: true:

network:
  version: 2
  ethernets:
    eth0:
      dhcp4: true

1. Apply the changes:

sudo netplan apply

1. If you're in a hurry, you can force a DHCP request immediately:

sudo dhclient eth0

I've seen many Linux users accidentally set dhcp4: false while experimenting with static IPs for Docker or VMs. This fix takes less than a minute once you know where to look.

Router-Side Checks: Is Your Router's DHCP Server On?

If none of the OS-level fixes work, the problem might be upstream. Here's how to check your router:

1. Log into your router's admin page (usually 192.168.1.1 or 192.168.0.1—check the sticker on the router).
2. Find the DHCP settings section (often under "LAN" or "Network").
3. Ensure DHCP Server is enabled. Note the IP address range (e.g., 192.168.1.100 to 192.168.1.200).
4. Save changes and reboot the router.

A quick diagnostic: if other devices on your network also can't get internet via Ethernet, the router is almost certainly the culprit. If only one computer is affected, focus on that computer's settings.

---

DHCP Not Working on Ethernet but Wi-Fi Works? Here's Why

This is one of the most confusing scenarios—your Wi-Fi works fine, but Ethernet refuses to get an IP address. I've debugged this exact issue dozens of times, and it usually comes down to one of two things.

The Adapter Priority Problem

Windows sometimes prioritizes Wi-Fi over Ethernet, even when both are connected. This creates a conflict where the Ethernet adapter never properly negotiates its DHCP lease.

To fix this:

1. Open Control Panel > Network and Sharing Center > Change adapter settings.
2. Click Advanced in the menu bar, then select Advanced Settings.
3. Under Adapters and Bindings, use the arrows to move Ethernet above Wi-Fi.
4. Click OK.

Alternatively, just disable Wi-Fi temporarily. This forces Windows to use Ethernet exclusively, and the DHCP handshake usually completes immediately.

Check for Static IP Conflicts

A leftover static IP on your Ethernet adapter can conflict with your router's DHCP range. Here's how to check:

1. Open Command Prompt and run ipconfig /all.
2. Look at the Ethernet adapter section. If "DHCP Enabled" says "No," you have a static IP.
3. Check if your IP address falls within your router's DHCP range (e.g., 192.168.1.100–200). If it does, you're in conflict territory.

The fix is simple: go back to Method 1 and switch to "Obtain an IP address automatically." If you need a static IP for specific purposes, reserve it in your router's DHCP settings instead—that way, the router knows to always assign you the same address without conflicts.

---

How to Prevent DHCP Errors in the Future

After fixing the issue, you don't want it coming back. Here's what I recommend to my clients to keep DHCP errors at bay.

Best Practices for Network Settings

• Always use "Obtain an IP address automatically" unless you have a specific, documented reason for a static IP. This is the single most effective prevention measure.
• Keep your network adapter drivers updated. Set a reminder to check every few months, or use your manufacturer's update utility.
• Reboot your router monthly. This clears the DHCP lease table and prevents address exhaustion issues.
• Use a UPS for your router. Power surges can corrupt router firmware settings, including DHCP configuration. A $40 UPS is cheap insurance.

When to Use a Static IP vs. DHCP

---

FAQ

How do I enable DHCP on my Ethernet adapter?

For Windows 10/11: go to Control Panel > Network and Sharing Center > Change adapter settings > right-click Ethernet > Properties > double-click Internet Protocol Version 4 (TCP/IPv4) > select "Obtain an IP address automatically" and "Obtain DNS server address automatically." macOS and Linux have similar options—see the detailed sections above for step-by-step instructions.

Why does my Ethernet say DHCP is not enabled?

The two most common causes are: (1) a manually configured static IP is still set on the adapter, and (2) the DHCP Client service is stopped in Windows. A third possibility is that your router's DHCP server is disabled. Check your adapter settings first, then verify the DHCP Client service is running.

Is DHCP not enabled a router or computer problem?

It can be either. Here's a quick diagnostic: check if other devices on the same network get internet via Ethernet. If they do, it's a computer problem—focus on the OS-level fixes. If no device gets internet via Ethernet, it's likely a router problem—check your router's DHCP settings.

How do I reset DHCP on my router for Ethernet?

First, reboot your router by unplugging it for 30 seconds and plugging it back in. If that doesn't work, log into the admin panel (usually 192.168.1.1 or 192.168.0.1), find the DHCP settings under "LAN" or "Network," disable the DHCP server, save changes, then re-enable it and save again. This forces all connected devices to request new IP addresses.

---

Conclusion

The "DHCP is not enabled for Ethernet" error is one of the most common—and most fixable—network issues you'll encounter. In this guide, I've covered seven methods: changing adapter properties, restarting the DHCP Client service, resetting network configurations via command line, updating drivers, fixing macOS and Linux systems, checking router settings, and resolving Wi-Fi/Ethernet priority conflicts.

Start with Method 1 (the GUI settings change) and work your way down. In my experience, that single fix resolves the majority of cases. If you've worked through all seven methods and still see the error, the issue may be hardware-related—try a different Ethernet cable or port before calling in professional help.

Did one of these methods fix your issue? Let us know in the comments below. If you're still stuck, drop your Windows version and the exact error message, and we'll help you troubleshoot further.