Professional Documents
Culture Documents
Identifying and Resolving
Identifying and Resolving
Identifying and Resolving
SERVICING
Level III
LEARNING GUIDE # 1
Unit of Competence: Identify and
Resolve Network Problems
Module Title: Identifying and Resolving
Network Problems
Module Code :ICT HNS3 07 1110
Module Title
Identifying and Resolving Network Problems
1.2 General Problem-Solving Model
When you’re troubleshooting a network environment, a
systematic approach works best. An
Unsystematic approach to troubleshooting can result
in wasting valuable time and resources, and can
sometimes make symptoms even worse.
Define the specific symptoms, identify all potential
problems that could be causing the symptoms, and then
systematically eliminate each potential problem (from
most likely to least likely) until the symptoms disappear
problem-solving process
1. Analyzing a network problem
2. Gather the facts that you need to help isolate
possible causes
3. Consider possible problems based on the facts
that you gathered Using the facts, you can eliminate
some of the potential problems from your list.
4. Create an action plan based on the remaining
potential problems.
5. Implement the action plan, performing each step
Networks can be composed of many types
of physical components
• copper wire
• optic cables
• wireless Access Points
• Switch
• Bridge
• Router
• firewall
• network adapters
• protocol
1.3 net work problem troubleshooting strategies
and documentation
Documented Network Is Easier to Troubleshoot it can
be contained following
1. A logical map of the network
2. A physical map of the network
3. Cabling and patch panel information
4. Default settings for computers and other devices on the
network
5. A logical map of the network shows the relationships
6. A physical map would show the location of each of the
computers, the hub or switch
1.5 Identifying common network problems
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
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.
Installing a NIC
.
The NIC is your computer system’s link to the network, and installing
one is the first step required to connect to a network. NICs are
manufactured to operate on specific media and network types, such as
100BaseT Ethernet or 16 Mbps Token Ring. Follow the
manufacturer’s instructions for installation.
NetBEUI is easy to configure, since no network addresses are
needed. Generally, all you need to establish a connection between
computer systems using
NetBEUI is a NetBIOS computer name
NWLink is a relatively easy protocol to configure. Normally, the
only settings you may need to specify are the internal network number
and frame type (usually, however, the default values are sufficient).
Which command line tools should I use?
1. I can connect but cannot view websites.
Ping - Trace route - DNS Lookup - Telnet
2. I can browse websites but cannot connect to email.
Ping - Trace route - Telnet
3. I have an intermittent connection problem.
Ping - Netstat - Netshell
3. I think I have a virus problem on my system.
Netstat - DNS Lookup
4. Ping(Packet Internet Groper) - "Can my data
reach you?"
Continuous Ping
Destination network unreachable - this means that a device that the you are sending
data to is not responding, it my down, or there might be a network fault. This type of
problem is usually outside Flush control.
IPCONFIG
Windows 2000/XP offer the command-line tool IPCONFIG for a quick balance at
your network settings. Click Start |Run and type CMD to get a command prompt.
From the prompt, type IPCONFIG /ALL to see all of your TCP/IP settings
Flush DNS Cache