Advertisement

Intel Ethernet controller does not receive a DHCP address

If your Intel Ethernet controller links up but never gets a DHCP address, the fix starts with separating the failure into Windows, the adapter, or the network. Check for APIPA, stale static settings, and link issues before you reinstall anything.

Windows 10 min read
desktop PC Ethernet cable

If an Intel Ethernet controller links up but never gets a DHCP address, the fault is usually in one of three places: Windows, the Intel driver or adapter state, or the router/switch/DHCP side. Start by separating those layers instead of reinstalling the driver right away. A static IP that works but DHCP does not usually means the cable path is fine, and the DHCP exchange is the part breaking.

Symptom

The adapter shows link, but Windows never receives a normal IPv4 address. That can look like no address at all, an empty lease, or a self-assigned 169.254.x.x address when Windows gives up waiting for DHCP.

That is different from no-link, where the adapter never negotiates carrier in the first place. It is also different from a stale static IP. In that case, the adapter has an address typed in manually and may reach some local devices even though DHCP is not working. If the link light is on and the port shows connected, but the address never arrives from the server, you are looking at a true DHCP failure rather than a dead cable by default.

Before you start

Use a known-good Ethernet cable and, if possible, a different switch or router port. If the machine is on a managed network, keep the current VLAN and port assignment in mind. A device can link and still be blocked from the DHCP scope it needs.

Have local admin access on Windows so you can change adapter settings, check the driver version, and reinstall or roll back the Intel driver if needed. If the adapter is carrying a static IP that somebody depends on, write that address, subnet mask, gateway, and DNS values down before you change anything.

If the PC is a server or part of a business network, stop before making broad resets that would affect other services. The goal is to prove where the fault lives first, then change only that layer.

Quick checks that isolate the fault

  1. Check whether the problem follows the cable or stays with the PC.

Move the cable to a different device, or move the Intel PC to a port that already works for another device. If the other device gets a lease on that cable and port, the router, switch, and DHCP server are less likely to be the cause. If neither device gets an address on that port, the switch port, VLAN, or DHCP path is the stronger suspect.

  1. Check whether the adapter has link but no lease.

Open an elevated Command Prompt or PowerShell window and compare the adapter state with its address.

Command Prompt
ipconfig /all

If you see 169.254.x.x, Windows did not get a DHCP lease. If you see a normal static address entered by hand, DHCP is not involved yet. If the adapter shows link but no useful IPv4 address, that points to the DHCP exchange rather than the physical link.

  1. Try a static IP on the same network.

If you know a free address on that subnet, set a temporary static IP, gateway, and DNS on the wired adapter. If the PC reaches local resources or the internet with the static address, the cable, port, and basic link negotiation are probably fine. That leaves DHCP server reachability, reservations, scope exhaustion, or a Windows-side DHCP block as the main suspects.

If static IP also fails, stop assuming it is a DHCP problem. At that point the path, switch port, VLAN, or adapter link settings are more likely than the lease process itself.

Windows settings that can block DHCP

  1. Check that the wired adapter is still using automatic addressing.

Open the Ethernet adapter’s IPv4 properties and make sure it is set to obtain an IP address and DNS server automatically. A manual static configuration can make the adapter look healthy while preventing DHCP from ever running.

Settings path
Settings > Network & internet > Ethernet > IP assignment

If your Windows build shows the old control-panel path instead, use the adapter’s properties there. The exact path varies by version, but the setting you want is still the automatic IPv4 option.

  1. Confirm the adapter is enabled and not bound to the wrong profile.

A disabled adapter, a paused network interface, or a stale VPN or security filter can keep DHCP from completing even when the link light is on. Disconnect any VPN, third-party endpoint filter, or network isolation tool before you keep chasing the hardware.

  1. Reset only the local DHCP state before you touch drivers.

Renew the lease first if the adapter is already up and Windows can talk to the network stack.

Command Prompt
ipconfig /release
ipconfig /renew

If release and renew succeed, Windows should get a normal address and default gateway. If the renew fails while the same cable and port work for another device, that shifts the suspicion toward Windows configuration, the Intel driver, or a local filter.

  1. Check the adapter in Device Manager.

Intel’s own support material shows Device Manager as the place to view the Ethernet adapter and confirm the driver version on Windows. Right-click the Intel Ethernet adapter, open Properties, and note the driver version before you change anything. That gives you a baseline if you need to roll back later.

Intel driver or adapter features that can interfere

  1. Roll back the Intel driver if the failure started right after an update.

If the adapter worked before and stopped right after a driver change, a rollback is the cleanest test. Intel support discussions also show that driver behavior can matter when the adapter stops getting DHCP addresses, even when the network itself looks normal.

Use the driver tab in Device Manager to roll back only one version at a time. If rollback restores DHCP, keep that version for now and check the current Intel package or OEM package against the adapter model before trying another update.

  1. Reinstall the driver when the install looks corrupted.

If rollback is unavailable, or the adapter has been swapped, remove the device from Device Manager and let Windows reinstall it after a reboot. That is safer than changing registry values or network services first.

  1. Watch for adapter features that are useful on paper but troublesome on a bad network path.

Energy-saving or offload features can hide problems, but they can also make a borderline link harder to diagnose. If the adapter gets a static address but DHCP still fails, temporarily disable nonessential advanced features in the Intel adapter properties one by one, then retest. If the exact setting names differ by driver package, use the current Intel or OEM driver notes for that adapter model.

If you change several features at once, you will not know which one mattered. Change one thing, retest, and keep the change only if it clearly fixes the lease problem.

When the router, switch, or DHCP server is the real cause

If more than one device stops getting leases at the same time, the network gear is the first place to look. A DHCP pool that is full, a bad reservation, a VLAN mismatch, a failed switch port, or a relay problem can all produce the same symptom from the Windows side.

A static IP working while DHCP fails is a strong clue that the physical path can carry traffic, but the DHCP handshake is not completing. That often means the request is not reaching the server, or the reply is not getting back. If another device works on that cable and port, the PC is less likely to be at fault and the switch, router, or DHCP service moves to the top of the list.

One useful check is to move the Intel PC to a port that already serves a known-good device. If DHCP starts working there, the original port or its VLAN assignment is suspect. If it still fails everywhere, the problem is more likely on the PC or with the DHCP settings that affect that client.

If you are on a managed network and the server address is not obvious, ask whoever runs the DHCP service to verify that the scope is active, the reservation for that MAC address is correct, and the client’s VLAN is allowed to reach DHCP. In the field, I have seen a switch fail in a way that looked like a driver issue until the port was replaced.

Reinstall, roll back, or stop

  1. Roll back first when the failure started after a driver update.

That is the safest way to test for a regression without changing the rest of the system.

  1. Reinstall when the adapter has no clean driver history, or the driver files look corrupted.

Use Device Manager, remove the adapter if needed, then reboot so Windows can load a fresh copy. If the adapter comes back with the same symptom on multiple networks, the driver is not the only thing to blame.

  1. Stop and hand the problem to the network side when a static IP works everywhere but DHCP fails everywhere.

At that point, the cable, port, and base link are probably fine. The remaining fault is usually DHCP scope, relay, reservation, VLAN, or a switch path that is blocking the exchange.

Verify

After the fix, the adapter should show a normal IPv4 address from your network, not 169.254.x.x, and ipconfig /all should list a valid lease, gateway, and DNS server.

Command Prompt
ipconfig /all

If the address appears only after a reboot or after reconnecting the cable, that still counts as a good result, but keep an eye on whether it renews normally later. If the same fault comes back on every network, recheck the Intel driver version and the adapter properties in Device Manager.

Prevent

Keep a note of the driver version that works and the exact switch or router port that was last known good. If DHCP breaks again after a driver update or a port move, that record makes it much faster to tell a PC problem from a network problem.

On managed networks, keep the static mapping or reservation in sync with the adapter MAC address. If the MAC changes because the adapter is replaced or a BIOS setting changes, the reservation can quietly stop matching the device.

Conclusion

If you still cannot get a lease after the cable, port, Windows settings, and Intel driver have all been checked, treat the issue as a network-side fault and move to the router, switch, or DHCP server owner with your test results.

Frequently Asked Questions

Should I renew the lease before reinstalling the Intel driver?

Yes. Renewing is the safer first test because it does not change drivers or rewrite the whole network stack. It also shows whether the failure is just a stuck DHCP exchange before you make bigger changes.

What does a 169.254.x.x address mean on a wired Intel adapter?

It means Windows did not get a DHCP lease and fell back to an APIPA address. That points you toward DHCP discovery, server reachability, or a local Windows or driver problem rather than a dead Ethernet link.

When should I roll back the Intel network driver?

Roll it back when the problem started right after a driver update, or when the adapter worked before and now fails on every network. That is the cleanest driver test because it changes one thing and leaves the rest of the system alone.

Sources