How to Fix 2.5G and 10G Ethernet Not Working: Multi-Gig Speed Troubleshooting Guide

Multi-gigabit Ethernet—2.5 Gbps, 5 Gbps, and 10 Gbps—is showing up in mainstream routers, motherboards, and NAS devices, but getting it to actually run at those speeds is a different story. If you’ve installed a 2.5GbE or 10GbE NIC, connected it to a compatible switch or router, and still see “1 Gbps” in your adapter settings, you’re not alone. This guide walks through every common cause and fix.

How Multi-Gig Ethernet Speed Negotiation Works

Both ends of an Ethernet link use a process called autonegotiation to agree on the fastest speed they both support. For 2.5G to work, every device in the chain—your NIC, the cable, and the switch or router port—must support NBASE-T (IEEE 802.3bz). If any one link in that chain only speaks Gigabit, the entire connection falls back to 1 Gbps. That fallback is normal and expected; it’s not a failure. The challenge is finding which link is the bottleneck.

Step 1: Verify Every Device in the Chain Supports Multi-Gig

This is the most common mistake. Check each piece of hardware:

NIC / motherboard LAN: Open Device Manager on Windows (or lspci | grep Ethernet on Linux) and look up the exact chip model. Common 2.5GbE chips include the Realtek RTL8125B, Intel I225-V, and Marvell AQC107. Verify the spec sheet confirms 2.5G support.
Router or switch port: Most home routers only have one 2.5G WAN port and standard 1G LAN ports. If you plugged into a regular LAN port, you’re capped at 1 Gbps regardless of your NIC. Check which port on your router is the multi-gig port—it’s usually labeled or a different color.
Intermediate switch: If a switch sits between your PC and router, every port it uses must support 2.5G. An old unmanaged Gigabit switch will silently cap you at 1 Gbps.

Step 2: Check Your Ethernet Cable

Good news: 2.5GBASE-T was specifically designed to run over existing Cat 5e and Cat 6 cable at distances up to 100 meters. You do not need to re-cable for 2.5G. However, cable quality matters more at higher speeds:

Cat 5e: Officially supports 2.5G up to 100 m. Works in most well-installed runs, but marginal cable or connectors may cause the link to fall back to 1G.
Cat 6: The safest choice. Rated for 10G up to 55 m and 2.5G up to 100 m. Most short patch cables sold today are Cat 6.
Cat 6A: Required for 10G at full 100 m distance.
Damaged or crimped cables: A cable that works at 1G may fail negotiation at 2.5G. Try swapping the cable with a known-good Cat 6 patch cord first—it’s free and eliminates the most common culprit in minutes.

Step 3: Update Drivers (Windows and Linux)

Outdated drivers are the second most common cause of 2.5G negotiation failures, especially for the Intel I225-V, which shipped with well-documented firmware bugs in early revisions.

Windows Driver Update

Open Device Manager → expand Network Adapters → right-click your 2.5GbE adapter.
Select Uninstall device, check “Delete the driver software for this device,” and confirm.
Go to your motherboard or NIC manufacturer’s support page and download the latest LAN driver package directly—do not rely on Windows Update.
For Intel I225-V boards, also download the latest NVM (firmware) update from Intel’s support site. Boards shipped before 2022 often need the NVM flashed to fix known I225-V errata.
Install the new driver, reboot, then check Device Manager → Properties → Advanced → Speed & Duplex and confirm “2.5 Gbps Full Duplex” appears in the dropdown.

Linux Driver Update

On Linux, check your link speed with:

ethtool eth0

Replace eth0 with your interface name (find it via ip link). Look for Speed: 2500Mb/s and Duplex: Full. If it shows 1000Mb/s, the driver or firmware is the likely culprit. For Realtek RTL8125B, install r8125 from the manufacturer rather than relying on the in-kernel r8169 driver, which historically had poor 2.5G support. For Intel I225-V, ensure your kernel is 5.15 or newer; the igc driver in older kernels had autonegotiation issues.

Note: Users running Linux 6.16 reported that Intel 10GbE adapters using the ixgbe driver lost link recognition; rolling back to 6.15 resolves the issue while a kernel patch is awaited.

Step 4: Force Link Speed in the Adapter Settings

If autonegotiation keeps falling back to 1G even though both ends support 2.5G, try forcing the speed manually:

Windows: Device Manager → NIC Properties → Advanced tab → Speed & Duplex → set to 2.5 Gbps Full Duplex.
Linux: ethtool -s eth0 speed 2500 duplex full autoneg off. Make this permanent with a systemd-networkd or udev rule.

Forcing speed bypasses autonegotiation, which can expose whether the problem is negotiation logic or the hardware itself. If forcing 2.5G makes the link come up and stay stable, the issue was a software or firmware autonegotiation bug. If the link goes down entirely, the hardware or cable cannot sustain 2.5G and needs to be replaced.

Step 5: Check Router and Switch Firmware

Just like your NIC, routers and switches need up-to-date firmware to handle multi-gig connections reliably. Log into your router admin panel and check for firmware updates. ASUS, Netgear, TP-Link, and Ubiquiti all have histories of releasing multi-gig stability patches in minor firmware revisions. If you have a managed switch, update its firmware via the web UI or CLI as well.

Step 6: Inspect for Bufferbloat and Packet Drops

Some 2.5G adapters run at full link speed but drop packets under load due to insufficient interrupt coalescing or ring buffer settings. You might see the link negotiated at 2.5G but never actually transfer data at more than 1 Gbps in practice. Test with a speed test or iperf3 to a local server. If throughput is much lower than the link speed, tune the adapter:

Windows: In the NIC’s Advanced properties, increase Receive Buffers and Transmit Buffers to their maximum values.
Linux: Use ethtool -G eth0 rx 4096 tx 4096 to increase ring buffer sizes. Also check ethtool -C eth0 for interrupt coalescing settings.

10G Ethernet—Additional Considerations

10GBASE-T adds extra complexity. At 10G, cable quality is critical: Cat 6A is required for runs longer than 55 m (Cat 6 tops out at 10G only up to 55 m). Even with perfect cable, 10GbE NICs run significantly hotter than 2.5G or 1G adapters—heat can cause throttling. Ensure the NIC has airflow and check its temperature with your system monitoring software. SFP+ fiber adapters avoid these cable and heat issues entirely and are preferred in prosumer and business installs.

Quick Diagnostic Checklist

Both ends (NIC + switch/router port) list 2.5G in their spec sheets
Cable is Cat 5e or better, in good condition, under 100 m
NIC driver is the latest version from the manufacturer’s site (not Windows Update)
Intel I225-V boards have the NVM firmware updated
Router/switch firmware is current
Speed & Duplex setting in Device Manager or ethtool confirms 2.5G
No intermediate Gigabit-only switch in the path

If you’ve checked every item above and are still stuck at 1 Gbps, the most likely culprit is a chip revision or hardware defect. For Intel I225-V, check whether your board has revision B3 (the fixed version) or an earlier silicon revision—some early-production boards were permanently limited and required a BIOS or NVM workaround from the motherboard vendor. For more on getting the most out of your wired connection, see our comparison of Ethernet vs WiFi speed and our guide to link aggregation for home networks.