Scribd
Upload
2K views19 pages

Identify and Resolve Network Problems

The document outlines an 8-step process for systematically troubleshooting network problems which includes defining the problem, gathering facts, considering possible causes, creating an action plan, implementing tests, analyzing results, and repeating the process if needed. It also discusses documenting network components and configurations to aid in troubleshooting, as well as common network problems like physical connectivity issues, cable faults, and software misconfigurations.

Uploaded by

Abubeker Hashim
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
2K views19 pages

Identify and Resolve Network Problems

The document outlines an 8-step process for systematically troubleshooting network problems which includes defining the problem, gathering facts, considering possible causes, creating an action plan, implementing tests, analyzing results, and repeating the process if needed. It also discusses documenting network components and configurations to aid in troubleshooting, as well as common network problems like physical connectivity issues, cable faults, and software misconfigurations.

Uploaded by

Abubeker Hashim
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Identify and Resolve Network

Problems
Structured Network Troubleshooting
• Troubleshooting Overview
When you’re troubleshooting a network
environment, a systematic approach works best.
Step 1. when analyzing a network problem, make a
clear problem statement. You should define the
problem in terms of a set of symptoms and
potential causes.
Step 2. Gather the facts that you need to help
isolate possible causes.
Ask questions of affected users, network
administrators, managers, and other key people.
Step 3. Consider possible problems based on the
facts that you gathered.
Step 4. Create an action plan based on the remaining
potential problems.
Step 5. Implement the action plan, performing each
step carefully while testing to see whether the
symptom disappears.
Step 6. Whenever you change a variable, be sure to
gather results. Generally, you should use the same
method of gathering facts that you used in Step 2
(that is, working with the key people affected, in
conjunction with utilizing your diagnostic tools).
Step 7. Analyze the results to determine
whether the problem has been resolved. If
it has, then the process is complete.

Step 8. If the problem has not been


resolved, you must create an action plan
based on the next most likely problem in
your list. Return to Step 4, change one
variable at a time, and repeat the process
until the problem is solved.
network problem troubleshooting strategies
and documentation
• Networks can be composed of many
types of physical components, from
copper wire or fiber-optic cables to
wireless Access Points and network
adapters, there are steps you can take
to make troubleshooting network
problems a little easier, regardless of
their composition.
Documented Network Is Easier to Troubleshoot
Some of the important things you should consider as
potential candidates for documenting include the
following:
• A logical map of the network. This may or may not
match up with the physical way the network is laid out.
• A physical map of the network. This documentation
should describe each physical component and illustrate
the ways in which the different components are
connected.
• Cabling and patch panel information. When you've got
hundreds of cables in a wiring closet patching together
different physical segments, you'll need to know which
cable connects this to that.
• Default settings for computers and other devices on the
network. A spreadsheet is good for this. An application
that manages servers, network components, and client
computers is even better.
• Listings of applications and the computers or users that
make use of them, as well as software versions, patch
levels, and so on. Be sure to know who to contact for a
particular application. If you are a network
administrator, you are primarily responsible for the
underlying network. If a particular application is failing,
but the network is up and running, you need to know
who to call. There should always be a contact on your
list for application managers. A network manager can
do only so much.
• Information about the user accounts, and
associated permissions and rights, for the users
and user groups on the network.
• A network overview. It's nice to be able to give a
new user a document that explains what she
needs to know about the network. This should be
a short document telling the user such things as
which drives are mapped to her computer, and
which printers offer what features. This should
not be an extensive document such as the
physical and logical maps described earlier in this
list.
• Problem reports. Keep track of problems as they arise,
and document the cause and remedy.

• A logical map of the network shows the relationships


between components and the flow of information
through the network. A physical map of the network
tries to approximate on paper a representation of how
each component of the network is connected to the
network. For example, a logical map for a Windows
network might show computers grouped by domains,
even though the computers are not located physically in
the same part of the network.
• A physical map would show the location
of each of the computers, the hub or
switch to which they are connected, and
so on. In general, logical maps can be
used to help isolate configuration or
application problems, whereas physical
maps can be used to isolate a problem
that affects only a portion of the
network, perhaps a single computer or
other device.
Problem detection and isolation
Network Problem-Solving Techniques

Item Commands
Check that the network cables are securely in place at the back of the computer.
Check that cables to hubs, switches, bridges and routers are fixed securely in their sockets.
Check the network configuration on workstations Use the commands ‘ipconfig/all’ and
involved, to ensure that they are correct. ‘ping’.

Check that you can access other computers and Use the commands ‘ping’ or ‘tracert’
peripherals on the network. if part of your network is on the
other side of a router.

Check the permissions to ensure that the user has the right levels of access network resources.
Check that an individual user is in the correct group that has access to network resources
Check and replace the network cards and drivers, as required.
Check the configurations of the default gateway and Use the command ‘ipconfig/all’ for
browser proxy server setting. the default gateway, and ‘Tools’,
‘Internet Options’ in the browser to
check proxy settings.
Identifying common network problems
THE FIVE MOST COMMON NETWORK PROBLEMS
Physical Connectivity Problems:
• Configuration is incorrect.
• Cable is faulty or improperly connected.
• Wiring closet cross-connect is faulty or improperly
connected.
• Hardware (interface or port) is faulty.
• Interface has too much traffic.
Cable Problem: Cables that connect different parts of a
network can be cut or shorted.
Cable testers can be used to test for many types of cable
problems such as:
Cut cable, incorrect cable connections, Cable shorts,
Interference level, Connector Problem
Testing Cables
• Cable length— The physical network topology restricts the length of
certain segments in the network.
• Resistance— Electricity encounters resistance as it travels along a
copper wire.
• Noise— Interference can come from other cables that are bundled
together or from outside sources, such as fluorescent lighting, nearby
welding, strong sources of electromagnetic frequencies, and other
high-voltage electrical sources located near the network cabling.
• Attenuation— As the cable encounters resistance traveling down the
wire, and as part of the signal radiates out of the wire, the signal
weakens.
• Near-end cross-talk (NEXT)— From the transmission end of a cable, it
is necessary to remove the surrounding material that encloses the
copper wires and attach each wire to a pin in the cable connector.
• Check the Configuration: Verify that the interface on the
device is configured properly and is not shut down. If the
device is connected to a hub or switch, verify that the port
on the hub or switch is configured properly and is not shut
down. Check both speed and duplex.
• Check the Network Interface card
Most interfaces or NICs will have indicator lights that show
whether there is a valid connection; often this light is called
the link light. The interface may also have lights to indicate
whether traffic is being sent (TX) or received (RX).
• Connectivity Problem: A connectivity problem with one or
more devices in a network can occur after a change is made
in configuration or by a malfunction of a connectivity
component, such as hub, a router or a Switch.
• Troubleshooting Local Connectivity Problems
 This section describes how to troubleshoot local
connectivity problems on LAN segments
Configuration problem
DHCP or BOOTP issue
Physical layer issue
Duplicate IP address

Software Problem: Network problems can often


be traced to software configuration such as DNS
configuration, WINS configuration, the registry
etc.
IP Troubleshooting
• To efficiently troubleshoot a TCP/IP connectivity
problem, it is necessary to identify a single pair of
source and destination devices that are exhibiting
the connectivity problem.
LO-2: Troubleshoot network problems
Network Diagnostic Tools
Installing and Configuring a Wired Network
• To have network connectivity, you need to have
three things in place:
■ NIC: The physical hardware that connects the
computer system to the network media.
■ Protocol: The language that the computer systems
use to communicate.
■ Network client: The interface that allows the
computer system to speak to the protocol.
LO-3: Carry out maintenance support on identified problem

Private IP address space

 
Starting Ending Remark
Address Address
1
10.0.0.0 10.255.255. We can have 224 private IP
255 addresses
2
172.16.0.0 172.31.255. We can have 220 private IP
255 addresses
3
192.168.0.0 192.168.255 We can have 216 private IP
.255 addresses

You might also like