Troubleshooting Common Issues with Network Cables: A Practical Guide for South African Makers & Technicians

Overview: Why Network Cable Problems Happen

Network cable faults are a leading cause of slow or intermittent connectivity in labs, classrooms, and small offices. This guide to troubleshooting common issues with network cables covers the most frequent failures - physical damage, incorrect termination, wiring mismatches, crosstalk, length and attenuation limits, and power-over-Ethernet (PoE) problems. We'll show hands-on checks, test procedures, and repair tips using tools and parts readily available from Communica in South Africa.

Quick tools checklist

• Cable tester (basic continuity and pair map) or advanced tester with length and wiremap.
• Digital multimeter for continuity and simple DC checks.
• Crimp tool and RJ45 plugs (RJ45 RJ-45) and punch-down tool for patch panels.
• Wire stripper, scissors, and a good pair of cutters.
• Spare patch cables, a small spool of Cat5e/Cat6, and endpoint devices (switch, NIC).

Common symptoms

• Link light not lit on switch or NIC.
• Slow throughput (e.g., 100 Mbps instead of 1 Gbps).
• Intermittent drops or packet loss under load.
• Devices receive no PoE power, or PoE works intermittently.

Standards & cable categories at a glance

Understanding cable categories and connector pinouts helps narrow faults quickly. The table below summarises common cable types you'll encounter.

RJ45 pinouts (reference)

The two most common terminations are T568A and T568B. Many installers use T568B for consistency; ensure both ends of a patch cable use the same scheme.

T568B pinout (left-to-right, clip down): 1 Orange/white, 2 Orange, 3 Green/white, 4 Blue, 5 Blue/white, 6 Green, 7 Brown/white, 8 Brown

First checks: quick isolation steps

Start simple and rule out obvious faults quickly before using test equipment.

• Swap the suspect patch cable with a known-good cable. If problem clears, cable is at fault.
• Test the same port and device with a different port or different NIC to exclude device faults.
• Check link LEDs on both ends. No LED often means no continuity, broken pairs, or bad termination.
• Inspect connectors and cable jacket for kinks, cuts, or crushed sections - physical damage is common in workshops and teach labs.

Use of the cable tester

A basic 8-wire cable tester verifies continuity and pair order. Advanced testers show pair length, split pairs, and return loss. Run a wiremap test first; it pinpoints opens, shorts, reversed pairs, and split pairs.

If you find a wiremap fault, re-terminate the plug or punch-down at the patch panel and retest. Keep spare RJ45 plugs and a crimp tool in your kit for quick repairs. For tips on proper handling and longevity, see best practices for using CAB02PR22MSCR network cables.

Deeper faults and how to fix them

Broken pairs and split pairs

Split pairs occur when wires from different pairs are used together, causing crosstalk and intermittent errors under load. Use the wiremap on a tester to identify split pairs; reterminate using the correct T568A or T568B order.

Attenuation and length issues

Ethernet over twisted pair is distance-limited: 100 metres is the practical maximum for structured cabling for 1 Gbps. If you suspect length/attenuation issues (poor signal over long runs), measure length with a tester or replace with a higher-category cable (Cat6a) or use a switch to break the run.

Shielding and ground loops (STP/FTP)

In electrically noisy or industrial environments, shielded cable can reduce interference. Ensure shield is terminated at the connector or panel per installer guidance. Improper grounding can cause hum or link instability.

PoE-specific checks

If PoE devices don't power up: confirm the switch or injector supports the required PoE class, check pair continuity (PoE uses pairs for power delivery), and inspect for overheating or high resistance in connectors. Some long or low-quality cables increase voltage drop; for PoE++ loads, use Cat6a and short runs where possible.

Practical examples and wiring diagrams

Example 1: Intermittent drops when transferring large files. Tester shows split pairs. Solution: Re-crimp both ends using T568B and retest - problem resolved.

Example 2: PoE camera not powering. Multimeter shows voltage at switch is present but not at device. Tester shows high resistance on pair 4/5. Solution: Replace damaged patch lead and verify PoE class on the injector.

Simple ASCII: straight-through (both ends T568B)
RJ45 end A: 1 2 3 4 5 6 7 8
RJ45 end B: 1 2 3 4 5 6 7 8
(Crossover would swap pairs 1/2 with 3/6; rarely used today)

Troubleshooting matrix: symptoms to likely causes

Local procurement and practical tips

Communica stocks patch cords, bulk cable, RJ45 plugs, and a selection of testers and crimp tools suitable for hobbyist, education, and industrial use. For campus or workshop installs, buy extra metres and spare plugs - re-terminating on-site is quick and cost-effective. For VAT invoicing and procurement, request an account quote for larger orders and check branch trading hours for Samrand and Cape Town pickup options.

When to escalate

If advanced testing shows poor return loss or near-end crosstalk outside acceptable ranges, or if multiple cables in a run fail, consider a certified installer or a cabling certifier. For mission-critical networks, documentation and labelling of patch panels and runs reduce future troubleshooting time.

Sources

• Ethernet cable wiring and color codes guide - Cable Matters
• IEEE 802.3 Ethernet standards overview - IEEE
• Ethernet Alliance: practical resources for cabling and PoE
• Communica - Connectors, wire & cable collection
• Communica - Branches & trading hours (Samrand, Pretoria, Cape Town)

Prices and lead times mentioned are estimates for South Africa (ZAR) and may vary by supplier and stock availability. For large or specialised orders, verify availability and request an invoice or quote through Communica's branch or account services. For where to buy locally, see where-to-buy-cab02pr22mscr-network-cables-in-south-africa.