A Realtek LAN adapter that won’t get a DHCP address usually means Windows can see the Ethernet hardware, but the DHCP exchange is failing somewhere between the PC and the network. Start by checking link lights, the adapter’s IP settings, and whether Windows is getting a 169.254.x.x address. Then move outward to the cable, switch port, router DHCP, and only after that the driver.
What this symptom usually means
One of three things is usually happening: the adapter has no link at all, it has link but never gets a DHCP lease, or it got a bad or stale lease and can’t use it. Windows may still show the Ethernet adapter as connected even when DHCP never completed.
A 169.254.x.x address means Windows fell back to APIPA after DHCP failed. That tells you the adapter didn’t get a usable lease, but it does not tell you yet whether the problem is the PC, the cable or port, or the router’s DHCP service.
A stale manual IP can also make the symptom look worse than it is. If the adapter was set to a fixed address, or if a bridge, VPN filter, or VLAN setting changed the path, DHCP can be bypassed or blocked even though the link light is on.
Before you start
- Have a known-good Ethernet cable handy.
- Be ready to test at least one other switch or router port.
- If this is a work network, keep in mind that VLAN rules, reservations, and MAC filters may be managed centrally.
- If you recently changed adapter settings, docking-station software, VPN software, or security software, note that before you change anything else.
Don’t start with a driver reinstall. First check whether Windows is configured to obtain an address automatically. That is faster to confirm and easier to undo than driver changes.
First decide if the fault is on the PC or the network
- Check the Ethernet link light on the PC, dock, switch, or router.
If there is no link light at all, treat it as a physical-layer problem first: cable, port, dock, or NIC. DHCP never gets a chance if the link never comes up.
- Swap in a known-good cable and move the cable to a different port.
If the link light comes on after that, the original cable or port is suspect. If another device also fails on the same port, the port or its configuration is more likely than the PC.
- Test the same PC on a different known-good port, or test the same cable and port with a different device.
If the same PC fails everywhere but other devices work, the fault follows the PC. If every device fails on one port, look at the router or switch configuration before blaming Windows.
| What you see | What it usually means | Next check |
|---|---|---|
| No link light | Cable, port, dock, or NIC issue | Swap cable or port |
| Link light on, 169.254.x.x address | DHCP failed | Check Windows settings and DHCP reachability |
ipconfig /renew fails immediately | Local adapter, filter, or service problem | Check adapter settings, VPN, security software, DHCP client |
| Other devices work, this one does not | Device-specific problem | Compare IP settings, MAC rules, VLANs, reservations |
If the same adapter fails on every known-good port and cable, the PC side is still the main suspect. If the problem follows one port, the network hardware or port config needs attention first.
What to check in Windows before touching the driver
Open the Ethernet adapter properties and confirm that IPv4 is set to obtain an IP address automatically and obtain DNS server address automatically. If either one is set manually, DHCP may never complete.
Then check ipconfig /all. Look for the correct Ethernet adapter, DHCP enabled, and a valid IPv4 address, subnet mask, default gateway, and DHCP server. If you see 169.254.x.x, or the gateway and DHCP server fields are missing, that fits a failed DHCP lease.
If you want a quicker sanity check, open Services and make sure the DHCP Client service is set to automatic and is running. If it is stopped, start it and retry the connection. That does not fix every DHCP problem, but it is a simple place to rule out a local service failure.
Also look for anything layered on top of the adapter: VPN clients, endpoint security software, network bridges, teaming tools, and docking-station utilities. These can install filters that interfere with DHCP. If you created a bridge for testing and forgot about it, remove that before changing drivers.
Check for VLAN settings too. Dell documents a case where the Realtek USB GBE Ethernet Controller Driver can fail to get a valid IP address when a VLAN tag is set on the adapter, and the client may receive a 169.x.x.x address. That is specific to the affected Dell hardware and driver path, but it is a good example of why a single adapter can fail while other devices on the same network keep working.
The fixes that usually matter most, in order
- Renew the lease first.
ipconfig /release
ipconfig /renewIf this works, the adapter should come back with a normal LAN address, gateway, and DNS server. If release or renew fails right away, the problem is probably not just a stale lease.
- Reset the Windows network stack if renew does not help.
netsh winsock reset
netsh int ip resetReboot after those commands, then check ipconfig /all again and try ipconfig /renew once more. This is the right next step when the adapter looks fine physically but Windows networking is stuck.
- Check whether the DHCP Client service is running.
If the service is stopped or disabled, set it back to automatic and start it. Then retry the connection. If it already is running, move on rather than looping on the same check.
- Reinstall, roll back, or update the Realtek driver based on timing.
If the problem started right after a driver update or Windows update, try Roll Back Driver first in Device Manager. That is the cleanest way to reverse a change that clearly lines up with the failure.
If rollback is not available, uninstall the device and restart so Windows can rediscover it, or install the current vendor driver from the PC, motherboard, or dock maker’s support page. Dell says updating to Realtek USB GBE Ethernet Controller Driver version A30 11.13.0420.2023 or later resolves the VLAN-related IP issue on the affected hardware. In 2026, check the current official support page for your exact model before using that package.
If the adapter works with the generic Windows driver but fails with the vendor driver, keep the working version for now and avoid more churn. If the adapter fails before Windows even finishes loading the driver stack, the driver is less likely to be the only problem.
When the evidence points to the router or hardware
If one device fails while others on the same network work, check the router or switch next. A DHCP pool that is exhausted can block one more device even though the network still looks alive. Reservations, MAC filters, and VLAN rules can also block only one client if that device is treated differently from the others.
A static IP conflict can create a mess that looks like a DHCP problem. If the adapter used to have a manual address that matches a current lease, the network may reject it or behave inconsistently until the duplicate is cleared. Stale leases can also linger after a router reboot or outage, so check the DHCP lease table if your router exposes it.
If the adapter works on one port and not another, look at the switch or router port configuration. A bad port can fail physically, but a misconfigured access port or VLAN can still show link while blocking DHCP. If every known-good port and cable has been ruled out, and Windows settings plus the driver have been checked, a hardware fault in the NIC, dock, cable, or switch port becomes more likely.
The cleanest comparison is simple: put a known-good device on the same port and VLAN. If that device gets a lease and the Realtek adapter does not, focus on MAC-based rules, reservations, VLAN membership, and pool exhaustion in the current router or switch settings. If the router or switch interface has changed since you last used it, verify those settings against the current official documentation for that model.
Verify the fix
After the change, run ipconfig /all again and confirm that the Ethernet adapter has a normal IPv4 address, a default gateway, and a DHCP server listed. Then browse a site or ping your router to make sure traffic is actually flowing.
If the adapter still shows 169.254.x.x, or ipconfig /renew still fails, go back one layer at a time: link, Windows settings, DHCP Client service, driver, then router or switch rules. Don’t stack more changes until you know which layer is failing.
Conclusion
If you’ve ruled out the cable, port, Windows settings, and DHCP Client service, then move to the driver and the router’s DHCP rules in that order. That keeps you from reinstalling software when the real fault is a dead port, a VLAN rule, or a lease conflict.
Frequently Asked Questions
Should I use a static IP to get back online faster?
Only as a short test. A static IP can prove that the cable and port path works, but it can also hide the real DHCP problem or create a duplicate address if you pick one that is already in use.
If `ipconfig /renew` fails, does that mean the Realtek driver is bad?
Not by itself. A failed renew can come from a bad driver, but it can also come from a blocked port, a VPN or security filter, a stopped DHCP Client service, a router DHCP limit, or a VLAN rule that only affects this adapter.
Why does my adapter show 169.254.x.x?
That usually means Windows did not get a DHCP lease and fell back to APIPA, which is a temporary self-assigned address. It strongly points to a DHCP failure, but it doesn’t tell you yet whether the cause is the PC, the cable, or the router.