Duplex Mismatch & Speed Negotiation

In Ethernet networking, devices must agree on two physical-layer parameters before they can communicate effectively: Speed (e.g., 100 Mbps or 1000 Mbps) and Duplex.

• Half Duplex: A device can send data, or receive data, but it cannot do both at the same time. Think of a two-way radio (walkie-talkie). If both devices transmit simultaneously, a collision occurs, destroying the data.
• Full Duplex: A device can send and receive data simultaneously without collisions. Think of a telephone.

Auto-Negotiation

When you plug a cable between a PC and a switch, they send fast link pulses to advertise their capabilities. This is Auto-Negotiation. If both support 1000 Mbps Full Duplex, they agree to use it.

Note: Gigabit Ethernet (1000 Mbps) fundamentally relies on Auto-Negotiation and is designed exclusively for Full Duplex operation.

The Duplex Mismatch Scenario

A Duplex Mismatch occurs when the two ends of a single cable operate in different duplex modes. The classic scenario happens when a network engineer manually hardcodes a switch port to "100 Mbps / Full Duplex" but leaves the connected server set to "Auto".

The server attempts to auto-negotiate. Because the switch port is hardcoded, the switch stays silent. The server detects the 100 Mbps electrical signal, but because it didn't receive an auto-negotiation reply, it falls back to the Ethernet failsafe standard: Half Duplex.

You now have:

• Switch Port: 100 Mbps / Full Duplex
• Server Port: 100 Mbps / Half Duplex

The Symptoms

A duplex mismatch is insidious because the link status shows "UP" and basic pings usually work perfectly. The network appears healthy until placed under load.

When the server tries to download a large file, the switch (thinking it is in Full Duplex) blasts packets at the server while simultaneously listening for replies. The server (in Half Duplex) assumes a collision has occurred because it is receiving data while trying to transmit. The server drops the packets and backs off.

Symptoms include:

• Excruciatingly poor Throughput (e.g., a 100 Mbps link transferring at 2 Mbps).
• High interface error counters on the switch (specifically Late Collisions and FCS/CRC errors).
• Intermittent application timeouts and massive TCP retransmissions.

Troubleshooting Workflow

1. Check Link State: Verify both ends of the cable agree on speed and duplex. (e.g., show interfaces on a switch, or the Network Adapter properties in Windows).
2. Check Interface Errors: A high count of Late Collisions is the hallmark of a mismatch. (Note: In a healthy, modern Full Duplex switched network, collisions do not exist. Any collision counter increasing indicates a physical problem or a mismatch.)
3. Check Cabling: A severely damaged cable can cause auto-negotiation to fail or negotiate at lower speeds (e.g., a Gigabit port negotiating at 100 Mbps Half).
4. Verify Auto-Negotiation: Avoid the outdated 1990s advice of hardcoding speed and duplex. Modern best practice is to leave all ports on Auto-Negotiate unless connecting to legacy specialized equipment.