If your gigabit Internet connection repeatedly tops out near 90–95 Mbps, check the Ethernet link speed before blaming the ISP. A 100 Mbps link usually points to the local path: a damaged cable pair, poor termination, Fast Ethernet port, dock, USB adapter, or network-interface setting. Do not start by buying Cat7 cable or forcing 1 Gbps in Windows. First record the negotiated link, connect the computer directly to a known gigabit port with a short, known-good Cat5e or Cat6 patch cord, and then restore one segment at a time. If the link already shows 1 Gbps, move the investigation upstream to the router WAN port, Internet plan, traffic, and test conditions.
- Link speed and an Internet speed-test result measure different parts of the path.
- 1000BASE-T uses all four twisted pairs; 100BASE-TX uses two, so a pair fault can leave a working but slower link.
- A short, known-good direct connection is the fastest way to separate room cabling from endpoint and router problems.
- Every device in the path matters, including WAN and LAN ports, switches, docks, wall jacks, and USB Ethernet adapters.
- If the local link is already 1 Gbps, stop replacing LAN cable and test the WAN side and actual Internet conditions.
1. Separate a 100 Mbps Ethernet link from a 100 Mbps speed test
The first decision prevents most wasted troubleshooting. The link speed is the rate negotiated between a network adapter and the device directly connected to it. That device may be a router, switch, dock, or media converter. An Internet speed test measures application traffic across that local link, the router, the ISP network, and a remote test server. The two numbers are related, but they are not interchangeable.
On Windows, open PowerShell and run Get-NetAdapter. Microsoft documents this command as a way to display basic adapter properties; the default table includes the active adapter and its link speed. You can also open Settings, inspect the Ethernet connection, and look for “Link speed (Receive/Transmit).” Router and managed-switch interfaces often report the negotiated rate for each port as well.
| Observed result | What it tells you | Where to look first |
|---|---|---|
| Link: 100 Mbps; test: roughly 90–95 Mbps | The test is close to the practical ceiling of a 100 Mbps Ethernet segment. | Patch cords, connectors, wall jacks, LAN port, switch, dock, and NIC. |
| Link: 1 Gbps; test: roughly 90–100 Mbps | The computer’s immediate Ethernet segment negotiated at gigabit speed, but another bottleneck remains. | Router WAN link, service tier, traffic shaping, router throughput, and test conditions. |
| Link alternates between 100 Mbps and 1 Gbps | An intermittent contact, marginal cable, unstable port, or adapter issue is plausible. | Both plugs, cable strain, terminations, port changes, and adapter logs. |
| Link: 1 Gbps; test: several hundred Mbps | The local gigabit link is working. Internet performance needs separate evaluation. | Test server, time of day, other traffic, router load, and ISP path. |
2. Why one cable-pair fault can produce a 100 Mbps link
A typical balanced copper Ethernet cable contains eight conductors arranged as four twisted pairs. 100BASE-TX transmits over two pairs. 1000BASE-T transmits over all four pairs. This difference explains a common symptom: the connection still works, but it negotiates at 100 Mbps because one of the pairs required for gigabit operation is open, miswired, poorly seated, or too impaired to support the faster mode.
The failure can be subtle. Web pages load, video calls connect, and the port LEDs remain on. A user may conclude that the ISP has throttled the service. Yet if the operating system also reports a 100 Mbps link, the more direct explanation is somewhere between the adapter and its immediate link partner.
Common causes include a poorly crimped modular plug, a conductor not fully seated in a keystone jack, a cable crushed under furniture, an overly sharp bend, damaged contacts, or an old installation that deliberately split four-pair cable into two two-pair 10/100 links. The category printed on the jacket cannot compensate for a bad termination. A Cat6 cable with one failed pair cannot deliver a healthy four-pair gigabit link.
Do not reject Cat5e simply because its category number is lower. Properly made Category 5e cabling is a standard choice for 1000BASE-T. For diagnosis, a verified Cat5e patch cord is more useful than an unverified cable marketed as Cat7. The objective is to establish a known-good four-pair path, not to buy the largest category number.
3. Use a direct connection to isolate the faulty segment
Troubleshooting should remove variables, not add products. Obtain a short, factory-terminated Cat5e or Cat6 patch cord that is known to work at gigabit speed. Connect the computer directly to a confirmed gigabit LAN port on the router or switch. This single test bypasses the room outlet, horizontal cable, patch panel, couplers, extension leads, and intermediate switches.
If the direct link immediately becomes 1 Gbps, the computer and the tested router port can negotiate gigabit speed. The fault is likely in something you removed. Reconnect the path in stages: first the original patch cord, then the wall run, then any switch or coupler. Check the link after each change.
If the direct connection remains at 100 Mbps, move the same known-good cord to another confirmed gigabit port. Then test another gigabit-capable computer or adapter on that port. A one-variable-at-a-time method creates evidence. Replacing the cable, port, adapter, driver, and settings together may restore service, but it does not reveal which change mattered.
For intermittent faults, note when the link changes and what was physically moved. A connection that shifts rates when the plug is touched suggests a contact or strain problem. A connection that fails only through one dock suggests the dock or its uplink. Avoid repeatedly flexing a live connector to “prove” a fault; replace or reterminate it properly. In commercial buildings, do not dismantle shared telecommunications rooms or ISP-owned equipment without authorization.
4. Check every port and device in the Ethernet path
Marketing phrases such as “gigabit Wi-Fi” do not prove that every wired port supports 1 Gbps. A router has a WAN port toward the modem or optical network terminal and LAN ports toward local devices. Either side can be limited to Fast Ethernet or can negotiate down because of its cable. An otherwise modern Wi-Fi router with a 100 Mbps WAN port cannot pass a gigabit Internet service to its clients.
Intermediate hardware is easy to overlook. A 10/100 switch, older powerline adapter, inexpensive USB Ethernet dongle, dock, or wall-mounted extender can set the limit for the entire path. Verify each model’s wired-port specification. “USB 3” on a dock does not automatically mean its Ethernet controller is gigabit-capable, and a gigabit-capable controller can still negotiate at 100 Mbps through a bad cable.
| Segment | Evidence to collect | Typical 100 Mbps bottleneck | Isolation test |
|---|---|---|---|
| ISP device to router WAN | WAN port status in the router interface | 100 Mbps WAN port or a two-pair/damaged uplink cable | Replace only the WAN patch cord and recheck the WAN link |
| Router LAN to computer | OS link speed and router or switch port status | Fast Ethernet port, damaged cord, or poor plug contact | Use a different confirmed gigabit LAN port |
| Switch, dock, or USB adapter | Exact model specification and negotiated rate | 10/100 hardware or unstable adapter | Remove the device and connect directly |
| Wall jack and installed cable | Eight-conductor wire map and both terminations | Open or split pair, miswire, damaged cable, or bad jack | Bypass the installed run with a known-good cord |
| Computer NIC | Adapter model, driver, link setting, and test on another port | 10/100-only NIC, driver issue, or physical port damage | Compare with another gigabit-capable device |
A basic continuity tester can identify opens, shorts, and obvious pin-order faults. It does not certify insertion loss, return loss, crosstalk, or the complete transmission performance of an installed Category link. If multiple workplace outlets fail, or the cabling is being accepted from a contractor, use the specified field-certification test and link model rather than treating a simple wire map as final proof.
5. Leave gigabit speed and duplex on auto-negotiation
For ordinary 1000BASE-T connections, auto-negotiation should be the starting setting on both ends. Intel’s official adapter guidance recommends Auto Negotiation for gigabit connections and warns that manually forced settings must match the link partner. Some drivers do not even offer a “1.0 Gbps Full Duplex” selection; that omission alone does not indicate a faulty adapter.
Forcing a software setting cannot reconnect an open conductor or repair a damaged jack. It may prevent the link from coming up or create a mismatch that complicates diagnosis. Keep the original setting documented. Test a known-good cable and port first. Change advanced adapter properties only when the adapter manufacturer’s procedure calls for it or when a network administrator has a specific interoperability reason.
A driver update also should not be the first response to a location-specific fault. If the same computer negotiates at 1 Gbps through the direct test, its hardware and driver have demonstrated that capability. Focus on the original cable path. If that computer alone stays at 100 Mbps through every known-good cable and port, then verify its NIC specification, driver package, dock, power-management behavior, and firmware using the manufacturer’s documentation.
6. When the link is 1 Gbps but the Internet is still slow
A 1 Gbps link proves only that the computer and its immediate link partner established a gigabit connection. It does not prove that the router’s WAN link is gigabit, that the service is provisioned correctly, or that the router can route and inspect traffic at the subscribed rate.
Open the router interface and check both the WAN link and the specific LAN port. Confirm the service tier on the current bill or provider portal. If practical and permitted by the ISP, compare the result with one wired computer connected directly to the provider device. Some services require a particular authentication method or VLAN, so do not assume direct connection will always obtain service.
For a useful speed test, disable Wi-Fi on the test computer, disconnect VPN software, pause cloud synchronization and large downloads, and reduce other network traffic. Select more than one reputable nearby test server and repeat the test at different times. Also consider the computer’s CPU load, security software, browser, router features such as traffic inspection or QoS, and the provider path.
A 1 Gbps Ethernet rate is not a promise of exactly 1,000 Mbps of application data from every public server. Frames, higher-layer protocols, device processing, and network congestion consume capacity or reduce throughput. Still, a repeatable plateau near the low 90s is a strong reason to recheck for a 100 Mbps link somewhere, especially the router WAN side.
- Confirm that the computer’s local Ethernet link is 1 Gbps.
- Confirm the router’s WAN link and the tested LAN port separately.
- Pause VPN, backups, downloads, streaming, and other heavy traffic.
- Run several wired tests against more than one nearby server.
- If allowed, compare through another router or directly at the ISP device.
- Save dates, times, server names, topology, and results before contacting the ISP.
7. Match the symptom to the next test
| Symptom | Most useful hypothesis | Next test |
|---|---|---|
| Only one room links at 100 Mbps | That outlet, installed cable, patch-panel termination, or room patch cord | Bypass the room run, then inspect both ends and test the link |
| Only one patch cord causes 100 Mbps | Plug contact, internal break, or excessive mechanical damage | Replace the cord; reterminate field-made cords correctly |
| Only one router or switch port causes it | Port specification, contamination, configuration, or damage | Move the same device and cord to another confirmed gigabit port |
| Only one computer causes it | NIC, dock, USB adapter, driver, or port damage | Use another gigabit device on the same cable and port |
| All local links show 1 Gbps, Internet stays near 100 Mbps | WAN link, service provisioning, router throughput, or policy | Check WAN status and perform a controlled wired comparison |
| Performance changes sharply by time of day | Shared traffic, provider congestion, or test-server path | Repeat the same controlled test and document the pattern |
This table ranks useful next tests; it does not prove a cause. “Only one room is slow” raises suspicion about that run, but comparison is valid only if the same computer and known-good patch cord work when connected directly. Conversely, if every endpoint has a gigabit local link and every Internet test shows the same limit, inspect the common WAN path before reopening every wall jack.
8. Frequently asked questions
Why does my Cat6 cable connect at only 100 Mbps?
Category describes a component’s intended transmission performance; it does not prove that the current channel is intact. One unseated contact, damaged pair, poor termination, 10/100 port, or Fast Ethernet adapter can reduce the negotiated link to 100 Mbps.
Does a 95 Mbps speed test prove my Ethernet link is 100 Mbps?
It is a common pattern, but do not diagnose from throughput alone. Check the operating system’s link speed and the router or switch port. If a 100 Mbps link and repeated low-90s tests appear together, trace the local or WAN segment that negotiated at 100 Mbps.
Should a gigabit plan always test at exactly 1,000 Mbps?
No. Protocol overhead, router capacity, device load, server choice, and network conditions affect application throughput. Provider promises and minimum-speed policies also differ by country and plan. Use the service agreement for contractual expectations.
Can a cheap cable tester confirm gigabit performance?
A continuity or wire-map tester is useful for pin faults, but it does not certify the full high-frequency performance of the installed link. For commercial acceptance, use the required permanent-link or channel certification method and the correct test limit.
Why does rebooting restore 1 Gbps only temporarily?
The reboot or reconnection triggers a fresh negotiation. If the link later falls back, investigate marginal contacts, cable movement, port stability, power, adapter behavior, and device logs. Rebooting is evidence of an intermittent condition, not a durable repair.
9. Conclusion: check the negotiated link before replacing equipment
When gigabit Internet appears capped at 100 Mbps, the fastest solution is disciplined isolation. Confirm the computer’s link speed, bypass the installed path with a known-good cord, change one variable at a time, and restore each segment until the fault returns. If the local link is 100 Mbps, inspect the four-pair path and both endpoints. If it is already 1 Gbps, move upstream to the WAN link, router performance, service provisioning, and controlled speed testing.
Do not buy a higher cable category merely because a replacement cable happened to work. Do not force 1 Gbps to conceal a physical fault. Identify the failed segment first; then choose the proportionate repair: replace a patch cord, reterminate a jack, change a port or adapter, certify an installed link, or escalate a documented WAN issue to the provider.
Read next
Sources
- Microsoft Learn — Get-NetAdapter
- Intel — Ethernet Adapter Limited at 100 Mbps
- Intel Ethernet Adapters and Devices User Guide — Setting Speed and Duplex
- IEEE Standards Association — IEEE 802.3 Ethernet
- Cisco — Connector and Cable Specifications
Korean version: 한국어로 읽기
