Identify and Diagnose Computer Network Faults
Identify and Diagnose Computer Network Faults
diagnose
computer
network faults
1. Identify the symptoms and potential
causes.
• In this first step you define and determine the nature of the
problem. Is it the user or computer that is problematic? Are all
websites unreachable, or just one or a few? Is the computer
consistently online or is the connection flapping? Are websites
reachable by IP address but not by name? Are there any error
messages indicating what type of error was encountered?
2. Identify the affected area.
• This step is similar to the first step, but here you determine the
extent of the problem. Is it affecting one computer or user, or
multiple computers or users? Are all computers in the subnet (or
all users in the domain) affected? Is the whole network down? If
you are providing support to another user, can you reproduce the
error yourself? Gather detailed information.
3. Establish what has changed.
• This is where you try to put the connectivity problem in some kind
of time frame. Find out if the user was ever able to successfully do
what he now cannot do. When did the error first appear? Before
the appearance of the error were there any programs or operating
system updates installed? How about new drivers or browser
plugins?
4. Establish the most probable cause.
• Use your technical expertise to isolate and explain the cause of the
problem. Some indepth investigation and diagnostic tools will
probably be required. This step is described in more detail below.
5. Determine if escalation is necessary.
• When you believe the steps of the action plan have been fulfilled,
try to re-create the error. Observe the results of the
implementation. Is the problem gone? If not, repeat steps 4, 5, and
6.
8. Identify the results and effects of the
solution.
• Once a solution has been found, ensure that normal network
operation has been restored and that no new problems have been
introduced.
9. Document the solution and process.
Your bandwidth is spread too thin, especially if there are plenty of devices
connected doing data-hungry applications and tasks
Peak hours where people connect all at once, thereby causing congestion
(e.g. urban areas, libraries, hotels, etc)
2. No connection at all.