Data connection slow, dropping, or unreliable
A data point links but is slow, drops out, or negotiates a low speed — pointing at cabling quality, a marginal termination, interference, or the run length, rather than a hard break.
Safety first
Extra-low-voltage. Keep data separated from mains to limit interference and for safety.
Isolate, lock out / tag out, and prove dead before working unless a live test is specifically required, authorised, and carried out under proper supervision. Always follow local regulations, your site procedures, and the equipment manufacturer's documentation.
Apprentice mode
Full walk-through — the why, what readings mean, mistakes & safety.
Likely causes
Ranked from most to least likely.
- 1
Marginal termination / patch lead
Most likelyA barely-working termination or a worn patch lead links but performs poorly.
- 2
Cable run quality / length / damage
#2A poor, long, or damaged run causes errors and renegotiation to a lower speed.
- 3
Interference (running beside mains/noise sources)
#3Data run too close to mains/noise causes errors and drops.
- 4
Auto-negotiation / duplex mismatch
Least likelyA speed/duplex mismatch (config) causes errors and poor throughput.
Reports are saved on this device to reflect what you actually find.
Testing sequence
Work through one test at a time. Expected reading and what each result means.
On the tools? Job Mode shows one test at a time with thumb-sized buttons — your place and readings carry straight over.
Enter Job ModeSwap the patch lead(s) and note the negotiated link speed before/after.
Full expected link speed with good leads.
It was the lead — done.
Still poor — test the run and check separation/config.
View all expected readings at once
Fault-finding flowchart
The same logic as a decision tree.
- 1start
Data slow/intermittent
→ step 2 - 2decision
Does swapping the patch lead restore full speed?
Yes→ step 3No→ step 4 - 3result
It was the lead — done.
- 4decision
Does the run test good with proper separation?
Yes→ step 5No→ step 6 - 5result
Run good — check switch-port speed/duplex config.
- 6result
Marginal run / poor separation — rectify cabling/routing.
Common mistakes apprentices make
- Only checking for a link, not the actual speed/errors.
- Running data hard against mains and getting interference.
- Ignoring a marginal termination that 'works'.
- Overlooking a duplex/speed mismatch in config.
When to stop & escalate
Performance/certification and switch config sit between the cabling installer and the network team — share the test results so it's resolved at the right layer.
If you're past your competence, authorisation, or the safe limits of the job — stop and hand it on. There's no fault worth getting hurt over.
Was this guide helpful?
Related faults
Data outlet has no link / no network
A device plugged into a data outlet gets no link or no network, while others work — pointing at the patch lead, the outlet termination, the cable run, or the patch panel/switch port.
Data cabling run fails certification / wiremap fault
A structured cabling run fails a tester (wiremap fault, open, short, split pair, or excessive length) — so it won't reliably carry the network even if a link sometimes appears.
PoE device (camera/AP/phone) not powering up
A Power-over-Ethernet device (IP camera, wireless AP, VoIP phone) won't power on over its data cable — pointing at the PoE source, the budget, the cable, or the device's PoE class.