Workshop

Summary
Previous Table of Contents Next
A problem that seems insurmountable can become easier to solve if you break it down into smaller parts.
Problems tend to be split in two ways: by location or by component (whether it’s software or hardware).
Although networks are complex and dependent systems, where one failing component can make it seem
like everything has failed simultaneously, typically there’s only one problem causing a domino effect.
The divide-and-conquer method allows you to find the problem component without knowing why it’s
causing a failure. When you have large numbers of components or locations involved, divide-andconquer
troubleshooting (also known as a binary search) can change your number of guesses from
millions to dozens, thus saving you a lot of time.
Although the divide-and-conquer method isn’t always the end-all and be-all of the troubleshooting
process, it’s still a powerful method that can usually pinpoint a culprit in most situations.
Workshop
Q&A
Q Why should I perform divide-and-conquer troubleshooting on my six-node network? It only
takes me six guesses to find any problem!
A You’re right. Obviously, using the divide-and-conquer method with small numbers might seem more
trouble than it’s worth. However, you may end up solving the problem in fewer than six guesses.
Q If my router port is having problems, won’t it seem like the whole network is down?
A Yes, if you have no local servers. In this case, you can try to contact workstations on your physical
segment—this will rule out the physical segment. (For users of Windows 95 file and printer sharing for
Microsoft Networks, try to find someone whose CD-ROM or printer is shared. If you have TCP/IP
installed, try to ping another workstation on the network—if you can, the network is definitely not
down.)
Q Although I’m having some problems on my workstation, the divide-and-conquer method is
problematic for me. I can’t get rid of everything in my Startup folder; otherwise, I won’t be able to
work. Any other suggestions?