Network Cable Troubleshooting Guide for Engineers (South Africa)

Overview: Why a Systematic Approach Matters

Network cable issues cause a large share of connectivity problems on sites and in labs. This network cable troubleshooting guide for engineers lays out a reproducible workflow: visual inspection, simple continuity checks, structured testing with a tester or TDR, and verification under load. The aim is to get you from problem report to root cause and fix, with consideration for availability, lead times, and common brands stocked locally by Communica.

Common symptoms

• Intermittent link drops or flapping
• Slow throughput (100 Mbps vs expected 1 Gbps)
• No link / link LED off
• Packet errors, CRCs, or high retransmits
• Physical damage, water ingress or connector corrosion

Standards & basic expectations

Most Ethernet deployments use UTP category cables (Cat5e, Cat6, Cat6a) and RJ45 connectors. Expected baseline for performance testing:

Keep in mind environmental factors common in South African sites: temperature swings in non-climate-controlled rooms and occasional dust or humidity can affect connectors and patch panels. When procuring replacements, Communica stocks a broad range of cable categories, RJ45 jacks, keystones and patch panels-check branch stock if you need to replace urgently.

First-line checks: visual and simple tests

Visual inspection

Start with a quick walk-through: look for crushed runs (under carpet, through door frames), kinks, damaged outer sheath, discoloured connectors or loose strain relief. Confirm correct wiring at both ends (T568B or T568A). Mismatched termination can produce no link or half-duplex behaviour.

Simple continuity and pin map

A basic continuity tester or simple LED cable tester will tell you if each pair is connected and whether any pair is shorted or split. For RJ45 pin mapping use this reference (T568B shown):

1: Orange/White   2: Orange
3: Green/White    4: Blue
5: Blue/White     6: Green
7: Brown/White    8: Brown

If continuity is good but link fails, move to advanced testing below.

Advanced testing: network cable troubleshooting guide for engineers

Use a certified cable tester or Time Domain Reflectometer (TDR) when simple checks don't reveal the fault. Key measurements and what they reveal:

• Wiremap: opens, shorts, split pairs, miswires
• Length/Distance to fault: TDR shows the approximate metre point of impedance changes
• Near-end crosstalk (NEXT) and attenuation: indicates crosstalk or excessive loss affecting gigabit negotiation
• Return loss and delay skew: important for high-speed links (10G and PoE++)

Interpreting link speed and duplex problems

If devices negotiate at 100 Mbps instead of 1 Gbps, check for:

• Broken or poor pairs (Gigabit needs all 4 pairs)
• Mismatched cable category (Cat5 vs required Cat6) or excessive length/noise
• Auto-negotiation issues-force to 1 Gbps for a test only; don't leave forced settings in production

PoE troubleshooting

For PoE issues (device not powering or dropping power), measure voltage under load and check the switch's PoE budget. Use a PD tester or clamp meter. Note: PoE power is provided over pairs; damaged pairs or high resistance can reduce available power and cause brownouts on cameras or APs.

Example calculations

Estimate cable loss: attenuation is often specified in dB/100 m. For example, if Cat6 has ~2 dB loss at 100 MHz per 100 m, a 50 m run loses ~1 dB. Link margin and NEXT budgets determine if the run supports required speed. Use these quick checks rather than deep math for field triage.

Wiring diagram (patch to switch)

[Switch RJ45]---(patch cable)---[Patch Panel]---(permanent link)---[Wall Jack]---(patch)---[Client]

When replacing elements, swap patch cables first, then patch panel ports, then tester the permanent link. This narrows where the fault lives.

Troubleshooting checklist and best practices

1. Recreate the fault and record symptoms, time and device IDs.
2. Swap patch leads and change switch port to rule out client or switch faults.
3. Run a wiremap and length test; inspect connectors and strain relief.
4. Run NEXT/attenuation tests for marginal gigabit links with a certifier or advanced tester.
5. For intermittent faults, monitor link Flap counters and log events from switches.
6. Document repairs with port numbers, cable IDs and test reports (retain for warranty/QA).

Common field fixes

• Replace patch leads first-these fail most often.
• Re-terminate RJ45 connectors with correct pair ordering and correct tool.
• Use ferrite or reroute near high-power sources to reduce EMI.
• Replace damaged sections or move cable away from compressors, fluorescent ballasts or heavy machinery.

Sources

• Ethernet technologies and troubleshooting - Cisco
• Telecommunications Industry Association (TIA) - Cabling standards reference
• Fluke Networks - Cable testers, certifiers and field guides
• Communica product categories: Connectors, Wire & Cable