Académique Documents
Professionnel Documents
Culture Documents
Network Hardware
Objectives:
When you have completed this lesson, you will be able to:
Discussion:
When a computer network stops functioning, it is the job of the
computer repair technician to be able to identify if a network
problem lies within the computer system or within the hardware and
software of the network system. With all network systems that
become a “notwork” system, the first step in the actual repair of the
problem is to divide the problem into whether a component or
software inside the client computer is causing the trouble. This is
often done by disconnecting the computer from the network and
seeing if the remainder of the network system functions normally.
When possible, a technician may also connect another computer to
the network connection that appears not to be functional, using this
method, if the new computer is able to connect to the network, the
problem lies within the computer.
It is beyond the scope of this course to teach network
administration, planning, design or deployment, it is only intended
to help the computer repair technician to become familiar with the
basic methods of troubleshooting.
Troubleshooting is a task that all LAN administrators must perform
at one time or another. Depending on their skill level and
experience, administrators may be able to troubleshoot the network
on a small or large scale. In either case, experience is a great
teacher when it comes to troubleshooting a network.
Many computer repair technicians spend a great deal of time
troubleshooting network problems. One user calls to report that he
or she can't print, another calls complaining that he or she can't log
into the network. Yet another user calls, irate, because the
workstation is frequently hanging; the LAN administrator must
diagnose these problems. Once the root of the problem is found,
solving the problem is fairly easy. Many times, all that is needed is
to replace faulty hardware or software.
The computer repair technician can solve the problem in one of two
ways by using a structured, rigorous methodology, or by
shotgunning, the latter method involves educated guesses and
arbitrarily replacing components to see if the problem disappears,
while using a structured methodology, requires definitively knowing
what the problem is before fixing it. Most experienced technicians
use both approaches in a staged fashion. For a new technician, a
structured approach is recommended, until experience provides the
knowledge base needed to make educated guesses.
It is important to fully understand the problem being diagnosed.
Missing vital information at the beginning of a check can lead to an
incorrect diagnosis and an inappropriate fix. An understanding of
the problem will also help determine whether a more thorough
check is needed.
The goal of this stage is to identify and eliminate potential causes of
the problem. The best way to do this is to talk to the users. Solicit
their input and complaints. Ask them to re-create the problem if
possible, so you can witness it firsthand. Find out if the problem is
widespread, with several people affected or if only one person is
experiencing the problem. Check to see if the problem is preventing
users from working or whether it's simply a performance problem,
causing delays or interruptions.
Always be aware of the kinds of work the users do and the
applications they use. For example, if a user is having trouble
printing a document, the problem could be that he or she isn't
executing the print command properly. Familiarity with users' work
and applications allows some problems to be fixed quickly.
Sometimes performing one or two simple tests is required to
ascertain the severity or scope of the problem. You may get the
system back up and running more quickly by simply replacing or
swapping a component or two. If this doesn't work, some
information has still been obtained without wasting much time.
Phase one is when experience and documentation are crucial. Is
anything about the problem similar to a previous problem? For
example, assume several adapter cards have gone bad in the past.
They started creating errors shortly before they failed completely,
as documentation should show. Now a user is having trouble
attaching to the network. After asking some questions and finding
out that he or she is getting error messages similar to those
associated with the cards that failed in the past it becomes
apparent that the problem is solved, remedied, and documented.
Most problems encountered on the network have probably
happened before, making it possible to identify the problem just by
going over the network's history in your mind. If you're new to the
Advanced Diagnostics
The network is divided into workable segments so you don't have
the entire network to contend with. Each segment can then be
examined and either ruled out or found to be the cause of the
problem.
Because more information must be gathered during this stage,
specialized equipment, such as a protocol analyzer, may be
needed.
Most network problems are directly related to the network
components. The following is a list of some of the components that
may need to be examined more closely.
Workstation
Network adapter
The network interface card is responsible for all communication
between the clients and the server. Regardless of the type of
network you are running, or the cabling installed at the location, the
NIC or network interface card must be installed correctly, and must
be communicating with the operating system. Common NIC
problems are usually traced directly to initial installation, or new
Wiring Concentrator
This device is sometimes called the HUB and is normally found
when the installed network operates either, in a token ring
configuration or utilizes standard telephone type wiring called
twisted pair. The common types of twisted pair wiring are 10BaseT
and 100BaseT, the differences between the two are the speed at
which the information is transferred, 10 Mbps and 100Mbps,
respectively. The concentrator or HUB must match the speed of the
installed network, and the protocol of the installed network. In
addition, the HUB should be powered from an uninterruptable
power source to prevent downtime related to power line
disturbances. Normally, once a hub is installed, they function with
little or no intervention by the technician or operator, and for the
most part, do not require any routine maintenance or repairs. Hub
related problems are normally easy to diagnose, because when a
hub fails, multiple stations on the network will go off line, and their
link lights and activity lights will go out. Single port failures on a
hub are unlikely, but can happen. If this problem occurs, only a
single station will be affected by the defective hub.
Cabling
The cabling of a network is the most important, and often the most
overlooked part of the network. Usually, once a network has been
installed, little if any thought is ever given to the cables as a
potential source of trouble. However, there is always the possibility
that a cable can be cut by someone working in the building,
Server
As with all computer systems, determining if the computer is
functional as a computer is the first priority. One should never
assume that the trouble being experienced is automatically a
problem that involves the network. To determine if the server is
functional as a computer system, it may become necessary to
disconnect the server from the network. It should be obvious, that
before you go disconnecting anything, be sure that you have the
permission necessary to do this, remember, other users may be
sharing files or information on the network, and disconnecting
something may cause permanent damage to data or stored files.
Host
This is a specialized computer, that can be thought of as a
fileserver, with a very special job. The host is used to connect a
group of computers to a wide area network, either through
dedicated phone lines or other long-range distribution technology.
When a host is not working, as with a file server, normal computer
repair strategy should first be employed.
Bridges
This is also a specialized computer that has a dedicated job of
connecting two networks together, forming a wide area network or
large corporate intranet. The sole job of the bridge is to read the
incoming network traffic, determine the type of data contained in
the network traffic, decide where the traffic is to go, and connect
that traffic to the network segment that contains the address of the
desired data, complete with the proper protocol for the new network
segment. The bridge can present many new and exciting problems
for the technician, most of which are related directly to information
not being processed to the correct or desired network segment.
Bridge problems that are NOT related to a computer failure or
malfunction should not be handled by the computer repair
technician but left to the network systems engineers.
Routers
A router is similar to a bridge in as much as the sole job is to
process incoming and outgoing information and direct that
information to the correct network segment. The major difference is
that a Router does NOT change the protocol of the information
being carried in the network packet. This information is decoded,
and transferred to the corresponding address of the destination
data. Routers can be as simple as stand alone devices that are
programmed using a laptop computer and serial data cable, or may
in fact be a computer all to itself.
Gateways
This computer connects networks that use different protocols. The
sole job of the gateway is to translate the incoming network traffic
to the protocol needed by the receiving network. If data is not being
received or understood by other computers on the system using
different protocols, the most likely reason is that the gateway has
stopped functioning. A common example of a gateway would be to
connect an Ethernet network to a Token Ring Network.
Protocol Stacks
The protocol stack is responsible for the communication between
the physical network and the network operating system, the
applications requesting information and the overall communication
between them. The repair technician does not have to be
concerned with the operation or communication of the Protocol
stack, only that the appropriate stack is loaded in the client and
server computer.
The Fileserver
As with all computer systems, determining if the computer is
functional as a computer is the first priority. One should never
assume that the trouble being experienced is automatically a
problem that involves the network. To determine if the computer is
functional as a computer system, it may become necessary to
disconnect the computer from the network. It should be obvious,
that before you go disconnecting anything, be sure that you have
the permission necessary to do this, remember, other users may be
sharing files or information on the network, and disconnecting
something may cause permanent damage to data or stored files.
Assignment:
1. Once a computer network stops functioning, it is the job of the
computer repair technician to be able to identify if a network
problem lies within the computer system or within the hardware and
software of the network system.
a. True
b. False