Symptoms
A gigabit-capable router negotiates only Fast Ethernet on the ONT link after several hours.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: A gigabit-capable router negotiates only Fast Ethernet on the ONT link after several hours.
- Comparison to run: Compare negotiated port speed at both ends while internet access still works.
- Pass condition: WAN link remains at its supported rate after multiple connection cycles.
Why It Happens
A local Wi-Fi icon and a registered optical link are different observations. First determine whether the interruption begins at optical registration, the Ethernet handoff, routing or the application using the connection.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Damaged or poorly terminated Ethernet pair — investigate this first only if the local state or controlled comparison supports it.
- Auto-negotiation fault — a second layer that may survive a simple restart and requires a targeted check.
- Power-save behavior in one port — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Do not force 1 Gbps when the link is unstable; preserve original port settings. Fiber access is a chain: the optical terminal, WAN negotiation, routing and DNS can fail independently. A green Wi-Fi light proves only the local radio is active, not that the provider link is usable. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Compare negotiated port speed at both ends while internet access still works. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Compare negotiated port speed at both ends while internet access still works. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Replace the ONT-to-router cable with a known good certified cable. | This can expose or rule out damaged or poorly terminated ethernet pair without changing several settings together. |
| Inspect the deeper layer | Compare port error counters and speed renegotiation timestamps. | Use the evidence to separate auto-negotiation fault from power-save behavior in one port; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether auto-negotiation fault is consistent with the evidence. If not, investigate power-save behavior in one port rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. A gigabit-capable router negotiates only Fast Ethernet on the ONT link after several hours. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare negotiated port speed at both ends while internet access still works. Do not erase logs or reset the device yet. Replace the ONT-to-router cable with a known good certified cable. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Connect directly to the rated ONT port rather than an old intermediate switch. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. WAN link remains at its supported rate after multiple connection cycles. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider damaged or poorly terminated ethernet pair, auto-negotiation fault and power-save behavior in one port separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare negotiated port speed at both ends while internet access still works. Compare port error counters and speed renegotiation timestamps. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Ask provider to test ONT Ethernet port and router vendor to review WAN port firmware. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. WAN link remains at its supported rate after multiple connection cycles. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating damaged or poorly terminated ethernet pair as certain before running the comparison: Compare negotiated port speed at both ends while internet access still works.
- Trying several changes at once, such as modifying auto-negotiation fault and power-save behavior in one port simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Do not force 1 Gbps when the link is unstable; preserve original port settings.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
WAN link remains at its supported rate after multiple connection cycles.
- Repeat the original failing action under equivalent conditions: A gigabit-capable router negotiates only Fast Ethernet on the ONT link after several hours.
- Run the control again: Compare negotiated port speed at both ends while internet access still works.
- Check the positive pass condition: WAN link remains at its supported rate after multiple connection cycles.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Compare port error counters and speed renegotiation timestamps. Ask provider to test ONT Ethernet port and router vendor to review WAN port firmware.
For an ISP escalation, provide the fiber link light state, WAN status, time of failure, and results from one wired client, without sharing passwords or public administrative addresses.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Compare negotiated port speed at both ends while internet access still works.
- Preserve the corrected behavior: WAN link remains at its supported rate after multiple connection cycles.
- Record ONT and gateway firmware versions, cabling positions and WAN status during a healthy period; keep the provider support reference for line-level faults.
- Review configuration or hardware changes that could reintroduce damaged or poorly terminated ethernet pair.
Frequently Asked Questions
Does this symptom prove damaged or poorly terminated ethernet pair?
No. Start with the controlled comparison: Compare negotiated port speed at both ends while internet access still works. Only treat damaged or poorly terminated ethernet pair as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Compare port error counters and speed renegotiation timestamps. That helps determine whether auto-negotiation fault or power-save behavior in one port fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: WAN link remains at its supported rate after multiple connection cycles. Keep a record of the working state for future troubleshooting.