Fix Excessive Packet Reordering on Your Network

You're getting "Excessive Packet Reordering" in your network logs, or maybe your VoIP calls sound like a robot gargling gravel. That's packet reordering. Happens when packets arrive out of sequence—like someone shuffling a deck mid-deal. I've seen this wreck a small law firm's phone system for two weeks before they called me.

The culprit is almost always one of three things. I'll walk through each from most common to least. Skip the other noise—no need to reboot your router or update firmware unless I call it out.

1. Router or Switch QoS Settings Are Screwing Up Packet Order

This is the #1 cause I see. Consumer routers and even some enterprise switches have QoS features that try to prioritize traffic, but they're implemented like a drunk octopus playing Tetris. They'll queue packets, delay them, then release them in a different order. That causes reordering on the receiving end.

The real fix: Log into your router or switch and disable QoS entirely. I mean all of it—WMM, DSCP, CoS, traffic shaping, whatever. Had a client last month with a Netgear Nighthawk RAX50 where the "Gaming QoS" was rearranging his office's VoIP packets. Turned it off, calls cleared up instantly.

Steps for most routers:
1. Open admin panel (usually 192.168.1.1 or 192.168.0.1)
2. Look under Advanced > QoS Setup
3. Disable QoS or set it to "Off"
4. Save and reboot

If you absolutely need QoS (e.g., you have 20 people on a 50 Mbps line), use a proper router with hardware-based QoS like a Ubiquiti EdgeRouter or pfSense box. Consumer QoS is garbage for packet ordering.

2. Duplex Mismatch Between Devices

This one's sneaky. When one device runs at full duplex and the other runs at half duplex—or auto-negotiation fails—you get collisions and retransmissions. Those force packets to be resent, often out of order. I walked into a doctor's office where the switch was set to 100Mbps Full, but the router auto-negotiated to 100Mbps Half. Packet reordering through the roof.

The fix: Check both ends of the link. On a managed switch, SSH in and look at the port status. On unmanaged gear, you might need to check the device's NIC settings (Windows: Control Panel > Network > Properties > Configure > Advanced > Speed & Duplex). Set both ends to the same fixed speed/duplex—typically 1000Mbps Full for modern gear, or 100Mbps Full if that's what the hardware supports.

Example on a Cisco switch:
interface gigabitethernet0/1
 speed 1000
 duplex full

I've seen auto-negotiation fail on older Cat5e cable runs over 80 feet. If you can't fix the mismatch, try a different switch port or replace the patch cable with a known-good Cat6.

3. Bad Network Cable or Connection

You'd be surprised how often a kinked cable or a loose RJ45 connector causes packet reordering. Physical issues introduce micro-bursts of errors that force TCP retransmissions. Those retransmitted packets arrive later than the originals, scrambling the order. Happened to a client who had a cable run under a rolling office chair—crimped jacket, intermittent shorts.

The fix: Try a known-good cable first. If that doesn't help, check the termination. Use a cable tester if you have one (a basic continuity tester works for most cases). Look for:

• Frayed or bent pins on the plug
• Cable runs near fluorescent lights or power lines (EMI)
• Damaged wall jacks (I've seen jacks where the punchdown tool crushed the wire)

Re-terminate both ends if you suspect the issue. I carry a Klein crimper and a bag of Cat6 ends for this exact reason. Also, swap out the patch cables from the wall to the device—those get stepped on and twisted more than anyone admits.

Quick-Reference Summary Table

Go through these in order. I'd bet money you'll fix it within 15 minutes. If not, it's likely an upstream ISP issue—call them and ask about jitter on your connection. But 9 times out of 10, it's one of these three.