If your USB-C Ethernet adapter can ping the router but not the internet, the local link is working. The break is farther out: usually DNS, the default gateway, routing, or a router policy is stopping traffic after it leaves your laptop. The fastest fix is to test a public IP first, then a hostname, and only then change DNS, gateway, or driver settings.
What this symptom really tells you
Pinging the router tells you the adapter, cable, and local Ethernet link are alive. It also tells you your laptop can reach the first hop on the network.
It does not prove internet access. Traffic can still fail at DNS resolution, at the default gateway, in the route table, in router policy, or on the ISP path. I split this into two questions right away: can the machine reach outside addresses by IP, and can it resolve names? That separation saves a lot of guesswork.
Before you start
Use this checklist before you change anything:
- Make sure the adapter is firmly seated and the Ethernet cable is good.
- If possible, have one other device ready to test with the same cable and router port.
- Know whether the laptop uses DHCP or a static IP.
- If you’re on a company or managed network, stop and check for router, VLAN, or device-policy changes before you edit network settings.
- If the computer had recent network or driver changes, keep that in mind; this kind of symptom can be local to one machine.
This is a safe, reversible troubleshooting path. Don’t start by changing several settings at once, because that makes it harder to tell which one mattered.
Fastest fix order
- Check whether the local link is up.
ping your-router-ipIf you can ping the router, the adapter and cable are at least working on the local LAN. If you cannot, fix the cable, port, adapter seat, or link status first.
- Test the internet by IP address, not by name.
ping 1.1.1.1A public IP test bypasses DNS. If this works, the path out to the internet is probably fine and the problem is name resolution. If this fails, DNS is not the first thing to touch.
- Test a hostname.
ping example.comIf the IP ping works but the hostname ping fails, you have a DNS problem. If both fail, look at gateway, routing, router policy, MTU, or ISP connectivity instead.
- Check your IP configuration, especially the default gateway.
If the adapter gets an address from DHCP, renew the lease and confirm it received a valid IP address, subnet mask, default gateway, and DNS server. If you use a static address, confirm the IP, mask, and default gateway all belong to the same network. A missing or wrong default gateway is a common reason a laptop can still talk to local devices but not reach the internet.
- Compare with another device on the same cable and router port.
Microsoft’s guidance for Ethernet problems is to try another PC on the same network. If the second device works, the first PC is the likely problem. If neither device works, the router, ISP, or USB-to-Ethernet adapter is more likely. BroadbandNow gives the same general split: if Ethernet works on other devices but not yours, look at drivers. If the router is not handing out an address, renew the IP and check the router.
- If only one computer fails, check the adapter driver and local security software.
If the adapter works on one machine but not another, that points to the driver, the OS network stack, or a machine-specific policy rather than the cable alone. Outdated or missing network drivers are a common cause when Ethernet works on other devices but not on the computer you’re troubleshooting.
- If every device fails, move upstream.
If the same cable and router port fail on another device too, the modem, router, or ISP path is the likelier problem. At that point, rebooting the modem and router, checking WAN status, and confirming service with the ISP are more useful than changing the laptop again.
How to tell DNS failure from gateway or routing failure
The easiest split is this:
- If a public IP pings but a hostname does not, DNS is the problem.
- If both the public IP and the hostname fail, DNS is probably not the root cause.
- If the router pings but outside IPs do not, suspect the default gateway, routing, MTU, firewall policy, or upstream service.
A wrong or missing default gateway can produce a very specific pattern: local LAN traffic still works, the router replies to ping, but anything meant for the wider internet never leaves the subnet. That is why I check the gateway before I touch DNS. If the gateway is blank or points to the wrong device, fix that first. If the gateway is correct and IP pings still fail, compare the route table on the failing machine with a working one instead of guessing at random settings.
If DNS is the only broken piece, the adapter is usually fine. In that case, changing the DNS server or renewing DHCP can solve the symptom without touching routing.
Router features that can block just this device
Yes, a router can block one device while local LAN pings still work. That is one reason a phone, tablet, or second laptop may be fine on the same network while this machine is not.
Check for these device-specific blocks:
- Access control or MAC filtering on the router
- Guest network isolation that allows local access but blocks the wider network
- Parental controls or device profiles that restrict internet access
- Firewall rules on the router that target this device only
- A bad DHCP reservation that gives this machine the wrong address, gateway, or DNS server
If the router is managing devices by policy, the symptoms can look exactly like a bad adapter. Local pings still work because the link is up, but internet traffic is filtered or misrouted after that point.
If the same adapter works on another computer, the adapter itself is less suspicious. If it fails on one computer but not another, focus on the driver, OS settings, and any endpoint security software before blaming the router.
When the modem, router, or ISP is the real problem
If another device on the same cable and port also cannot reach the internet, the problem is probably upstream of the laptop. That can be the router, the modem, or the ISP path.
The practical test is simple: if the laptop can ping the router but nothing outside the local network works on any device, the laptop is not the only thing to check. Rebooting the modem and router, confirming the WAN light or status page, and checking for a service outage are the right next steps. If your router has a status page, look for WAN address and connection state; if that looks wrong, the issue is outside the USB-C adapter.
BroadbandNow’s troubleshooting guidance also separates cable problems, router IP assignment problems, and driver problems instead of treating every Ethernet failure the same way.
Verify the fix
You know the problem is fixed when all three checks line up:
- The adapter still pings the router.
- A public IP ping works.
- A hostname ping works.
If the public IP works but hostnames do not, keep working on DNS. If the router pings but the public IP still fails, go back to gateway, route, router policy, or ISP checks. The point is not to make the icon look connected; the point is to confirm the packet can leave the local network and come back.
Conclusion
If you only remember one thing, make it this: test by IP first, then by name. That tells you whether to fix DNS, the gateway, the router policy, or the adapter driver before you waste time chasing the wrong layer.
Frequently Asked Questions
Should I change DNS first if websites do not load?
No. Test a public IP first, because that bypasses DNS. If the IP ping works and only hostnames fail, then DNS is the likely fault, and changing the DNS server is a sensible next step.
Can my USB-C Ethernet adapter look connected and still have no internet?
Yes. The link can be up while the default gateway, DNS server, router policy, or ISP path is broken. A connected icon only tells you the adapter sees Ethernet; it does not prove traffic can reach the internet.
Sources
- Fix Ethernet connection problems in Windows | Microsoft Support (support.microsoft.com)
- How to Set Up and Troubleshoot Ethernet Connections (broadbandnow.com)