FIND A GUIDE
A better next check
starts here.
Search symptoms, test methods and wiring faults.
All 9 guides and references.
- TroubleshootingAll eight lights pass. Why is Ethernet still at 100 Mb/s?
Separate a wiring fault from a 100 Mb/s port, a damaged pair or a configuration problem with a controlled Ethernet troubleshooting sequence.
- Testers & toolsVerification, qualification or certification?
Understand what each level of network cable testing proves, which tool you need and what should appear in a cabling handover report.
- PoE & camerasPoE voltage is present. Why does the camera keep rebooting?
Check a PoE camera that restarts when infrared lighting or PTZ movement begins, using port budgets, known-good leads and loaded measurements.
- Cabling & tracingHow to trace an Ethernet cable at a switch
Choose a tracing method for disconnected, active and PoE Ethernet links, and understand why shielding and switch termination change the result.
- Testers & toolsNOYAFA NF-8209S: check the capability, not just the name
A pre-purchase and pre-use checklist for NOYAFA NF-8209S cable testers: model revisions, split-pair detection, PoE load claims and test-port restrictions.
- Cabling & tracingT568A vs T568B: what changes and what does not
Compare T568A and T568B pin assignments, physical pair membership and termination checks using an explicit numbered diagram.
- TroubleshootingCable length and distance-to-fault: what a tester can estimate
Understand electrical distance, NVP, reference points and far-end conditions before using a cable tester’s length or distance-to-fault reading.
- PoE & camerasPoE identification vs loaded measurement: what each result means
Distinguish PoE detection, advertised power, inline observation and applied-load testing before diagnosing a camera or switch.
- Fault referenceEthernet cable fault library
Seven illustrated fault types with symptoms, test limits and next checks.
Try a broader term such as PoE, wiremap, tracing or length. You can also browse the fault library or reset the search.
Open the fault library →