If an Intel Ethernet controller can ping the router but not the internet, the local link is working. The break is beyond the router: DNS, the default gateway, routing, IPv6, a proxy or VPN, security software, or a router rule. Start by testing router, public IP, and DNS separately. Then change only the setting that matches the failure.
What this symptom usually means
This pattern means your PC reaches the local network, but traffic breaks somewhere past the router. A successful ping to the router proves the cable, link, local IP address, and first hop are working for basic traffic. It does not prove that websites will load or that name lookups are working.
Treat this as a layer-by-layer fault, not an Intel adapter fault by default. The real question is not “is the adapter alive?” It is “which hop stops working: the router, the internet path, or DNS?”
Here is the quickest way to read the symptom:
| Test | What works | What it usually means |
|---|---|---|
| Ping router | Local link is up | The PC can reach the gateway on the LAN |
| Ping public IP | Internet path by raw IP | If this fails, look at gateway, routing, IPv6, proxy, VPN, firewall, or router filtering |
| Resolve a name | DNS | If this fails but public IP works, the problem is name resolution |
If router ping works, but both the public IP ping and DNS fail, stop thinking about the adapter first. That pattern usually points to routing, gateway, IPv6, or a router-side rule that is blocking only this device.
Before you start
Work on one change at a time, and test after each one. That keeps you from losing the clue that shows where the fault really is.
Use a wired connection on the Intel Ethernet controller while you test. If you can, have another device connected to the same router for comparison.
If the PC uses a static IP, note the current IP address, subnet mask, gateway, and DNS settings before changing anything. If you use a VPN client, proxy, or security suite, know how to turn it off and back on cleanly.
Run the three tests in order
- Ping your router’s LAN address. If you do not know it, open Command Prompt and run
ipconfig, then look forDefault Gateway.
ping 192.168.1.1If this works, the local link and gateway path are alive enough for local traffic.
- Ping a public IP address, not a website name. This skips DNS and checks whether your PC can reach the internet by raw IP.
ping 8.8.8.8If this fails while router ping works, the break is usually gateway, routing, IPv6 mismatch, a proxy or VPN, a firewall, or a router rule blocking this device.
- Test name resolution with a domain. If the public IP ping works but a site name does not, that points to DNS.
nslookup www.microsoft.comIf nslookup cannot return an answer, or it returns the wrong server, fix DNS first. If it resolves but browsers still fail, look harder at proxy, security software, or browser-specific filtering.
Think of it this way: router ping proves the LAN path; public IP ping proves raw internet reachability; DNS proves name resolution. Those are separate checks, and they do not fail for the same reason.
If public IP works, fix DNS first
If ping 8.8.8.8 works but websites do not load by name, this is usually a DNS problem, not an Ethernet problem. DNS turns a name like example.com into an IP address your PC can contact.
Start in Windows on the Intel adapter. Open Network and Sharing Center, then the adapter properties, then Internet Protocol Version 4 (TCP/IPv4). If DNS is set manually, switch it back to automatic first unless you know exactly why it was set by hand. If the router hands out DNS, make sure the router’s DNS path is still valid and not stale or misconfigured.
Then check for a leftover manual DNS entry or other old network setting. I have seen this after a move, a VPN install, or a router change: the link looks fine, raw IP traffic works, but names still fail because Windows is using the wrong resolver.
If you change DNS, change one place at a time and test again after each change. Don’t guess at multiple settings together, because that makes it impossible to tell which one fixed it.
If raw IPs work but names do not, the Intel controller is usually not the real fault. The problem is name resolution on the PC or in the router-provided DNS path.
If public IP fails, check gateway, IPv6, and filtering
If router ping works but a public IP does not, focus on forwarding, not DNS. That usually means a bad default gateway, a static-IP mistake, IPv6 trouble, or something on the PC or router blocking outbound traffic.
- Check the default gateway shown by
ipconfigand make sure it matches the router address you actually use. If the PC has a static IP, verify the gateway, subnet, and DNS values against the current network. A wrong gateway can still leave local LAN traffic working, which makes the problem look like “internet only.”
- Check IPv6. A mismatch where IPv6 is enabled but the router or ISP path is broken can cause odd behavior, especially if some apps try IPv6 first. For testing, temporarily disable IPv6 on the adapter, then retest the public IP ping and a browser page. If that fixes it, the issue is on the IPv6 path, not the Intel controller.
- Check proxy, VPN, firewall, and security software. A proxy setting can send web traffic to a dead server. A VPN client can capture traffic and fail to release it cleanly. Security software can block browser traffic while ICMP ping still succeeds, so a working ping does not clear the PC.
- Check router-side filtering. Parental controls, MAC filtering, access control, device quarantine, per-device internet rules, and content filters can allow local LAN access but block WAN traffic for one device. The clue is that another PC on the same router works normally, while this one does not.
If you are tempted to reinstall the Intel driver right away, stop and test first. The most common mistake is updating the driver before proving whether the machine can reach a public IP directly.
When the failure is on the PC, the safest order is: confirm the symptom, isolate the layer, change one setting, and verify again. When the failure is on the router, stop changing adapter settings and move to the router admin side instead.
What Windows settings can trigger this pattern
These are the Windows-side settings I would check first on a machine with an Intel Ethernet controller:
- Manual DNS values that no longer match the network.
- A static IP with the wrong gateway or subnet.
- IPv6 enabled when the IPv6 path is broken.
- A proxy that is still turned on after a prior network change.
- A VPN client that is still binding traffic or leaving routes behind.
- Security software or a firewall rule that allows ping but blocks browsing.
The adapter itself is often fine. The pattern usually comes from the settings layered on top of it.
If you change one of these settings, test immediately after the change. Do not make three changes, reboot, and hope the problem stays gone. That may get you back online, but it will not tell you what was wrong.
What to verify before calling the ISP or router admin
After each change, repeat the same two tests: ping the public IP and resolve a domain name. If both work, open a browser and load a few different sites. That confirms the break was on the PC side and the fix took effect.
If the public IP ping still fails after you have checked gateway, IPv4, IPv6, proxy, VPN, firewall, and router filtering, the fault is more likely upstream or on the router itself. At that point, try another device on the same router, then test this PC on another network if you can. If the PC works elsewhere, the router or ISP is the likely problem; if it fails everywhere, the issue is on the PC.
If one device on the router works and this Intel Ethernet PC does not, stop changing the adapter settings and ask the router admin to review access control, filtering, quarantine, or per-device rules. If every device on the connection has the same failure, contact the ISP and report the exact test that fails: router ping, public IP ping, or DNS resolution.
Conclusion
If you can ping the router but not the internet, don’t guess. Test router ping, public IP ping, and DNS in that order. Then fix the matching layer or hand the problem to the router admin or ISP once the PC-side checks are done.
Frequently Asked Questions
Should I reset the Intel Ethernet adapter first?
No. Test the router, a public IP, and DNS first so you know what is actually broken. Resetting the adapter before that can erase the clue that tells you whether the problem is DNS, routing, proxy, IPv6, or router filtering.
Can a firewall block internet but still let me ping the router?
Yes. Some firewalls and security suites allow ICMP ping but block browser traffic, DNS, or other outbound connections. If a public IP ping fails or browsers hang while router ping still succeeds, temporarily rule out security software before changing more network settings.
Why does one device work on the router and this Intel PC does not?
That often means the router is applying per-device rules, such as MAC filtering, parental controls, access control, or a device quarantine. If another PC on the same network gets online normally, the router is a strong suspect and the PC may not be at fault.