May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Troubleshooting TCP/IP Communication Issues

Faulty Cable

Those days this is are problem. So it is pretty difficult to diagnose when it does happen. You need to differenciate faulty cable from falty connection.

Often faulty cable problem develops because the plastic lock fall out. Then connection can became unreliable due to vibration.  This is more typical for home networks for obvious reasons, but can sometimes happen in datacenters too.

Check that the link status LED is lit first. Then test the connection with your laptop or with a known working cable. The link LED will be lit even if the transmit line is damaged. Verify that a mdi-x connection or crossover cable is being used if connecting hub to hub.

For example users on network A could not reach hosts on network B even though routers R1 and E2 appeared to be functioning normally.

First you need to verify that the routers R1and R2 were configured correctly and that the interfaces are up. They you need to verify that  systems A and B were up and configured correctly.

You need to use the traceroute utility to discover the actual route from system A to system B.

For example the traceroute output shows that the attempted route from system A on network net-1 goes through router R1 as expected. But the traffic never reaches router R2 though.

Investigate the router R2 log files. For example is they show that  the interface to network net-2 is flapping (going up and down at a very high rate) and corrupt routing tables you can suspect that the cable is a problem.

To solve this problem, replace the network net-2 cable to router R2. If it fixes the problem then it was faulty and causes intermittent connections.

Top Visited
Past week
Past month


Old News ;-)

Troubleshooting network problems

Troubleshooting a cable problem

Although many types of cables are used for networking, the most commonly used fall into two categories: coax (which looks similar to the wire used for cable television) and twisted pair (which is similar to telephone cable). Because these types of cable are so dissimilar, they require different troubleshooting methods.

Troubleshooting twisted pair

Twisted pair is considerably easier to troubleshoot than coax. Because of the nature of twisted pair, each line services only one PC (unless that line happens to run between two switching devices). If you suspect a cable problem in a network that uses twisted pair, the first thing you should check is the link light. If the link light isn't lit, it means that you don't have a complete physical link. Usually this indicates a break in the cable or a loose RJ-45 connector. Note that the link light can sometimes be illuminated even if you have a cable problem: link light merely indicates that the wire is connected at both ends.

If the link light is lit but you still suspect a cable problem, you should plug a known good laptop computer into the cable. If the laptop establishes a network connection, the problem is with your PC. Otherwise, you have a cable problem.

Troubleshooting coax

The sidebar "Coax Basics" provides some background on coax-based networks. Needless to say, most cable problems on coax-based networks affect multiple PCs. If you have a communication failure but your terminators are connected and are the correct type, you should check for a cable break. A break in the cable causes the wire to function as two separate unterminated networks, because the point at which the cable ends (the break) is unterminated.

Breaks or shorts in coax cables are often hard to find, because they aren't always visible to the naked eye. A break could be caused by something as simple as a loose T-connector. Although the wire may not be completely pulled out of the connector, it may be loose enough that it can't make a good connection. It's also tricky to locate breaks and shorts when a coax cable snakes its way through walls and conduit, under desks (where users often stack boxes on top of the wire), and into other inaccessible places.

The easiest way to troubleshoot a coax segment is to take two known good terminators and use one to terminate the cable at the source. The source is the place at which the cable connects to the server, another segment, a hub, and so on. Go to the first PC on the segment and disconnect the T-connector from the PC. Remove the portion of the line that goes to the rest of the network and replace it with the second terminator. Now, reconnect the T-connector to the PC and try to log on to the network with the PC. If the PC fails to connect, your problem is somewhere between the two terminators.

If the PC does connect, remove the terminator from the T-connector on the PC, reattach the cable to the T-connector, and repeat the process at the second PC on the line. As you get further down the line, you'll reconnect and test one PC at a time until you come to the source of the problem. If you fix a problem but the line still malfunctions, keep in mind that you may have multiple breaks on the line.

Occasionally, you may trace a problem to a particular PC and yet be unable to find a break in the line. If this happens, try disconnecting the T-connector from that PCbut enable the rest of the PCs on the line and test the network. Sometimes, a network card will go bad and flood the line with high-volume random packets. If this happens, it can cause symptoms similar to a cable break or a missing terminator.

Recommended Links

Google matched content

Softpanorama Recommended

Top articles


Troubleshooting network problems (Microsoft Technet).

Solving Hardware Problems

PC Repair Guide Network Interface Card (NIC) Diagnosis, Repair and Replacement - ACME HOW



Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy


War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes


Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law


Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright © 1996-2021 by Softpanorama Society. was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to to buy a cup of coffee for authors of this site


The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019