Advertisement

Realtek LAN adapter can ping router but not internet

If your Realtek LAN adapter can ping the router but not the internet, the local link is probably fine. This article uses ping, nslookup, tracert, and ipconfig to separate DNS, gateway, proxy, IPv6, and driver problems so you can stop guessing.

Networking 8 min read
A Windows desktop computer is connected by an Ethernet cable to a router on a desk.

If your Realtek LAN adapter can ping the router but not the internet, the local Ethernet link is usually fine. The fault is more likely above that layer: DNS, the default gateway, a proxy or VPN, IPv4/IPv6 settings, or the Realtek driver and settings. Start by separating routing from DNS, then move through the simplest Windows checks before you touch the driver or router.

What the ping results actually mean

Pinging the router shows that the PC can reach the local network. If a ping to a public IP like 1.1.1.1 fails and the router ping works, the break is usually at the default gateway, routing, the router’s WAN path, or the ISP side, not the Ethernet cable itself. If the IP ping works but a domain name does not, that points to DNS rather than the adapter.

A Realtek adapter can look healthy in Device Manager and still fail higher up in the path. I treat this symptom as a path problem first, and as a driver problem only after the basic checks rule out everything else.

Before you start

  • Use the router’s real LAN address in your tests, not a guessed one.
  • Run the checks in order so you keep a clean baseline.
  • If you change a setting and it does not help, revert it before trying the next one.
  • If the PC is on a work or school network, stop before changing DNS, proxy, or security settings you do not control.
  • You may need to restart Windows after a network reset for the change to take effect.

This is the fastest safe path on a Windows PC with Ethernet. First confirm whether the failure is DNS or routing. Then check for a wrong gateway or static IP. After that, rule out VPN, proxy, firewall, and security software. Only then touch the driver.

Match each result to the most likely cause

Use the tests to separate DNS, routing, proxy, and adapter problems instead of guessing.

ResultMost likely cause
Router ping works, public IP ping fails, tracert stops at the routerDefault gateway, router WAN, or ISP path
Router ping works, public IP ping works, domain lookup failsDNS server setting or DNS filtering
Router ping works, public IP ping works, but browsing failsProxy, VPN, MTU, or security software
ipconfig shows no default gateway or a strange oneStatic IP mistake or bad DHCP lease
nslookup works, but ping by name failsName resolution path is inconsistent, often IPv6, proxy, or security filtering
Router ping works only sometimesAdapter power saving, driver issue, or a flaky port

The most useful clue is often the default gateway in ipconfig. If it is missing or wrong, the PC may still talk to the LAN but have no proper next hop for the internet.

Fix the most common Realtek and Windows causes

  1. Turn off VPN and proxy first, then retest.

If a VPN client is connected, disconnect it and try the router ping, public IP ping, and browser again. Then check the Windows proxy setting.

Settings path
Settings > Network & internet > Proxy

If a proxy is on and you did not set it on purpose, turn it off and retest. If this fixes the issue, stop there.

  1. Check whether Windows has a valid IP, gateway, and DNS server.

Open ipconfig /all and look for the IPv4 address, subnet mask, default gateway, and DNS server lines.

Command Prompt
ipconfig /all

If the adapter has a static IP you did not intend to set, or the default gateway is missing or wrong, switch the adapter back to automatic addressing unless your network truly requires manual settings. A bad static IP can still allow router pings while breaking anything beyond the LAN.

  1. Separate DNS failure from general internet reachability.

If ping 1.1.1.1 works but browsing does not, or nslookup www.microsoft.com fails, the DNS setting is the first thing to fix.

Command Prompt
nslookup www.microsoft.com

If names start resolving after you correct DNS, the issue was DNS and not the cable. If public IP pings still fail, keep looking at the gateway, router WAN, or ISP path.

  1. Check IPv4 and IPv6 together.

A mixed setup can cause odd behavior if one stack is broken and the other is not. In the adapter properties, keep the protocol your network uses, and only disable IPv6 temporarily if you are testing a suspected IPv6 path problem. Re-enable it if the change does not help.

  1. Review the Realtek adapter’s advanced and power settings.

In Device Manager, open the Ethernet adapter’s properties and look for power-saving options and advanced features that affect link behavior. Power management that lets Windows turn off the device can cause intermittent loss of internet access while the LAN still looks alive. If you change an advanced setting, change one item at a time and retest before touching the next one.

  1. Reset the Windows network stack if the earlier checks do not explain it.

A reset can clear Winsock and TCP/IP state that has gone stale or been altered by security tools, VPN software, or failed configuration changes.

Command Prompt
netsh winsock reset
netsh int ip reset

Restart Windows after those commands. This does not fix every problem, but it is a good next step when the adapter still talks to the router and nothing obvious in ipconfig explains the failure. If the reset makes things worse, use System Restore or your normal rollback path if your setup has one.

  1. Check whether Windows security software is the blocker.

A firewall or endpoint security suite can allow local LAN traffic but still filter traffic once it leaves the subnet. If you use third-party security software, turn off its network filtering only long enough to test, then turn it back on if it was not the cause. If disabling it changes nothing, put it back immediately and keep troubleshooting elsewhere.

When to reinstall the driver or test the network gear

The Realtek driver itself becomes the likely cause when the tests point back to the adapter, not the rest of the network. That is usually the case if the link drops, the adapter reports normal status but routing still fails after you have ruled out VPN, proxy, DNS, gateway, IPv4/IPv6, and security software, or the issue follows the same PC across different ports.

If you reinstall or roll back the driver, use the safest path first. Remove only the adapter driver package from Device Manager if Windows offers that option, then restart and let Windows load a known working driver. If a newer driver from Realtek or your PC maker makes the problem start, rolling back is often the cleaner test than chasing newer settings. Check the current driver release on the official support source for your adapter or PC model before replacing anything. Realtek is the company behind these adapters, and its support site is the place to confirm the right package for your model.

You also need to test the router and modem side before blaming the PC. Try another device on the same Ethernet port, or move the PC to a different LAN port on the router. If another device reaches the internet from the same port, the router and WAN path are probably fine and the PC remains the better suspect. If no device can reach the internet, the router’s WAN side or upstream connection may be the real problem. One Microsoft Q&A case ended up being resolved only after the router was replaced, which is a reminder that the router can be the fault even when the PC-side tests look confusing.

Verify the fix

The issue is fixed when all three of these line up: the router pings, a public IP pings, and a domain name resolves and loads in a browser. You should also see a normal default gateway in ipconfig /all, and nslookup should return a result without delay or failure.

If the router ping works but the public IP still fails after the checks above, keep troubleshooting the gateway, router WAN, or ISP path instead of spending more time on the Realtek adapter. If public IP pings work but names still do not resolve, keep working on DNS, proxy, or security filtering.

Conclusion

If you’ve gone through the tests and the adapter still only reaches the router, the safest next move is to compare the same cable, port, and router path with another device before you swap more settings.

Frequently Asked Questions

Why can my PC ping the router but not websites?

That usually means the PC can reach the local network, but it cannot get out through DNS, the default gateway, or the router’s WAN path. The quickest split is to ping a public IP first, then test a domain name with `nslookup`.

Should I reset Windows networking right away?

No, not before you check the gateway, DNS, VPN, proxy, IPv4/IPv6, and security settings. A Winsock or TCP/IP reset can help when those checks do not explain the failure, but it should come after the simpler and more reversible tests.

Sources