The clue: link speed, not internet speed
The wired connection was stable, with no drops. That detail made the problem hard to spot. A flaky link announces itself, but a link that has quietly settled at a lower speed doesn't.
Rozario checked the negotiated rate in Windows under Settings, then Network & internet, then Ethernet. He found it reporting 100 Mbps instead of 1,000 Mbps. This figure is the speed the PC's network adapter and the device at the other end of the cable agreed on. It is not an internet speed test. A 100 Mbps link will cap a 500 Mbps plan, but a 1 Gbps link doesn't guarantee you'll get 500 Mbps in every app.
One caveat on labels. Rozario's account refers to an "Aggregated link speed" field. How Geek's report of a similar case describes "Aggregated link speed (Receive/Transmit)" showing 100/100 (Mbps) instead of 1000/1000. Microsoft's own documentation confirms that Ethernet status lives under Network & internet settings. Exact wording and layout can differ across Windows builds, so look for the link speed or speed fields on the Ethernet page.
Why a damaged cable can still "work"
Rozario's explanation holds up. Twisted-pair Ethernet cable has four pairs of wires. Gigabit Ethernet requires all four twisted pairs in the cable, while a 100 Mbps connection can operate using only two pairs. That's why if one pair is damaged, incorrectly terminated or not connected, the devices may still establish a link but negotiate it at 100 Mbps instead of 1 Gbps.
The cable doesn't have to fail outright. It only has to lose something Gigabit needs but Fast Ethernet doesn't.
Several things can cause this:
- A broken conductor inside the cable.
- A poor crimp or loose contact in the RJ45 connector.
- Sharp bends or repeated flexing. Broken conductors, loose connectors, sharp bends, or poor termination can make a connection fall back to 100 Mbps.
- In-wall runs have extra failure points. A poorly punched-down wall jack, damaged patch panel port, or low-quality coupler may interrupt one twisted pair while the connection stays active at 100 Mbps.
Rozario saw no visible damage and doesn't know how the cable failed. Treat the exact fault as unknown. Replacing the cable fixed it, which is strong circumstantial evidence. It isn't a lab diagnosis.
"But it's Cat6" doesn't settle it
Rozario remembered using a Cat6 cable. The category label describes what the cable is designed to do, not what condition it's in. A damaged Cat6 cable can still negotiate at only 100 Mbps.
The reverse also applies. Intel's cabling documentation for its Ethernet adapters says Fast Ethernet and Gigabit need category 5 or 6 cable. Gigabit isn't a "Cat6 only" feature. What matters is that all four pairs are intact and properly terminated.
A troubleshooting sequence that doesn't cost a router
- Read the negotiated link speed. If a gigabit-capable PC and router show 100 Mbps, something in the physical path or the adapter settings is limiting the link.
- Try a known-good cable. Microsoft's Ethernet guidance says that if another cable works, the first cable might be the problem. Rozario's swap to a spare Cat6 cable took the link back to 1,000 Mbps.
- Reseat both ends and try other ports. Microsoft advises making sure the cable is firmly seated at both the router and the PC. It also says to use a LAN port on the router, not the Internet/WAN port. Rozario tried different ports on both the router and the motherboard first, and nothing changed. That made the cable the next suspect.
- Check the adapter's speed and duplex setting. Open Device Manager, expand Network adapters, open the adapter's properties and go to the Advanced tab. Look for Speed & Duplex. If it's forced to 100 Mbps Full Duplex rather than Auto Negotiation, that could explain the symptom. A manually forced setting such as 100 Mbps Full Duplex can prevent the adapter from negotiating Gigabit Ethernet. Property names and options vary by adapter and driver, so what you see may differ.
- Test another device or adapter. Microsoft suggests trying a second PC on the same network to narrow down whether the fault is the first PC or the network. If the problem persists, it also describes reinstalling the Ethernet driver. Have a backup driver on hand before you do that.
Don't blame the cable by default
Cables are the cheapest thing to swap, so they make a good first test. They aren't the only possible cause. Port faults count too. A failing Ethernet port may still provide a connection but lose one or more signal pairs, causing automatic fallback to 100 Mbps. The same applies to the 10/100-only hardware sometimes hiding in older gear, such as an unmanaged switch, wall plate or inline adapter.
There's a dissenting view too. One troubleshooting guide argues that people over-focus on cables when a port-level or configuration cause is more likely. A hard fault should show up as exactly 100 Mbps, and a marginal one can behave more erratically. A related WindowsForum report describes a 2.5GbE link that kept dropping to gigabit and sometimes fell to 100 Mbps overnight. So a link that bounces between speeds points to a marginal run, a connector or a port. The sensible approach is to test one variable at a time.
On the router
Rozario's router was cleared mostly by elimination. His Wi-Fi devices reached plan speeds, and the cable swap restored gigabit. D-Link's DIR-882 specifications list Gigabit LAN ports, so the router was supposed to be capable of the speed. That alone doesn't rule out a bad port, which is why trying other ports mattered.
A practical caution applies to the cheap-cable fix. A cheap cable can be fine, but don't assume a new one is good. Plug it in and confirm the link reads 1,000 Mbps, or 2.5 Gbps on a faster setup.
The takeaway
If a wired PC lags behind your other devices on Wi-Fi, check the link speed before you shop for routers. A 100 Mbps reading on gigabit gear is a strong hint of a physical-layer problem. Start with a known-good cable, then work through ports, adapter settings and drivers. For Rozario, the fix was a spare cable from a drawer, and the router kept its job.