Random Ping Drops & Packet Loss? Fix Speed/Duplex on Windows

A user complains that the network “keeps cutting out.” File copies stall, video calls freeze for a second, and a continuous ping shows the odd Request timed out in the middle of a perfectly normal day. The switch looks fine. The cable looks fine. Everything looks fine — and that is exactly what makes random ping drops so annoying to chase.

In a lot of real support cases the culprit is a Speed and Duplex mismatch on the network adapter: someone (or some old driver default) forced the NIC to a fixed setting like 100 Mbps Half Duplex while the switch port is negotiating something else. The link still comes up, so nothing screams “broken” — but packets get lost under load. This guide shows how to spot it and fix it the right way.

Table of Contents

1. What a duplex mismatch actually looks like
2. Why a mismatch drops packets
3. Troubleshooting flow
4. Step 1: Check the current link speed
5. Step 2: Check the Speed & Duplex setting
6. Step 3: Set it back to Auto Negotiation
7. Step 4: Rule out cable and switch problems
8. Step 5: Confirm with a sustained ping test
9. Quick reference table
10. FAQ

What a duplex mismatch actually looks like

The link is up, but the connection is unreliable. Typical signs:

• A continuous ping (ping -t) shows occasional Request timed out or latency spikes, especially while data is actually flowing.
• Large file transfers start fast then crawl or stall.
• Only one machine is affected, while others on the same switch are fine.
• The adapter shows an odd link speed — for example 100 Mbps on a gigabit switch and gigabit cable, or Half Duplex on a modern LAN.

If the whole office is down, it is probably not this. A duplex mismatch is usually a single-port, single-device problem.

Why a mismatch drops packets

Modern Ethernet is full duplex — both ends can send and receive at the same time, and there are no collisions. That only works if both ends agree. Auto Negotiation is how they agree.

When one side is forced to a fixed value and the other is left on auto, auto-negotiation fails to see a partner and falls back to half duplex. Now one end thinks it is full duplex and transmits whenever it likes; the other end is half duplex and treats those overlaps as collisions and late collisions. The result is retransmissions, errors, and exactly the kind of intermittent loss that shows up as random ping drops under load.

Troubleshooting flow

Step 1: Check the current link speed

Open PowerShell and look at what the adapter actually negotiated:

Get-NetAdapter | Format-Table Name, Status, LinkSpeed, FullDuplex -Auto

On a gigabit network you expect 1 Gbps and FullDuplex = True. If you see 100 Mbps, 10 Mbps, or FullDuplex = False on hardware that should do better, that is your lead. You can also check it quickly in the GUI: run ncpa.cpl, double-click the adapter, and read Speed on the Status window.

Step 2: Check the Speed & Duplex setting

Now look at the adapter's advanced property to see whether it was forced:

Get-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex"

If DisplayValue is anything other than Auto Negotiation (for example 100 Mbps Half Duplex or 100 Mbps Full Duplex), it has been hard-set. That is the thing to change. (The property name can vary slightly by driver — some show it as “Speed/Duplex” or “Link Speed & Duplex.”)

Step 3: Set it back to Auto Negotiation

GUI method (safest): Device Manager → Network adapters → right-click your NIC → Properties → Advanced tab → select Speed & Duplex → set the value to Auto Negotiation → OK.

PowerShell method (run as Administrator):

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex" -DisplayValue "Auto Negotiation"

The link will drop for a second as it re-negotiates. Re-run the Get-NetAdapter command from Step 1 and confirm you now see the full line rate and FullDuplex = True.

Important: the modern best practice is auto on both ends. Do not “fix” a mismatch by forcing the PC to match a forced switch port — fix whichever end was forced so both sides auto-negotiate. Forcing one end is the classic way these problems are created in the first place.

Step 4: Rule out cable and switch problems

If auto-negotiation still lands on a low speed, the physical path may be limiting it:

• Cable category: Gigabit needs all four pairs and at least Cat 5e. A damaged or cheap Cat 5 cable can force the link down to 100 Mbps.
• Cable length / damage: Over ~100 m, or with a crushed or kinked cable, you get errors. Swap in a known-good patch lead as a test.
• Switch port: Try a different port. A port that was manually configured (common on managed switches) can force speed/duplex — have the network team set it back to auto or to a matching fixed value.
• Wall jack / patch panel: One bad punch-down pair is enough to drop you to 100 Mbps or cause intermittent loss.

Step 5: Confirm with a sustained ping test

Prove the fix held under load. Run a long ping to the gateway while copying a large file:

ping 192.168.1.1 -t
:: let it run a few minutes, then press Ctrl+C to see the loss summary

You want 0% loss and steady, low latency even while data is flowing. If it is clean now, the mismatch was the problem. If you still need to measure real throughput end-to-end, a quick throughput test between two machines will confirm the link is healthy — see our guide on testing network speed between two computers with iperf3.

Quick reference table

What you see	Likely cause	First fix
Link is 100 Mbps on gigabit kit	Forced speed or bad cable	Set NIC to Auto; swap cable
FullDuplex = False	Duplex mismatch	Auto Negotiation both ends
Loss only under load	Collisions from mismatch	Fix the forced end
One PC affected, rest fine	Local NIC/cable/port	Swap port and cable

FAQ

Should I force 1 Gbps Full Duplex to be safe?
No. Forcing is what usually causes mismatches. Leave both the NIC and the switch port on Auto Negotiation — that is the supported, reliable setting for modern Ethernet.

My link shows 1 Gbps Full Duplex but I still get drops. Now what?
Then it is not a duplex mismatch. Look at cable/jack errors, a failing NIC, driver issues, Wi-Fi vs wired confusion, or something upstream (switch, gateway). Check adapter error counters and try another port.

Is this a Windows-only problem?
No — duplex mismatch is a physical-layer Ethernet issue and happens on any OS. The checks here are just the Windows way to read and change the setting.

Where is the Speed & Duplex option if my adapter doesn't show it?
Some drivers hide it or name it differently. Update the NIC driver from the vendor, then look again under Device Manager → adapter → Advanced. USB and some laptop adapters may not expose it at all — those always auto-negotiate.

Related: Test network speed between two computers with iperf3