If gigabit-capable equipment unexpectedly connects at 100 Mbps, investigate the physical link and the capabilities at both ends. A lower negotiated rate can be a clue about a cable, termination, port or adapter. It is different from a television whose port was designed for 100 Mbps.
Record the old and current arrangement before replacing equipment. The most useful question is what changed between the previously working path and the present one.
Confirm the expectation is correct
Check the exact models and ports. A router can contain ports with different roles or capabilities, and a USB adapter’s advertised rate does not establish its host’s supported behavior. A specification for another generation is not a valid comparison.
Then read the negotiated rate where the equipment exposes it. A broadband speed test cannot establish the local link rate because it includes other constraints. Keep those two measurements separate.
Isolate the removable cable and port
A cable can appear connected while failing to support the expected link. Start with a known suitable lead on the same two endpoints. If the rate returns, retain the result and check ordinary operation before making additional changes.
If the lead substitution does not help, try a known working LAN port as a separate test. For a wall run, distinguish both patch leads from the fixed cable and its terminations. This sequence avoids replacing a router to solve a damaged connector.
- Verify that both endpoints and the specific ports support the intended rate.
- Read the actual negotiated link value.
- Substitute one known suitable cable while retaining the ports.
- Compare another supported port separately.
- Have a fixed run checked appropriately if the issue follows that path.
- Retest the original viewing symptom after the link issue is resolved.
Do not force a bigger number
Manual speed or duplex settings are not a general repair for negotiation trouble. The configuration must match the technology and both endpoints. Follow the manufacturer’s documented procedure rather than selecting the largest option in a menu.
An unexpected fallback deserves investigation, but it does not by itself prove why a programme stalled. You may find a physical limitation and a separate source-specific issue. Keep both observations instead of allowing the first discovered defect to explain everything.
| Result | Next interpretation |
|---|---|
| Known lead restores expected rate | Original lead or its connection is a strong suspect |
| Issue follows one wall route | Check fixed cabling and patching |
| Rate matches endpoint specification | Investigate another cause rather than treating design as failure |
Keep the repair evidence
Record the replacement segment and final rate. If the connection later falls back again, this makes the recurrence easier to compare. Note movement, power interruptions or equipment changes without assuming they caused it.
Once a stable expected link is restored, stop experimenting with negotiation settings. Use the actual viewing result to decide whether further network work is necessary.
Useful answers
Can one cable cause a lower negotiated speed?
Yes. A known suitable cable substitution is a useful isolation step, but ports and adapters must remain part of the investigation.
Does the lower rate mean the ISP reduced my plan?
No. Ethernet negotiation occurs on a local link. Your internet service and its measured throughput are separate questions.