The Quick Answer
When an ethernet connection fails, the instinct is to re-terminate both ends and hope for the best. That works sometimes, but it wastes time when the problem is not at the connector. A systematic approach, starting with the symptom you can observe and working backward to the root cause, gets you to the fix faster and prevents you from replacing things that were never broken.
This guide is organized by symptom. Find the problem you are seeing, follow the diagnostic steps, and you will land on the cause. If you want the condensed version, skip to the diagnostic flowchart at the bottom.
No Link Light
The port LED on the switch, router, or device is completely dark. No amber, no green, no blinking. The device does not detect that a cable is connected.
Step 1: Check both ends
Push the connector firmly into the jack at each end. Listen for the click. A connector that is not fully seated will not make contact with the jack pins. If the latch is broken, the connector can slide partway out under its own weight or from cable tension. A strain relief boot prevents latch damage, but if the latch is already broken, re-terminate with a new connector.
Step 2: Try a known-good cable
Swap in a cable you have already tested and confirmed working. If the known-good cable lights up the link, the original cable is the problem. If the known-good cable also fails, the problem is the port, not the cable.
Step 3: Test the port
Plug the known-good cable into a different port on the same switch. If it works on another port, the original port may be disabled (check the switch configuration), dead, or damaged. For wall jacks, the problem could be in the punch-down termination at the patch panel. Check both the wall plate and the patch panel end.
Step 4: Test the cable with a cable tester
Connect the cable to a cable tester and run a wire map test. The tester will show you exactly which pins are connected and which are not. An "open" on any pair means the conductor is not making contact at one or both ends. A "short" means two wires are touching. Both will prevent a link from being established.
Common causes
- Connector not fully seated in the jack (most common, easiest fix)
- One or more wires did not reach the contact blades during crimping
- Conductor broken inside the cable from a kink or crush point
- Wrong wire order (crossover when straight-through was needed, or vice versa)
- Port disabled in switch configuration or port hardware failure
Link Light On, But No Data
The port LED is lit (solid or blinking), but the device cannot reach the network. No IP address, no ping response, no internet.
Step 1: Check IP configuration
Before blaming the cable, verify the device has an IP address. A link light means the physical layer is working. If the device shows "no network" or a 169.254.x.x address, it is not getting DHCP. Try a static IP to rule out DHCP issues. This is a network configuration problem, not a cable problem.
Step 2: Try a different device on the same cable
Connect a laptop or other device you know works on other ports. If the second device also fails to get data, the problem is between the cable and the switch (VLAN configuration, port security, or a cable fault). If the second device works, the original device has a network configuration issue.
Step 3: Check for split pairs
This is the cable fault that fools people. A split pair means the wires are on the correct pins but are not paired correctly. For example, pin 1 is connected to pin 1 on the other end (correct), but it is twisted with the wire going to pin 2 instead of the wire going to pin 2 in the same pair. A basic continuity tester shows all pins passing. But because the twist pairing is wrong, crosstalk between the wires corrupts the data signal.
To detect split pairs, you need a tester that checks pair assignments, not just pin-to-pin continuity. The VDV MapMaster 3.0 detects split pairs. A simple LED continuity tester does not. For more on how cable testers work, see How to Use a Network Cable Tester.
Common causes
- DHCP server not reachable (network problem, not cable)
- Port assigned to wrong VLAN or port security enabled
- Split pairs passing wire map but failing data integrity
- Device NIC driver issue or auto-negotiation failure
Intermittent Connection
The connection works, then drops, then comes back. Sometimes for minutes, sometimes for seconds. The link light may flicker or stay solid while data stops flowing.
Step 1: Reseat all connections
Unplug and firmly replug both ends of the cable, including any patch panel connections and wall plate jacks along the path. A connector that is 90% seated can work most of the time and fail when the cable shifts even slightly. Reseat the patch cable at the switch and at the wall jack or device.
Step 2: Swap the patch cable
If the run goes from device to wall jack to patch panel to switch, the patch cables at each end are the most likely failure points because they get handled the most. Swap both patch cables with known-good replacements. If the intermittent goes away, one of the original patch cables has a marginal termination.
Step 3: Test under stress
Connect the cable to a tester and gently flex the cable near each connector while watching the test results. A marginal crimp will show up as a flickering open or intermittent short when the cable is moved. Also check for kinks, crush points, or sharp bends along the run. A cable that passes the tester on the bench but fails in the wall may have been damaged during installation — a staple through the jacket, a tight bend around a corner, or a crush point where the cable crosses a beam.
Step 4: Check for EMI sources
Ethernet cable running parallel to fluorescent light ballasts, electric motors, power cables, or other electromagnetic interference sources can experience intermittent errors. The TIA-568 standard specifies minimum separation distances: at least 5 inches from power cables running parallel, and at least 12 inches from fluorescent fixtures and motors. If the cable run cannot be rerouted, shielded cable may be needed.
Common causes
- Marginal crimp where one conductor barely contacts the blade
- Broken latch allowing the connector to slowly slide out of the jack
- Cable damaged during installation (staple, crush, tight bend)
- EMI from parallel power cables or fluorescent lights
- Loose punch-down at the patch panel or keystone jack
Slow Speed: 100Mbps Instead of 1Gbps
The connection works but is stuck at 100Mbps when the switch and device both support Gigabit. File transfers are slow, and the switch may show the port operating at 100Mbps.
Step 1: Check the link speed on both sides
Confirm the port is actually negotiating at 100Mbps and not just transferring slowly for another reason (network congestion, device CPU bottleneck, wrong duplex setting). Check the switch port status and the device network adapter properties. If both show 1000Mbps, the cable is fine and the slowness is elsewhere.
Step 2: Run a cable tester
A wire map test on a VDV MapMaster 3.0 or LANSeeker will show the status of all four pairs. If pairs 1-2 and 3-6 pass but pairs 4-5 and 7-8 fail, the cable will work at 100Mbps but cannot reach 1Gbps. The failing pair will show as open (wire not connected) or short (wires touching).
Step 3: Re-terminate the failing pair
Once the tester identifies which pair is bad, cut off the connector and re-terminate. The most common cause is one or two wires that did not seat fully during the original crimp. With pass-through connectors, you can verify all eight wires are through before crimping, which prevents this problem. After re-termination, test again to confirm all four pairs pass.
Common causes
- One pair not making contact at the connector (bad crimp)
- Conductor broken mid-run on one pair
- Using a cable that only has two pairs (telephone-grade cable)
- Punch-down termination on one pair not seated at the patch panel
- Cat3 or Cat5 cable that does not support Gigabit
Cable Tester Failures Explained
When you connect a cable to a tester and it fails, the tester will report the type of fault. Here is what each fault means, what causes it, and what to do about it.
Open
What it means: A wire is not connected at one or both ends. There is no electrical continuity on that conductor.
Causes: Wire did not reach the contact blade during crimping, conductor broke inside the cable, or the wire pulled out of a punch-down terminal.
Fix: Re-terminate the connector end. If both ends test fine individually but the cable still shows open, the break is in the middle of the run and the cable needs to be replaced.
Short
What it means: Two wires are touching each other, creating an unintended connection between them.
Causes: Stripped insulation on adjacent wires touching inside the connector, a whisker of copper bridging two contact blades, or cable crushed to the point where conductor insulation has been compromised.
Fix: Cut off the connector and re-terminate. Inspect the stripped area carefully for any nicks in the conductor insulation. If the short is mid-cable, replace the run.
Miswire
What it means: A wire is connected to the wrong pin. Pin 1 on one end connects to a different pin on the other end.
Causes: Wires were arranged in the wrong color order before crimping. The two most common are swapping the green and blue pairs, or mixing up T568A and T568B on opposite ends.
Fix: Re-terminate one or both ends with the correct T568B (or T568A) wire order. Use pass-through connectors so you can visually verify the color sequence from the front before crimping.
Split Pair
What it means: The correct pins are connected, but the wires are from different twist pairs. Pin continuity is correct, but pair geometry is wrong.
Causes: A subtle wiring error where individual wires end up on the right pins but with the wrong partner. This maintains continuity while destroying the crosstalk cancellation that the pair twist provides.
Fix: Re-terminate with careful attention to pair assignments, not just pin positions. The T568B standard specifies which wires belong to which pair. A split-pair-aware tester like the VDV MapMaster 3.0 will catch this; a basic LED continuity tester will not.
Physical Inspection Checklist
Before you reach for the cable tester, a visual and physical inspection catches many problems. Work through this checklist at both ends of the cable and along the entire run.
When to Re-Terminate vs Replace the Cable
Not every failed cable needs to be replaced. Sometimes cutting off the connector and putting on a fresh one fixes everything. Other times, the cable itself is damaged and no amount of re-termination will help. Here is how to tell the difference.
Re-Terminate When:
- Cable tester shows an open, short, or miswire at the connector end
- One or two pins fail while the rest pass — likely a seating issue
- The connector latch is broken or the connector is physically damaged
- You can see that the cable jacket does not extend into the strain relief
- The strip length was too long or too short
- The wire order is wrong (miswire or split pair)
All of these are connector-side problems. Cut off the old connector, strip fresh cable, and crimp a new connector following the correct procedure. Test after re-termination.
Replace When:
- The cable has a visible kink, crush, or puncture in the jacket
- A conductor is broken mid-run (re-termination at both ends does not fix the open)
- The cable was installed with staples and one or more conductors are nicked
- The cable exceeds the minimum bend radius and has a permanent set
- The cable is Cat3 or Cat5 (pre-Cat5e) and needs to support Gigabit
- A tone generator shows the fault is in the middle of the run, not at the ends
Mid-cable damage cannot be spliced reliably for network use. The cable needs to be pulled and replaced. For permanent structured cabling, this means a new cable pull.
Diagnostic Flowchart
Start at the top. Follow the path that matches your symptom.
Tools for Troubleshooting
You do not need every tool on this list for every job. But having the right diagnostic tools turns a guessing game into a five-minute fix.
Cable Tester
The single most important troubleshooting tool. Tests wire map, detects opens, shorts, miswires, and split pairs. Every cable problem is diagnosable with a tester.
The LANSeeker handles basic pass/fail and cable tracing. The MapMaster adds detailed wire map, split pair detection, and length measurement. The Net Chaser certifies actual throughput up to 10 Gbps. For a full comparison, see Best Network Cable Testers.
Tone Generator and Probe
Sends an audible tone down a specific wire pair so you can trace a cable through walls, ceilings, and bundles without pulling anything apart. Essential for identifying unlabeled cables.
A tone generator connects to one end of the cable and sends a signal. The probe (an inductive amplifier) is held near the cable at the other end or along the run to pick up the signal through the jacket. Useful for identifying which cable goes where when labels are missing.
Loopback Adapter
A small plug that connects the transmit pins to the receive pins on the same port. Lets you verify that a NIC and its port are working by sending data to itself. Useful for isolating whether the problem is the device or the cable.
If a loopback test passes on the device but the device cannot communicate through the cable, the problem is in the cable run or at the far end, not in the device NIC.
Related Articles
Frequently Asked Questions
Why is my ethernet cable not working even though it is plugged in?
Start by checking the link light on the switch or router port. If there is no link light, the physical connection is not being made. Try a known-good cable in the same port. If the known-good cable works, the original cable has a termination or conductor problem. If neither cable works, the port itself may be disabled or faulty. A cable tester will confirm whether the cable has an open, short, or miswire.
Why is my ethernet stuck at 100Mbps instead of 1Gbps?
Gigabit Ethernet requires all four wire pairs to be connected. 100Mbps Fast Ethernet only uses two pairs. If one or more pairs have an open, short, or bad crimp, the link will auto-negotiate down to 100Mbps. Run a cable tester to check all four pairs. The most common causes are a bad crimp on one pair, a damaged conductor, or a connector where one pair did not seat against the contact blades.
What does a split pair mean on a cable tester?
A split pair means the wires are on the correct pins but paired incorrectly. A basic continuity tester will show all pins connected and in the correct order, so it looks like a pass. But the crosstalk between the mis-paired wires causes data errors. You need a tester that checks for split pairs specifically, such as the VDV MapMaster 3.0, which verifies pair assignments in addition to pin-to-pin continuity.
How do I fix an intermittent ethernet connection?
Intermittent connections are usually caused by a physical problem: a bad crimp, a cable that is kinked or crushed, or a connector that is not fully seated. Start by reseating both ends. If it persists, swap the patch cable. If the problem continues, test the permanent link with a cable tester. Wiggle the cable at each termination while watching the tester. An intermittent will often show up as a flickering open.
When should I re-terminate a cable vs replace it entirely?
Re-terminate when the cable tester shows a problem at the connector end, such as an open on one pin, a miswire, or a short between adjacent pins. These are connector-side failures that a fresh termination will fix. Replace the cable when the failure is in the middle of the run, such as a crushed cable, a nicked conductor, or a permanent kink. A tone generator and probe can help locate where along the run the fault is.
Fix It Right the First Time
The right diagnostic tools turn cable troubleshooting from a guessing game into a five-minute fix. Browse our testers, connectors, and termination kits.