low-voltage troubleshooting
No data link / port won't connect
Common symptoms: no link light; ethernet no connection; port won't negotiate; no network on jack; link down
Stop and call a pro if:
- confirm the jack is data cabling only — stop if line voltage may be cross-connected
- never look into a live fiber end face or fiber port (invisible laser radiation)
- do not disturb fire-alarm initiating circuits while tracing cabling
Step-by-step diagnostic flow
Step 1
Is this strictly data cabling (no suspected line-voltage cross-contact) and, if any fiber is involved, will you avoid looking into any port or end face?
Invisible fiber laser light can damage your eyes; line voltage on a data jack is a shock hazard.
Step 2
Is this run copper (RJ45) or fiber?
Copper and fiber fail differently — copper on wiremap/pairs, fiber on polarity/cleanliness.
Step 3
Are both ends actually connected — device patched in at the jack, and the run patched through to an active switch port at the closet?
A surprising share of 'dead jacks' are simply not cross-connected at the patch panel.
Step 4
Is the switch port administratively up, and does the device link on a known-good port/cable?
Managed switch ports can be shut down or stuck on a forced speed/duplex. Swap one variable at a time.
Step 5
Are the fiber connectors clean, and is Tx/Rx polarity correct (your Tx into their Rx)? Does swapping/flipping the strands at one end bring up link?
Most fiber 'no link' issues are a dirty end face or reversed Tx/Rx. Use proper inspection tools — never the naked eye on a live port.
Possible outcomes
Stop — resolve the safety concern first
high confidencePossible line-voltage cross-contact or live fiber must be handled safely before tracing or terminating.
- If line voltage may be present, call a licensed electrician
- Never inspect a powered fiber port or end face
- Leave fire-alarm circuits undisturbed
Run wasn't cross-connected — now linked
high confidenceThe jack was live but not patched through to an active switch port; completing the cross-connect brought up link.
- Confirm the device gets an IP / network access
- Label the patch-panel-to-port mapping
Switch port was disabled or mis-configured
high confidenceAn administratively-down port or a forced speed/duplex mismatch prevents link; correcting it restored the connection.
- Leave the port set to auto-negotiate unless there's a reason not to
- Confirm the port is in the right VLAN for the device
- Switch model and port number
- Any required VLAN/speed settings
Original switch port or patch cord is suspect
high confidenceLinking on a known-good port/cable isolates the fault to the original port or patch cord.
- Replace the patch cord or move to a known-good port
- If a fixed port repeatedly fails, have the switch checked
Likely cabling fault — verify wiremap
medium confidenceNo link on a known-good port/cable with both ends patched points to an open, short, reversed, or split pair in the permanent link.
- Run a wiremap/continuity test on the permanent link
- Re-terminate or repair any open/short/split pair found
- Re-test after repair
- Wiremap/continuity result
- Cable category and approximate length
- Whether other nearby jacks work
Fiber polarity/cleanliness corrected — linked
high confidenceReversed Tx/Rx or a contaminated end face is the most common fiber no-link cause; correcting it restored link.
- Confirm stable link and acceptable light levels if you have a meter
- Cap unused connectors to keep end faces clean
Fiber still down — escalate to a fiber tech
low confidenceClean, correctly-polarized fiber that won't link may have excessive loss, a broken strand, or an SFP/optic mismatch needing an OTDR/power-meter and proper tooling.
- Stop visually inspecting powered ports
- Have a fiber tech measure loss and verify the optics match
- Fiber type (SM/MM) and connector type
- SFP/optic models at each end
- Approximate run length and any splice points
Pro launch updates
Get notified when Pro launches, plus a monthly code-change digest. Email only — no account required.