A USB-C Ethernet adapter that shows link but still won’t get a DHCP address usually has one of three causes: the adapter is fine but DHCP is failing, the device is stuck on a static IP, or the network is blocking the adapter with policy such as MAC filtering or 802.1X. The quickest fix is to separate those layers first. Then test the adapter on another port, cable, and network before you replace hardware. If the adapter gets a normal lease on another network, the problem is on the router, switch, DHCP server, or network policy side—not the dongle.
Symptom
What you usually see is a live Ethernet link light or a connected status, but no usable IPv4 address. On Windows, that often shows up as a self-assigned 169.254.x.x address. That means the system did not get a valid DHCP reply.
On macOS, the network panel may show a self-assigned address warning. In some cases, the adapter does not appear cleanly in System Information under USB, which means macOS is not seeing the hardware properly. On Linux, the interface may exist and still sit there without a lease.
The useful clue is where the failure happens. If the physical link never comes up, you are dealing with cable, port, adapter, or power. If the link is up but the IP never arrives, the problem is usually DHCP, static configuration, or a network rule blocking the request. If the adapter works on one network but not another, the hardware is probably good enough to pass traffic and the blocker is on the network side.
Before you start
Use a known-good Ethernet cable if you have one. If the adapter is connected through a dock, a flaky dock or port can be the real problem. Make the checks in this order: physical link, local configuration, then network policy.
A few things can block DHCP before you start changing anything else:
- A static IP set on the adapter instead of automatic addressing.
- MAC filtering or registration on the switch or router.
- 802.1X authentication on managed networks.
- A VLAN mismatch that keeps DHCP traffic on the wrong segment.
If you are on a corporate network, stop guessing once you know the adapter works elsewhere but not there. In managed environments, a working link does not guarantee access because the network may still refuse the USB Ethernet interface until it is authorized.
What to try on your own device first
- Unplug the adapter, then plug it back in and reseat the Ethernet cable.
- Try a different USB-C port on the device. If the adapter only fails through one port or dock, the problem is probably with that path, not the adapter itself.
- Test with another Ethernet cable.
- Check whether the adapter is set to a static IP. If it is, switch it back to automatic DHCP before you do anything else.
- Renew the lease after changing the setting.
On Windows, open the Ethernet adapter properties and make sure IPv4 is set to obtain an address automatically. Then renew the lease.
ipconfig /release
ipconfig /renewIf Windows shows a 169.254.x.x address before or after that renewal, the machine still is not getting a valid DHCP reply. That does not prove the adapter is bad. It only proves DHCP did not complete.
On macOS, check the Ethernet service in Network settings and make sure it is not set to manual addressing. If the adapter is missing from System Information under USB, macOS may not be seeing the device cleanly. If it appears there but still will not get a lease, the issue is usually configuration or network-side blocking rather than a missing driver, since these devices normally should not need a separate driver.
On Linux, confirm the interface exists, then release and renew the lease with your DHCP client. If you use NetworkManager, make sure the connection is set to automatic rather than manual.
sudo dhclient -r
sudo dhclientIf the lease comes back after one of these changes, the problem was local. If nothing changes, keep going. At that point, the network may be refusing the request or the adapter may not be presenting cleanly to the OS.
How to tell link failure from DHCP failure from network-policy blocking
The easiest way to separate the problem is to think in layers.
- Link failure: no negotiated Ethernet link, so the light stays off or the connection never shows as active.
- DHCP failure: the link is up, but the adapter never gets a valid address, gateway, or DNS server.
- Network-policy blocking: the link is up and the hardware is seen, but the network refuses to authorize the adapter or hand out a lease.
A 169.254.x.x address points to DHCP failure, not a dead cable by itself. If the same adapter works on one network and not on another, that is the strongest sign that the network policy or DHCP setup is the blocker. If the built-in Ethernet port works on the same machine but the USB-C adapter does not, that also points away from the dongle and toward a policy or authorization issue.
For a managed network, the most common blockers are a switch or router that only allows approved MAC addresses, or 802.1X authentication that has not completed. If you are not the network owner, do not keep toggling settings you cannot verify. Collect the evidence and hand it off.
When the network is the real problem
Test the same laptop and adapter on a second network before you decide the adapter is bad. A home router, a simple guest network, or a phone hotspot setup with Ethernet-style sharing is enough to tell you whether DHCP works elsewhere. If the adapter gets an address there, the hardware is doing its job and the original network needs attention.
If you administer the network, check the router, switch, or DHCP server in this order:
- Confirm the DHCP server is running and has free leases.
- Confirm the port is in the correct VLAN.
- Check whether the adapter’s MAC address is allowed.
- Check whether 802.1X or another authentication step is required before normal access.
If the DHCP scope is exhausted or the server is down, the adapter will keep failing even though the physical link looks fine. If the port is on the wrong VLAN, DHCP requests may never reach the scope that should answer them. If MAC filtering or 802.1X is enabled, the network may see the device and still refuse access until it is registered or authenticated.
If the network owner can make the built-in Ethernet port work on the same machine but the USB-C adapter still fails, that is a strong sign of network policy tied to the adapter’s identity rather than a general outage.
How to confirm the adapter is actually working
A real fix gives you a normal lease, not just a flashing link light. You want four things at the same time: a valid IPv4 address in the right subnet, a default gateway, DNS servers, and an active lease.
After the fix, check for these signs:
- The adapter has a normal IP address, not 169.254.x.x.
- The default gateway is present.
- DNS servers are present.
- The lease is active.
- You can reach the gateway, local resources, and the wider internet.
On Windows, ipconfig /all should show DHCP enabled, a valid IPv4 address, gateway, and DNS entries. On macOS, the Ethernet service should show an IP address and router field, not a self-assigned warning. On Linux, ip addr and resolvectl status or your distro’s network tool should show a live address and name servers.
IPv4 address: a valid address from your network
Default gateway: present
DNS servers: present
DHCP lease: activeIf local devices respond but public sites do not, the adapter is probably fine and the remaining issue is DNS or upstream internet service, not DHCP. If the address is valid but the gateway is missing, that is still a network configuration problem, not a healthy lease.
When to stop troubleshooting and hand it off
Stop and escalate when the adapter works on one network but not another, when the port requires 802.1X or MAC registration, or when the built-in Ethernet behaves differently from the USB-C adapter on the same network. Those signs point to policy or infrastructure, not a broken dongle. Replace the adapter only when it fails on multiple cables, ports, and networks, or when the OS cannot reliably see the device at all.
Give IT or the network owner these details:
- The device model and operating system.
- The adapter brand and model, if known.
- Whether the link light is on.
- The exact IP state, including any 169.254.x.x self-assigned address.
- Whether DHCP works on another network.
- Whether the built-in Ethernet port works on the same machine.
- The adapter’s MAC address.
- Any recent changes to VLANs, access control, 802.1X, or MAC registration.
That gives them enough to check DHCP scopes, switch authorization, and allowlists without making you repeat the same tests. If you have already confirmed the adapter works elsewhere and the network still rejects it, hand it off rather than replacing hardware at random.
Frequently Asked Questions
Does a 169.254.x.x address mean my USB-C Ethernet adapter is broken?
Usually not. It means the device did not get a valid DHCP reply, so it assigned itself a fallback address instead. That can come from a bad cable or adapter, but it can also come from static settings, DHCP trouble, or a network that blocks the adapter.
Why does the link light come on if I still have no IP address?
Because link and DHCP are different steps. The hardware can negotiate Ethernet successfully, which turns on the link light, while DHCP still fails later when the network does not hand out an address. That pattern often points to policy, server, or configuration issues rather than a dead adapter.
What should I test first if my USB-C Ethernet adapter only fails on one network?
Test it on a second network, like a home router or a phone hotspot setup with Ethernet-style sharing. If it gets an address there, the adapter is probably fine and the original network is blocking it through DHCP, VLAN, MAC filtering, or 802.1X.
Sources
- USB-C Ethernet Shows 169.254.x.x? Fix DHCP Issues – Lention (lention.com)
- USB-C Ethernet adapters not working with … - Apple Community (discussions.apple.com)
- Apple USB Ethernet Adapter has a self-assigned IP address and will not be able to connect to the Internet (apple.stackexchange.com)