A useful diagnosis starts by reproducing the failure under controlled conditions. In this case, Video through a dock is fine but its gigabit Ethernet link negotiates at 100 Mbps. Keep the result of every test so a temporary workaround is not mistaken for a permanent repair.
Symptoms and scope
What you may see: Video through a dock is fine but its gigabit Ethernet link negotiates at 100 Mbps. Note the precise device model and whether the failure also occurs in firmware setup, in a second app, or on a second cable or port. That distinction determines which repair is reasonable.
- Original behavior: Video through a dock is fine but its gigabit Ethernet link negotiates at 100 Mbps.
- Comparison result: Compare link speed with a known-good CAT5e or better cable and a different switch port.
- Verification target: Dock maintains a stable negotiated 1 Gbps link on a gigabit network.
Why this happens
A USB-C connector can carry power, USB data and optional video paths, but device and cable capabilities vary. A dock working for one function does not prove that another path is supported. For this specific symptom, use the following diagnostic boundary: Check pair faults, Ethernet auto-negotiation and docking station link status.
Do not treat every warning in Event Viewer, firmware diagnostics or the device manager as the root cause. A useful event must line up with the failure time and change with a repeatable test.
Before making changes
Identify laptop, dock, cable and monitor exact models, not just USB-C connector appearance. Use the original rated power supply and disconnect unused peripherals during a controlled test.
Safety boundary: Actual internet speed may be slower than LAN link speed for unrelated reasons. Save a copy of current device settings and confirm a working path back before testing any repair.
Step-by-Step Troubleshooting
Begin with non-destructive comparisons. Open Advanced for device-specific diagnostics.
Confirm the exact failure
Start from the reported behavior: Video through a dock is fine but its gigabit Ethernet link negotiates at 100 Mbps. Write down whether it occurs every time, only on battery, after restart, after a cable change, or in one application. This baseline prevents a temporary workaround from being mistaken for a repair.
Run one safe comparison
Comparison: Compare link speed with a known-good CAT5e or better cable and a different switch port. Change only the stated variable. If the comparison succeeds, inspect what differs from the original setup before changing unrelated drivers or firmware.
Apply the relevant correction
Targeted action: Replace a faulty cable or dock network adapter and use approved LAN drivers. Keep the original setting or cable available. After each change, repeat the exact original failure once before testing a second hypothesis.
Retest and record the result
Pass condition: Dock maintains a stable negotiated 1 Gbps link on a gigabit network. Recheck after an ordinary restart or reconnect. If it fails, undo unhelpful test settings and retain the observed difference for deeper diagnosis.
Inspect the affected layer
Technical check: Check pair faults, Ethernet auto-negotiation and docking station link status. Capture exact device model, driver/firmware build, error timestamp and the state immediately before the transition.
Get-NetAdapter | Select-Object Name, Status, LinkSpeedCorrelate with the control
Repeat this controlled comparison: Compare link speed with a known-good CAT5e or better cable and a different switch port. Compare timestamps and specific device states, not just a generic warning. Separate a physical link loss from a software or policy failure when applicable.
Change one supported parameter
Controlled adjustment: Replace a faulty cable or dock network adapter and use approved LAN drivers. Where administrator or manufacturer approval is required, obtain it before changing the device. Avoid combining a firmware change, driver reinstall and cabling change into one test.
Validate under realistic conditions
Evidence of success: Dock maintains a stable negotiated 1 Gbps link on a gigabit network. Confirm stability under the original workload and after the state transition that triggered the issue. Keep logs free of passwords and recovery keys.
Interpret the test results
| Observation | Next decision |
|---|---|
| Original setup fails; comparison works | A pass in the control test narrows the cause; do not rebuild the entire computer when one cable or profile explains the difference. |
| Both setups show the issue | A failure in both paths points to a common dependency. Capture that evidence before replacing parts. |
| Behavior changes only after restart or reconnect | Check the device power state, re-enumeration and saved settings before replacing hardware. |
Common mistakes to avoid
- Assuming all USB-C cables support video and high power.
- Testing through multiple unknown adapters at once.
- Turning off platform security to allow an untrusted accessory.
- Actual internet speed may be slower than LAN link speed for unrelated reasons.
How to verify the fix
Return to the exact scenario that failed, not an easier substitute. Expected result: Dock maintains a stable negotiated 1 Gbps link on a gigabit network. Verify with a second run after reconnecting, waking from sleep or restarting when that transition was part of the issue.
Record the successful configuration and check the quality of the outcome as well as the error message. A device that merely appears in a list but cannot transfer a file, display an image or produce clean audio is not yet repaired.
Solution Checklist
If the problem continues
Restore the previously working setting if the attempted correction did not help. Investigate this next boundary: Check pair faults, Ethernet auto-negotiation and docking station link status. Compare the failed and successful cases side by side; include timestamps and product versions when contacting the manufacturer.
For persistent physical defects, unusual heat, electrical warnings or data loss, stop further experiments and arrange a qualified repair or recovery. Share only non-sensitive diagnostic evidence, never passwords, BitLocker recovery keys or complete personal files.
Prevent recurrence
Keep a record of the successful fix: Replace a faulty cable or dock network adapter and use approved LAN drivers. Retain documented firmware and driver versions, a known-good cable or test device, and backup copies when storage is involved. Recheck the same symptom after major updates rather than applying unrelated registry tweaks.