Packet loss on Ethernet but not Wi-Fi points first to something unique to the wired path: the cable, router port, wall jack, dock, switch, Ethernet adapter, driver, or wired network configuration. Repeat the same gateway and public tests on both connections, then swap one wired component at a time.
Microsoft Ethernet troubleshooting, ping behavior, and Get-NetAdapterStatistics documentation plus IETF UDP guidance were checked on August 4, 2026.
IN THIS GUIDE
Packet loss on Ethernet but not Wi-Fi sounds backward because the cable is supposed to be the responsible adult in the room. Still, Ethernet is not one magic object. It is a chain that can include a cable, wall jack, USB dock, switch, router port, network adapter, driver, and software filters.
If Wi-Fi stays clean while the wired connection repeatedly loses packets, inspect what changed between those paths. Do not start by replacing the ISP, changing DNS, and buying a router with enough antennas to receive weather satellites.
Prove that Ethernet is the only failing path
Use the same PC or console, game region, destination, room, and 30-minute window. Pause downloads, cloud sync, streams, and updates. Test Ethernet, Wi-Fi, then Ethernet again. Three runs in that order help catch a problem that disappeared because household traffic changed.
Record:
- the connection type and exact time;
- game region, mode, and displayed loss;
- whether voice chat or another game also failed;
- gateway and public ping results;
- every cable, port, dock, or switch in the wired path.
Do not compare a desktop on Ethernet with a phone on Wi-Fi. Different hardware and apps create several new variables. If the opposite pattern appears, use the packet loss on Wi-Fi but not Ethernet guide instead.
Also confirm that the symptom is missing packets. If packet loss stays at 0% while latency jumps, follow the high ping on Ethernet checks. If ping and loss stay steady while the picture hitches, inspect FPS, frame time, CPU, GPU, storage, and heat.
Compare the router and public path on both connections
On Windows, run ipconfig and find the Default Gateway for the active adapter. Open two Command Prompt windows. Test the router in one:
ping -n 200 YOUR_GATEWAY_IPTest a stable public destination in the other:
ping -n 200 1.1.1.1Microsoft documents ping as an IP-level reachability test that reports round-trip time and missing replies. Run both commands first over Ethernet, then over Wi-Fi. A public address is a comparison point, not the game server.
| Ethernet result | Wi-Fi result | Better first suspect |
|---|---|---|
| Gateway loses packets | Gateway stays clean | Cable, port, dock, switch, wired adapter, or driver |
| Gateway stays clean, public target loses packets | Both stay clean | Wired software path, router handling, or an inconsistent test |
| Both connections lose packets beyond the router | Both fail | Router, modem, ISP access, load, or wider route |
| Both tests stay clean, one game reports loss | Other games stay clean | Game client, telemetry, destination, route, or server |
One timeout is not a conviction. Routers and public hosts can limit diagnostic replies while forwarding ordinary traffic normally. Look for a pattern that repeats on Ethernet, disappears on Wi-Fi, and lines up with the game symptom. For the wider branch, use the packet loss but internet is fine checklist.
Remove every extra wired hop
Build the shortest possible wired path: one known-good cable from the gaming device directly to a LAN port on the main router. Temporarily bypass these items:
- a USB Ethernet adapter or laptop dock;
- a wall jack or patch panel;
- a secondary switch;
- a powerline adapter;
- a mesh satellite with an Ethernet socket;
- a console stand or hub carrying the network connection.
Repeat the gateway ping and the same game test. If the direct path is clean, add one item back at a time. The first item that makes repeatable loss return deserves investigation, not immediate ceremonial disposal.
If the direct path still loses packets, reseat both cable ends, try another known-good cable, and move to another LAN port on the main router. Microsoft recommends checking the cable, trying another router port, restarting the modem and router, and testing the connection again. Follow the hardware maker’s restart order if it differs.
A cable can remain connected while producing errors. A port can also be damaged or poorly negotiated. Leave speed and duplex on automatic unless the adapter or router maker gives a specific supported instruction. Forcing a random value can create the mismatch you were trying to find.
Watch Ethernet adapter counters during the failure
On Windows PowerShell, list the active adapters and negotiated link speed:
Get-NetAdapter | Format-Table Name, Status, LinkSpeedThen view the Ethernet adapter’s statistics:
Get-NetAdapterStatistics -Name "Ethernet"Use the actual adapter name shown by the first command. Microsoft says the statistics include broadcasts, multicasts, discards, and errors.
Take one snapshot before the test and another after the loss occurs. Totals that existed since startup prove little. Error or discard counters that rise during the bad wired run, then stay flat during the Wi-Fi comparison, are more useful evidence. The exact counters available depend on the adapter and driver.
A link speed below what the hardware normally negotiates does not itself prove packet loss. It does tell you to isolate the cable, port, dock, and adapter. A link that repeatedly disconnects and reconnects is even louder evidence that the local wired chain needs attention.
Test the adapter, driver, and software path
If cables and ports pass, focus on the gaming device:
- Update the Ethernet driver from the PC, motherboard, dock, or adapter maker. Save the current version first so you can roll back if the update makes things worse.
- Compare a different Ethernet adapter. A known-good USB adapter can isolate the built-in adapter, but connect it directly rather than through the same suspect dock.
- Remove overlapping network tools one at a time. Disconnect another VPN, traffic optimizer, web shield, virtual switch, or packet-capture driver for one controlled run. Keep the operating system firewall enabled.
- Check power and dock behavior. If loss appears only through a dock, test the laptop’s direct port or a separate adapter. Update dock firmware from its maker.
- Use Windows network reset only near the end. Microsoft notes that it removes and reinstalls network adapters and may require VPN or virtual-switch software to be set up again.
After each change, repeat the same Ethernet, Wi-Fi, Ethernet sequence. Changing the driver, cable, port, duplex, DNS, and router settings together produces a result with no explanation attached.
Know when the wired path is cleared
The wired hardware is less likely to be the cause when gateway tests stay clean on several cables and ports, adapter counters remain steady, and only one game still reports loss. Check that game’s official service status, selected region, and support instructions. Save match IDs and timestamps. The packet loss in one game guide covers that destination-specific branch.
A VPN cannot repair a damaged cable, bad port, unstable dock, or adapter errors because the tunnel still crosses that local wired link. Once the gateway remains clean, a nearby endpoint may be tested only as an alternate upstream route. It may help a poor route or add more delay. Keep it only when repeated direct and tunneled runs show a real improvement.
LagZero is being built for that final route comparison, not for making a bent cable feel emotionally supported. Join the LagZero waitlist when the local wired path is clean and you want to test another route after launch.
FAQ
Why would Ethernet have packet loss when Wi-Fi does not?
Ethernet and Wi-Fi use different local hardware and drivers. A damaged cable, bad router port, wall jack, dock, switch, wired adapter, negotiation problem, or Ethernet software filter can affect only the wired path. Comparable gateway tests help isolate that difference.
Can a bad Ethernet cable cause packet loss without disconnecting?
Yes. A cable or connector can remain linked while errors occur. Compare a known-good cable and another router port, then watch whether adapter error or discard counters rise during the problem.
Should I force Ethernet speed or duplex settings?
Usually no. Leave automatic negotiation enabled unless the hardware vendor or network administrator provides a specific setting for both ends. A mismatch can cause poor performance and errors.
Will changing DNS fix packet loss on Ethernet?
Usually not. DNS helps locate a service before a connection is established. It does not repair packets lost between the device and router or along an active game path. A DNS change may help a lookup issue, not a faulty wired hop.
Can a gaming VPN fix wired packet loss?
Not when the loss begins on the cable, port, dock, switch, adapter, or router-facing hop. A VPN may help only after the local path is clean and an upstream route remains the likely cause. It can also add latency or loss, so compare repeated runs.