MAICHEW POLYTECHNIC COLLEGE

DEPARTMENT OF INFORMATION TECHNOLOGY

HARDWARE AND NETWORK 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

Nominal Duration
Learning outcome
Implement regular network monitoring
Troubleshoot network problems
Carry out maintenance support on identified problem

1|Page Prepared By Haftamu Hailu

 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

LO-1: IMPLEMENT REGULAR NETWORK MONITORING

.
1 Structured Network Troubleshooting
1.1Troubleshooting Overview

Dependency on network resources has grown tremendously over the past ten years.
In todays world, a companys success is highly dependent on its network
availability. As a result, companies are increasingly less tolerant of network
failures. Therefore, network troubleshooting has become a crucial element to many
organizations.
Not only has the dependency for network grown, but the industry also is moving
toward increasingly complex environments, involving multiple media types,
multiple protocols, and often interconnection to unknown networks. These
unknown networks may be defined as a transit network belonging to a Internet
service provider (ISP). The convergence of voice and video into data networks has
also added to the complexity and the importance of network reliability.
More complex network environments mean that the potential for connectivity and
performance problems in internetworks is high, and the source of problems is often
elusive.
1.2 General Problem-Solving Model
When youre 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.
The following steps detail the problem-solving process outlined here:
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.
To properly analyze the problem, identify the general symptoms and then ascertain
what kinds of
problems (causes) could result in these symptoms. For example, hosts might not be
responding to service requests from clients (a symptom). Possible causes might
include a misconfigured host, bad interface cards, or missing router configuration
commands.
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. Collect

2|Page Prepared By Haftamu Hailu

 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

information from sources such as network management systems, protocol analyzer

traces, output from router diagnostic commands, or software release notes.
Step 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.
Depending on the data, for example, you might be able to eliminate hardware as a
problem so that you can focus on software problems. At every opportunity, try to
narrow the number of potential problems so that you can create an efficient plan of
action.
Step 4. Create an action plan based on the remaining potential problems.
Begin with the most likely problem, and devise a plan in which only one
variable is manipulated.
Changing only one variable at a time enables you to reproduce a given solution to a
specific problem. If you alter more than one variable simultaneously, you might
solve the problem, but identifying the specific change that eliminated the symptom
becomes far more difficult and will not help you solve the same problem if it
occurs in the future.
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.
Note If you exhaust all the common causes and actionseither those outlined in
this book or
ones that you have identified for your environmentyou should contact your
Cisco
technical support representative.
1.3 net work 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. Although each device, protocol, or standard that is
a part of your network may come with its own tools used for troubleshooting
purposes, it's important to realize that you should take a structured approach to
3|Page Prepared By Haftamu Hailu
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

solving problems on the network. This chapter introduces a few concepts that make
life much simpler for a network administrator, including documenting network
components, and also documenting problems (and solutions that work).
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. No need to solve the same problem twice! This also
includes outage reportskeeping track of unscheduled downtime for a
computer or network device can tell you over time just how capable the
device is.

4|Page Prepared By Haftamu Hailu

 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

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.

1.4 Problem detection and isolation

1.4.1 Network Problem-Solving Techniques

In any troubleshooting procedure a series of tests narrows down the possible

causes of a problem. The following procedure can be used as a guideline
each organisation will have their own procedures to suit their computing
environment.

Table 3: When the user cannot access a peripheral on the network typical
techniques for troubleshooting

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 Use the
configuration on commands
workstations involved, to ipconfig/all
ensure that they are and ping.
correct.
Check that you can Use the
access other computers commands
and peripherals on the ping or
network. tracert if part
of your network
5|Page Prepared By Haftamu Hailu
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

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 Use the
of the default gateway command
and browser proxy server ipconfig/all for
setting. the default
gateway, and
Tools,
Internet
Options in the
browser to
check proxy
settings.

1.5 Identifying common network problems

THE FIVE MOST COMMON NETWORK PROBLEMS

1. Physical Connectivity Problems:

This section describes how to troubleshoot Layer 1 and 2 physical connectivity

issues on LANs such as Ethernet or Token Ring. Problems can generally be found
more quickly by first troubleshooting at Layer 3 and then working backward when
a physical problem is found or suspected. Possible problems include these:

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.

6|Page Prepared By Haftamu Hailu

 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Cable Problem: Cables that connect different parts of a network can be cut or shorted.
A short can happen when the wire conductor comes in contact with another conductive
surface, changing the path of the signal. 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

Things that are usually tested include the following:

Cable length The physical network topology restricts the length of

certain segments in the network. If you make your own cables, a common
error may result from trying to stretch the limits of the topology and create a
cable that's just a few meters too long. If a desktop is just a few meters
farther from a switch than the standard allows, you may get complaints from
that user!
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. This is
a normal side effect of using copper wiring instead of fiber optics. You can
expect copper wiring to work best at the standardized lengths, and take your
chances at extending that length.
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. Because the strength of
signal is strongest at the end of the cable where the electrical signal is
generated, there is a greater potential for interference between the wires at
this end of the cable.

7|Page Prepared By Haftamu Hailu

 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Rule Out a Configuration Problem

Check to make sure that all cables are connected to the appropriate ports.
Make sure that allcross-connects are properly patched to the correct location
using the appropriate cable and method.
Verify that all switch or hub ports are set in the correct VLAN or collision
domain and have appropriate options set for spanning tree and other
considerations.

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). If the interface has indicator
lights that do not show a valid connection, power off the device and reseat the interface
card.

2. 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 such as Ethernet or Token Ring. Going through the methodology in this
chapter with help determine and resolve problems moving packets on the local LAN
segment or to the next-hop router. Possible problems include these:

Configuration problem

DHCP or BOOTP issue

Physical layer issue

Duplicate IP address

8|Page Prepared By Haftamu Hailu

 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Check for Configuration Problems

To begin troubleshooting, display and examine the IP configuration of the source

device. The method to determine this information varies greatly from platform to
platform. If you are unsure of how to display this information, consult the manual for
the device or operating system. Refer to the following examples:

On a Cisco router, use show ip interface and show running-config.

On Windows 95 or 98, use winipcfg.exe.

On Windows 2000 or NT, use ipconfig.exe.

On a UNIX platform, use ifconfig.

Examine the configuration, looking specifically for the IP address and subnet mask. On
Windows 9x or Windows 2000 platforms, the default gateway address should also be
displayed.

If no IP address is configured, verify that this node receives its IP address from
BOOTP or DHCP. Otherwise, an IP address should be statically configured for this
interface.
Configure an address if one is not present. If the source is configured to receive an
IP address via DHCP or BOOTP and is notreceiving one, make sure that the bootp
(IP) helper address is configured on the router interface facingthe source device.
If the incorrect IP address, subnet mask, or default gateway is configured, verify
that this node receives
its IP address from BOOTP or DHCP, and then contact the DHCP or BOOTP
administrator. Ask the
administrator to troubleshoot the DHCP or BOOTP servers configuration. If the
address is statically
configured, configure the correct address.

3. Excessive Network Collisions: These often lead to slow connectivity. The problem can
occur as a result of bad network setup/plan, a user transferring a lot of information
or jabbering network card.

NB: A jabbering Network card is a network card that is stuck in a transmit mode.
This will be evident because the transmit light will remain on constantly, indicating
that the Network card is always transmitting.

9|Page Prepared By Haftamu Hailu

 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Software-Based Analyzers

Software analyzers are the cheapest route for large, complex networks. Because
processors have scaled to much greater speeds and network adapters can capture
packets from the fastest LAN speeds, software analyzers are now catching up to
hardware-based analyzers. And you can find some freeware analyzer products on
the Web that perform some or all of the functions you might need in a small
network.

Windows NT 4.0 through Windows 2003 servers come with a network monitor
tool that enables the local workstation or server to monitor network traffic that is
generated by or sent to the computer. The version that comes with the Systems
Management Server (SMS) allows the network administrator to monitor all traffic
on the LAN, using a feature referred to as promiscuous mode. The Windows 2000
Servers and Windows 2003 Servers network monitor can be found in the
Administrative Tools folder.

4. Software Problem: Network problems can often be traced to software configuration

such as DNS configuration, WINS configuration, the registry etc.

Troubleshooting Domain Name Server Problem

It is possible for IP connectivity to work but for DNS name resolution to fail. To
troubleshoot this situation, use one of the following methods to determine whether DNS
is resolving the name of the destination:

Ping the destination by name, and look for an error message indicating that the name
could not be resolved. Otherwise, continue troubleshooting as follows:

1. Determine which name server you are using; this can be found in different places on
each operating system, so if you are unsure of how to find it, consult the devices
manual

On Windows 95 or 98, use winipcfg.exe.

On Windows 2000 or NT, use ipconfig.exe.

On a UNIX platform, type cat /etc/resolv.conf at a command prompt.

2. Verify
that you can ping the name server using its IP address. If the ping fails, go to the
section to troubleshoot connectivity between the client and the name server.

10 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

3. Verify that you can resolve names within your domain. (For example, if your host is
Host1.test.com, you should be able to resolve the names of other hosts in the test.com
domain, such as host2.test.com.)

4. Verify that you can resolve one or more domain names outside your domain. If you
cannot resolve names from all domains except that of the destination, there might be a
problem with the DNS for the destination host. Contact the administrator of the
destination device. If you cannot resolve names within your domain or a large number of
external domains, contact your DNS administrator because there may be a problem with
the local DNS (or your host could be using the wrong domain server).

5. Duplicate IP Addressing: A common problem in many networking environments occurs

when two machines try to use the same IP address. This can result in intermittent
communications.

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. When youve selected the two devices, test to make sure that the problem is
actually occurring between these two devices. Possible problems include these:

Physical layer issue somewhere along the path

First-hop Layer 3 connectivity issue, local LAN segment
Layer 3 IP connectivity issue somewhere along the packets path
Name resolution issue
Where to start:
1. Try to ping from the source to destination device by IP address. If the ping fails,
verify that you are using the correct address, and try the ping again. If the ping still
fails, go to the next section, Troubleshooting Local Connectivity Problems.
Otherwise, proceed to Step 2.
2. Try to ping from the source to the destination device by name. If the ping fails,
verify that the name is correctly spelled and that it refers to the destination device,
and then try the ping again. If the ping still fails, go Troubleshooting Domain
Name Server Problems, later in this chapter.
Otherwise, proceed to Step 3.
3. If you can ping the destination by both name and address, it appears that the
problem is an Upper-layer problem.

11 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

LO-2: Troubleshoot network problems

2. 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.
If you want to share resources on your PC with other network users, you also need
to enable Microsofts File and Printer Sharing. This installs the services and
software that turns a Windows PC into a server. Plus, of course, you need to
connect the PC to the network hub or switch
via some sort of cable (preferably CAT 6 with Gigabit Ethernet cranking through
the wires, but thats just me!). When you install a NIC, by default, Windows 2000
and XP Professional install the TCP/IP protocol, the Client for Microsoft
Networks, and File and Printer Sharing for Microsoft Networks upon setup.
Installing a NIC
The NIC is your computer systems 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 manufacturers instructions for installation. If your NIC is of
recent vintage, it will be detected, installed, and configured automatically by
Windows 2000 or Windows XP. You might need a driver disc or a driver
download from the manufacturers Web site if you install the latest and greatest
Gigabit Ethernet card.
Add Hardware Wizard
The Add Hardware Wizard automates installation of nonplug-and-play devices,
or plug-and- lay devices that were not detected correctly. Start the wizard by
clicking Start | Settings | Control Panel, and double-clicking the icon for the Add
Hardware applet. (Note that Windows 2000 calls this the Add/Remove Hardware
applet.) Click the Next button to select the hardware task you wish to perform, and
follow the prompts to complete the wizard.
Configuring a Network Client
To establish network connectivity, you need a network client installed and
configured properly. You need a client for every type of server NOS to which you
plan to connect on the network. Lets look at the two most used for Microsoft and
Novell networks.
Client for Microsoft Networks
12 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Installed as part of the OS installation, the Client for Microsoft Networks

rarely needs configuration, and, in fact, few configuration options are available. To
start it in Windows XP, click Start, and then right-click My Network Places and
select Properties. In Windows 2000, click Start | Settings | Network and Dial-up
Connections. In all versions of Windows, your next step is to double-click the
Local Area Connection icon, click the Properties button, highlight Client for
Microsoft Networks, and click the Properties button. Note that theres not much to
do here. Unless told to do something by a network administrator, just leave this
alone.
Client Service for NetWare
Microsofts Client Service for NetWare provides access to file and print
resources
on NetWare 3.x and 4.x servers. Client Service for NetWare supports some
NetWare utilities and NetWare-aware applications. To connect Microsoft client
workstations to NetWare servers running NDS also requires the Microsoft Service
for NetWare Directory Services (NDS). Once installed, Client Service for NetWare
offers no configuration options.
Configuring Simple Protocols
Protocols come in many different flavors and perform different functions on the
network. Some, such as NetBEUI, lack elements that allow their signals to travel
through routers, making them non-routable (essentially, this protocol is unsuitable
for a large network that uses routers to re-transmit data).
The network protocols supported by Windows include NetBEUI, NWLink
(IPX/SPX), and TCP/IP, although Windows XP drops support for NetBEUI. This
section looks at installing and configuring the simple protocols used by Windows
2000: NetBEUI and NWLink.
NetBEUI
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. NetBIOS names must be unique
and contain 15 or fewer characters, but other than that there isnt much to it.
To install the NetBEUI protocol in any version of Windows except XP,
follow these steps:
1. In Windows 2000, click Start | Settings | Network and Dial-up Connections.
Double-click the Local Area Connection icon to bring up the Local Area
Connection Status dialog box (Figure 2.1).
2. Click the Properties button to bring up the Local Area Connection Properties
dialog box (Figure 2.1).

13 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

LAN Properties dialog box (Figure 2.1)

3. Click the Install button. In the Select Network Component Type dialog box,
highlight Protocol and click the Add button (Figure 2.2).
4. In the Select Network Protocol dialog box, select NetBEUI Protocol (Figure
2.3), and click the OK button. You will be prompted to reboot the system to make
the changes take effect.

(Figure 2.2)

(Figure 2.3)
14 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

NWLink (IPX/SPX)
As mentioned, NWLink is Microsofts implementation of the IPX/SPX protocol.
The Microsoft version of NWLink provides the same level of functionality as the
Novell protocol and also includes an element for resolving NetBIOS names.
NWLink packages data to be compatible with client/server services on NetWare
networks, but it does not provide access to NetWare File
and Print Services. For this, you also need to install the Client Service for
NetWare, as noted
earlier.
Follow the same steps used to install NetBEUI to install NWLink, except choose
NWLink rather
than NetBEUI when you make your final selection. Youll be prompted to reboot
after adding
the protocol.
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). The internal network number is used by
the network for routing purposes.
The frame type specifies how the data is packaged for transport over the network.
For computers to communicate by NWLink, they must have the same frame types.
By default, the
Frame type is set to Auto Detect.
To configure NWLink properties manually, follow these steps:
1. In Windows XP, click Start | Control Panel and open the Network
Connections applet. Double-click the Local Area Connection icon. In Windows
2000, click Start | Settings | Network and Dial-up Connections, and double-click
the Local Area Connection icon.
2. Click the Properties button, highlight NWLink IPX/SPX/NetBIOS Compatible
Transport Protocol, and click the Properties button.
3. In the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol properties
dialog box, set the internal network number and frame type (Figure 2.4).

TCP/IP testing tools

All versions of Windows come with handy tools to test TCP/IP. Those that youre
most likely to use in the field are Ping, IPCONFIG, NSLOOKUP, and TRACERT.
All of these programs are command prompt utilities! Open a command prompt to
run them,if you just place these commands in the Run command, youll see the
command prompt window open for a moment
and then quickly close!

15 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Introduction

There are many possible causes of connection problems. This guide will show how
you can investigate problems using some simple tools that come with most
versions of Windows. To use all of the tools though, you will need Windows Vista
or XP.

Testing your network

The tools in this guide can be accessed from the command prompt. While this can
look a little intimidating, it is simple to use with a little bit of know-how.

Connection Settings
This Module assumes that you have checked and confirmed that your connection
settings are correct. Broadband customers should first check our General
Broadband Setup Guide.

Does your PC have a network connection?

Check the sockets. Most sockets have a connection light.

1. The light is on when a connection is detected.

2. The light flashes when data is passing through the connection.

Check your network settings

1. Click Start.
2. Click Settings.
3. Click Network Connections.
4. Check the status of your network connection. If your connection is broken,
your connection icon will show a small red cross.

5. Right click on your connection icon.

16 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

6. Select Status to view details.

7. If your connection is broken, click on Repair to attempt to reconnect.

If your connection is still broken, you need to check your network settings.

Using the command line (DOS prompt)

To use the network tools described in this article you need to open a command line
window. Command line looks like the old DOS environment, and is used through
typed commands rather than with a graphical interface. To open a command line:

1. Click Start.
2. Click Run (or press the r key).
3. Type "cmd" into the 'Run' window.
4. Click Return.

Although you can run these tools by typing them directly into the Run prompt, as
soon as the command has finished, the window will close which will stop you from
seeing the results. Always open a command line window first before starting the
tool.

Saving results to Notepad

17 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

If you need to send results of your tests to the support team for further
investigation, you can do so by copying them from the command line window, into
Notepad or another text editor.

To copy test results

1. Right Click on the title bar of the command line window.

2. Click Edit.
3. Click Select All.
4. Click Enter.
5. Paste into Notepad.
6. Save the Notepad file to your hard drive. Many tools will allow you to
output the results to a text file instead of on the screen. To do this, type on
the command line "[tool] > c:\test_results.txt". For example - netstat >
c:\netstat_results.txt
7. Then view the file using a text editor.

Which command line tools should I use?

I can connect but cannot view websites.

Ping - Trace route - DNS Lookup - Telnet

I can browse websites but cannot connect to email.

Ping - Trace route - Telnet

I have an intermittent connection problem.

Ping - Netstat - Netshell

I think I have a virus problem on my system.

Netstat - DNS Lookup

Ping(Packet Internet Groper) - "Can my data reach you?"

18 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Ping sends packets of data to another computer and measures how long it takes to
get there. Ping results can tell you that:

You are connected.

Your connect is responsive (low latency).
Your connection is consistent (not dropping out).

To use Ping

1. In the command line window, type"ping [destination address]".

2. Click Enter and watch for the results.

3. You'll see how Ping turns the web address into the corresponding IP address
(i.e. "www.google.com" would be turned into 64.233.183.99).

Ping sends four packets and gives you an average for the time it takes for the ping
to make it round

Ping responses

Response Explanation
Ping request could not find Check your destination
host... address.
Reply from... Destination is responding.
Request timed out... Destination not responding.

Continuous Ping

Ping sends four packets of data, which isn't very good at showing problems that are
intermittent. A continuous Ping can be useful if you think there might be a problem
with cables, as you can see exactly when connection problems are occurring.

19 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

To use Continuous Ping

1. In the command line window type ping [destination address] -t"
2. Click Enter and watch for the results.
3. when you want to end the ping press Control and C together.

Path ping (Vista/Windows XP/Windows 2003 Server)

Is an enhanced form of ping that provides some of the information you would gain
from using the trace route tool. It is most useful for identifying where a connection
problem is occurring.

1. In the command line window type "path ping [address]" for example
"pathping
2. View the first set of results - which is a list of servers that your ping data
travels through to reach the destination address. Each server that is passed
through on the route is known as a 'hop'. You will see the message
"Computing Statistics for 250 seconds..." Pathping is now monitoring data
through each of the servers, looking to see if any of them are responding
slowly, or intermittently. The longer the route to the destination, the more
time will be required for the test. Once complete, you'll see a table that
shows if any of the servers are dropping packets of data. If a server is faulty
or overloaded you might see a high percentage of lost packets.

Trace route - "How does my data reach its destination?"

Trace route shows you the route your data packets are taking to reach a destination
system. Trace route results can show:

Problems with the system you are trying to connect to.

Problems with the network between you and the destination system.
Problems with your own network setup (Firewall or router problems).
20 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Trace route Responses

Response Explanation
Unable to resolve target Check your destination
system... address.
Trace complete... Trace route worked.
Request timed out... Destination not responding.
Destination network Indicates a network
unreachable...* problem.

*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 Plusnet's control.

IPCONFIG

Windows 2000/XP offer the command-line tool IPCONFIG for a quickglance 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

IPCONFIG /ALL( Figure 2.5).

When you have a static IP address, IPCONFIG does little beyond reporting your
current IP settings, including your IP address, subnet mask, default gateway, DNS
servers, and WINS servers. When using DHCP, however, IPCONFIG is also the
primary tool for releasing and renewing your IP address. Just type ipconfig /renew
to get a new IP address or ipconfig /release to give up the IP address you currently
have.

21 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

DNS Lookup - "Is my computer data going to the right place?"

DNS (Domain Name System) turns your user-friendly web addresses into the
numerical IP addresses that are used by computer systems. If you have a working
connection, but can't view popular websites like BBC or Google, then faulty DNS
settings may be the cause.

Flush DNS Cache

The first thing you should do is remove the saved DNS information in your
computer, this may now be out of date.

To Flush your DNS Cache

1. In the command line window, type "ipconfig /flushdns"

2. Click Enter.
3. Watch for the flush to complete with the message. "Successfully flushed the
DNS Resolver Cache."
4. Retest to see if you can browse popular websites.

DNS lookups You can test to see if your DNS is working properly by doing a
DNS lookup, using the command line tool nslookup.

To do a DNS Lookup

1. In the command line window, type"nslookup [Website Address]" for

example "nslookup
2. Click Enter.
3. Check the results to see if an (IP) address is found that corresponds with the
name of the website address. If your DNS is not working properly, nslookup
won't be able to return an IP address.

22 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Netstat - "what's my computer connecting to?"

Netstat tells you what your computer is connected. This makes if useful for seeing
if your computer is connected to servers that you don't know about. If you think
that your computer is infected with "Spyware" or certain types of virus Netstat may
help you find them out.

To run Netstat

1. In the command line window, type "netstat -a"

2. Click Enter
3. View the list of connections on your PC.

Different programs and processes may connect to remote computers. In most cases
there's nothing to worry about. The two things to look for are the numbers after the
colon (port numbers), and the Foreign Addresses.

Ports are the doorways that different computer programs use to send data over a
network. For example, browser traffic uses Port 80, email uses ports 25 and port
110. If you are worried that your system has been infected with a Trojan, or similar
virus, you may be able to spot the connection it uses. The port numbers that are
associated with Spyware and Trojans are changing all the time - its always best to
make sure you have updated anti-virus and firewall software running on your
computer.

Foreign addresses are the systems that are connected to your computer that appear
to be remote. While it can be hard to know what to look for, one solution is to run
netstat while no programs are running and save the results to compare later.

Telnet - "Can I connect to it?"

23 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Telnet is a program that allows you to access and use other computers remotely. It
has lots of uses for testing problems because it can let you manually test Internet
services as if you were a browser or email program. You can then see if a problem
you have is due to the service or your computer setup. You can use telnet to
confirm that a service like email is accepting connections.

A telnet client is included with most versions of Windows, though in Windows

Vista it has to be added as follows:

1. Click Start > Control Panel > Programs

2. Then Turn Windows Features on or off.
3. In the list, scroll down and select Telnet Client.
4. Click OK to start the installation.

Netshell - "One-stop network check"

Netshell is a tool that allows you to check that Windows is properly setup for
networking. It can test many different aspects of your network connection,
depending on what you have got setup on your system.

To use Netshell

1. In the command line window, type "netsh diag gui".

2. Click Enter.
3. A Network Diagnostics Window will open.
4. Click Scan your system to begin testing, or Set scanning options to change
which things you want Netshell to test.

Tracert command
The tracert command lists the number of hops needed to connect to a target
computer. Each hop represents a device that the packets of data must travel
through in order to continue along the network. On the Internet, this is a usually a
router. When testing in a LAN environment, there is usually just one hop.

Validating Network Cabling

24 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Network Cable Testing

Network Cable Testing, the physical and electrical testing of Network cabling, is a
very specialist area. As a Network Manager you have to deal with cable faults,
broken wires, incompatibilities and a host of other cable related issues. What can
you do? What do you need to test for?

The design and installation of network cabling can be extremely complex. A whole
host of factors have to be taken into account, network speed, length of cables,
avoiding architectural features or electrical interference, and many more.

Network Speed
10M, 100M, Gigabit? Who knows? Something that reports network speed is very
useful. Link testing can be used to identify the network speed. Its useful to find
out additional network information using DHCP.

If you are running Gigabit on your network you need to ensure that your cabling is
up to the Cat5e standard, the older Cat5 standard is fine for 100M but needs careful
checking if you intend to run Gigabit. Many organizations only discover this too
late.

Cable Length

The longer the cable the more the signal is reduced (attenuated), ultimately to the
point where no signal gets through. Measuring cable lengths to check that they are
within specification is important and remember that attenuation increases with
network speed, so your new faster network may have cable lengths that were fine
on your old network, but are now too long.

Wire mapping

Are you sure that pin 1 is really connected to pin 1 at the other end? You need to
check this to be certain. What about short circuits, crossed wires, split pairs etc.?
Most of these faults can be detected using a continuity test, but some, like split
pairs, require a signal to be sent down the wire. Something that can send a signal or
tone is required.

25 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

You can also use tone generators for signal tracing and cable identification.

Connectivity Testing

Ping tests confirm connectivity across the network, to PCs and Network Cards.

Voltage on the wire

Phantom voltages or electrical noise can cause faults on the network. Its useful to
be able to check where voltage are occurring, either intentionally or not.

Conclusion

As a Network Manager you will be expected to deal with day to day cabling
problems. You probably cant justify the cost of the specialist testers used by
cabling professionals, but a simple testing kit will allow you to check for the most
common problems, save you time chasing phantoms, and help you resolve issues
faster and more efficiently.

How to Test an Ethernet Cable for Continuity

The easiest and most informative method to test the continuity of an Ethernet cable
involves purchasing an affordable device called a continuity tester. A basic model
will test the continuity of Ethernet and coaxial cable. A continuity tester is not
absolutely necessary, but highly useful if you need to test Ethernet cables
frequently. There is some important terminology you should understand before
proceeding. Jacks are where the ends of the cable plug into a computer or other
networking device. Plugs are the small plastic connectors on the the end of the
cable. Pairs refers to color-coded strands of wires that are matched together, and
cable housing is the plastic insulation that covers and protects these wires.

Instructions

1. Testing Using a Continuity Tester

1 Power on the continuity tester.

2 Insert one of the cable plugs into the tester and the other into the
terminator.

26 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

3 Look at the display of the network tester. Depending on your

continuity tester, at a minimum it will indicate if there is a break in the
cable and, should it include this feature, which cable pairs the break
affects.

2. Testing Continuity Without a Continuity Tester

1 Power the computer and a router or other networking device on.

2 Plug the cable into the network port on the computer and the other
end into the networking device.

3 Look at the back of the computer where the cable is plugged into the
Ethernet jack and see if any flashing green or yellow lights come on.
These lights indicate if the computer is sending or receiving any
information. If the lights are lit or flashing, the cable continuity is
good. If not, replace the cable.

4. Resolving NIC Problem

The Ethernet Adaptor or the Network Interface card (NIC) is the piece of hardware
that makes it possible to access the internet. The Network Interface card is also
essential for PC-to-PC communication and other forms of computer interactions
that involve two or more devices such as Bluetooth and Infrared. Frankly, two
computer systems can only share a file with each other because they have a
network Interface Card that enables them to communicate with each other --
sending and receiving signals. If a device must communicate with another device,
it needs a NIC. Your broadband modem and printer use the NIC technology.

Diagnose NIC Problems

The Network Interface Card must be functioning for your PC to be able to
communicate on a network. When network problems occur, the NIC is less likely
to be the cause than infrastructure such as cables, routers and hubs. All problems
below assume that you are experiencing a complete or intermittent failure of
network connectivity.

Common problems with NIC and respective Troubleshooting

The cable is connected but there is no light on the NIC

Unplug and replug the network connector into the NIC and at the other end.

27 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Check that the other end of the cable is connected to a device that is powered
on.
Try switching the cable to a different port if available.
Try a different network cable.
Check the control panel in Windows to make sure the card is recognized and
working.

The data collision light is frequently or continuously lit

Check that the far end of the network cable is connected to the proper port,
or try a different port.
Check that your PC is not using an IP address that is already in use on your
network.
Make certain that your PC is not using a name that is already in use by
another PC on the network.

The lights on the NIC are normal but I cannot connect to the network

Make certain that other network devices are powered on.

Make certain that your PC is configured with the proper Workgroup or
Domain name.
Check that your PC is not using an IP address that is already in use on your
network.
Make certain that your PC is not using a name that is already in use by
another PC on the network.
Allow up to 20 minutes for network polling to identify all available
resources.
Check the network cable connections and use a different port if available.
If Windows is configured for more than one NIC, make certain that the
correct one is being used for this network.

7. Analysing Server and Client performance

What Factors that affect performance of a network?

The data path between any two computers involves dozens, sometimes thousands,
of hardware and software devices. Any one of these may have a substantial impact
on performance.

At any given time there is likely to be one factor which most directly limits the
maximum speed of a data flow. Identifying the limiting factor for each data flow
is vital to improving performance. Common factors are listed below:
28 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Factor One: Network Adapter

A network adapter is the device that physically connects your Mac to your
network. The network itself will be Ethernet (which comes in three speeds,
10Megabit, 100Mb, and 1000Mb) or LocalTalk (one speed, about 0.25Mb). Power
Macs, iMacs, and G3/G4s have at least 10Megabit Ethernet (often faster), and all
Macs with printer and modem ports can use LocalTalk. Many LocalTalk Macs can
also add Ethernet support.
Ethernet's three speeds can be deceptive, since they imply you can increased your
network speed tenfold just by purchasing a faster network adapter. Sadly, this is
not the case. A 10Megabit Ethernet adapter probably won't reach full speedabout
1.25 megabytes per secondwithout a specially optimized test system. "Real
world" performance will be more like 100-200 kilobytes per second in an average
AppleTalk network. 100Mb Ethernet will be 4-6 times faster (not 10), and 1000Mb
a few times faster still, but still not the blinding speed you might imagine.
Conclusion
Ethernet naming aside, switching to a faster adapter is usually the simplest way to improve network
speed, assuming you also get a faster hub or switch.
Speaking of which...

Factor Two: Ethernet Hub or Switch

Most Ethernet networks use a hub or switch, which serves as the central connection point and moves data
around. Like the network adapters, they have three speed ratings, 10Mb, 100Mb, and 1000Mb.Your
switch must support the same speed as your network adapters to use it on your network (most support
multiple speeds for this reason). You should use a hub or switch that supports your full range of network
adapter speeds, so you don't limit the higher-speed computers.
Switches perform more efficiently than hubs in high-traffic networks, so it's a good idea to use a switch if
your network will pass data between three or more computers simultaneously.
Conclusion
your hub or switch must support your highest network speed to make use of it, but model and make
should make relatively little difference in speed.
Factor Three: Network Software
Your Mac's network adapter uses software to translate the network data into a form the computer can
understand and vice versa. The newer the software is, generally speaking, the better the network adapter's
performance will be. Software updates usually fix bugs and improve translation, so check the adapter's
web site regularly for updates (this includes Apple, who updates their Ethernet software from time-to-
time).

Conclusion
The effects of software vary widely. Speed increases come from quashed bugs that hindered network
adapter performance or improvements to the network translation.
Factor Four: Motherboard Speed
Like your skeleton, a Mac's motherboard defines what it's capable of. The motherboard's processing speed
has inherent limits that include (to a degree) network performance. Newer Macs have faster motherboard
speeds, which in turn help network speed (or at least hinder it less).

29 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Conclusion
A faster motherboard generally means faster everything, including network performance. Upgrading the
motherboard, however, means getting a new Mac.

Factor Five: Hard Disk Throughput

Disk performance (how much information you can read or write from the disk in a second) is often the
primary bottleneck to network performance. Since most network data represents a file, your hard disk has
to read the source file and another disk must write it to complete the data transfer. Maximize disk
throughput on the networked Macs and your network performance should see a marked improvement.

You can improve your disk performance by using a faster disk, which makes more information available,
and a more efficient disk interface, which processes more information at once. Generally, newer hard
drives are faster, up to 10K RPM and more. Interfaces, including SCSI, IDE, and FibreChannel, have
become more efficient with time. New Macs use IDE for their built-in hard disks, but you can add other
support with an expansion card. Get a high-speed disk interface with a high-speed drive and you're almost
certain to notice the change on your network (and everywhere else).

Conclusion
Upgrading your disk drive and interface will almost certainly increase network performance, although the
performance increase will be relative to what you used previously.

Factor Six: Network Server

Most home or small offices use peer-to-peer Mac networking, since it's easy to use and comes with the
Mac OS. If you can justify the expense, however, purchasing actual network server software (Apple's
AppleShare IP) will lift your performance significantly. The downside is cost, since you need to purchase
the software and possibly dedicate a computer to running it.

Conclusion
Using AppleShare IP will improve network throughput notably, but regrettably does the same to your
wallet.

Factor Seven: AppleTalk vs. TCP/IP

AppleTalk is less efficient (and therefore slower) than some other network formats like TCP/IP. For home
and small office users, AppleTalk makes up for the speed drop in convenience. Mac OS 9 supports
AppleTalk-over-TCP/IP, which improves things somewhat, but still makes a speed tradeoff for the
convenience of the drag-and-drop Desktop functionality.

Conclusion
AppleTalk is (somewhat) slower than other options, but makes up for it in convenience.

Factor Eight: Shared Internet

The performance of your network is limited somewhat by outside factors, such as an Internet connection.
If you have a cable or DSL modem, for example, you have little control over how quickly Internet data
comes and goes (your cable or DSL company sets that limit, either by availability or choice). The typical
limit on an Internet connection is around 200 kilobytes, which is easily within the range of a 10Mb
Ethernet network adapter.

30 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Conclusion
Sharing an Internet connection has its own speed limitations that are out of the home network user's
control.
Network Bottleneck
What does Network Bottleneck mean?
A network bottleneck refers to a discrete condition in which data flow is limited by
computer or network resources. The flow of data is controlled according to the
bandwidth of various system resources. If the system working on a network is
delivering a higher volume of data than what is supported by the existing capacity
of the network, then a network bottleneck will occur.

A common computing bottleneck culprit is network data interruption caused by

microprocessor circuitry or TCP/IP. Bottleneck is also known as a hot spot.
A bottleneck occurs when bandwidth is unable to accommodate large amounts of
system data at designated data transfer rate speeds. Road traffic is a common
bottleneck analogy. For example, bottlenecking is inevitable when only one of two
busy road lanes is passable.
Bottlenecks are caused by multiple factors, including:

Hardware components, like CPUs

Graphical processing units
RAM memory

How to Find a Network Bottleneck

If you've ever wondered why sometimes when you connect to a website it's fast
and other times it's slow, there is an answer. Your request may go through many
routers and switches before it gets to its destination, and sometimes some of the
network switches or routers could be having problems. This will cause the
slowness. You can check to determine what is causing your particular network
bottleneck in a few steps.

Instructions:
1 Right-click an empty spot on your system tray -- usually at the bottom of your
computer screen -- and select "Task Manager."
2 Click the "Networking" tab.
3 Click "View" in the options above the tabs and click "Select Columns."
4 Click to check "Bytes Sent/Interval" and "Bytes Received/Interval." Click "OK."

31 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

8. Proactive Network Maintenance

Proactive Network Maintenance
- Common preventive maintenance techniques should continually be performed for a
network to operate properly.
- Heat is a big problem for network devices, especially in the server room. Network
devices, such as computers, hubs, and switches, do not perform well when over-heated.
Excess heat is generated by dust and dirty air filters. Dust impedes the proper flow of
cool air and sometimes even clogs fans. Keep network rooms clean and change air filters
often.
- Preventive maintenance involves checking the various components of a network for wear.
Check the condition of network cables because they are often moved, unplugged, and
kicked. Many network problems can be traced to a faulty cable. You should replace any
cables that have exposed wires, are badly twisted, or are bent.
- Label the cables. This practice will save troubleshooting time later. Refer to wiring
diagrams and always follow your company's cable labeling guidelines.
- Test devices on a regular basis.
- AC power adapters should be checked regularly.
- The uninterruptible power supply (UPS), which provides backup power, should be tested
to ensure that you have power in the case of an outage. Before installing a new UPS, plug
it into a power source to charge the batteries. The initial charge time is usually 12 hours
or more. Follow the manufacturer instructions for unpacking the UPS and preparing it for
use.

Troubleshoot a network
- Network issues can be simple or complex. To assess how complicated the
problem is, you should determine how many computers on the network are
experiencing the problem.
- If there is a problem with one computer on the network, start the
troubleshooting process at that computer.
- If there is a problem with all computers on the network, start the
troubleshooting process in the network room where all computers are
connected.
- As a technician, you should develop a logical and consistent method for
diagnosing network problems by eliminating one problem at a time.
- After completing this section, the students will meet these objectives
- Review the troubleshooting process.
- Identify common network problems and solutions.

32 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Network Troubleshooting Process

Step 1 Gather data from the customer
Step 2 Verify the obvious issues
Step 3 Try quick solutions first
Step 4 Gather data from the computer
Step 5 Evaluate the problem and implement the solution
Step 6 Close with the customer

1. Gather Data from the Customer

Start troubleshooting by gathering data from the user. Record this information in a
work order
Start with open-ended questions with customers when evaluating a network problem.
Open-ended questions will allow the customer to describe the problem. Examples of
open-ended questions:
What problems are you experiencing with your computer or network?
What software has been installed on your computer recently?
What were you doing when the problem was identified?
What error messages have you received on your computer?
What type of network connection is your computer using?
Closed-ended questions will direct the customer to provide critical answers. Examples
of closed-ended questions:
Has anyone else used your computer recently?
Can you see any shared files or printers?
Have you changed your password recently?
Can you access the Internet?
Are you currently logged into the network?
When a customer is not able to accurately describe the problem, there are other
ways to evaluate the situation in subsequent steps in the troubleshooting process.
2. Verify the Obvious Issues
Review the obvious network issues, with your customer.
The questions should be at a level of difficulty that the customer will easily
understand.
Follow a step-by-step procedure and make sure to document all answers and
steps you take.
Some obvious issues to check:
Physical connections - Check that the network cables are properly connected.
To simplify the troubleshooting, connect the problem computer directly into
your DSL or cable modem.

33 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Link light - If a cable is not connected properly or if a NIC is improperly

installed or configured, the LED link lights on the NIC will not light.
Wireless signal strength - Check the wireless access point signal strength in
your network client software. If a very low signal strength is apparent, move the
computer closer to the wireless access point. Move cordless telephones and
microwave ovens that can cause interference with the signal. Turn off any other
devices that use radio waves to reduce interference.
IP address - Use the ipconfig tool to make sure that the computer has a valid, unique
IP address. Check for errors in the subnet mask and default gateway address. If the
problem is not fixed by a quick review of the obvious issues, then a more detailed
investigation into the problem is warranted.
3. Try Quick Solutions First
The next step in the troubleshooting process is to try quick solutions. If checking
the obvious issues did not solve the problem, you should then attempt some quick
solutions. Here are some examples of quick network solutions:
Re-enable Network Connections - Sometimes a problem in the
hardware or the software can cause a network connection problem. To
do so, follow this path: Start > Control Panel > Network
Connections
Reboot - A quick solution that seems to work in many situations is a
simple reboot of the network device. A simple reboot will clear the
contents of RAM and give the device a clean start. If the problem goes
away after a reboot, then it was probably a software problem. If the
problem occurs again, it is probably a hardware problem such as a
malfunctioning RAM chip.
Contact the ISP/Network Administrator - If all of the equipment
that the customer has is working properly, but there is still no
connection to the Internet, contact the customer's ISP or the network
administrator.
It is not always possible to solve the problem with a quick solution. To proceed
troubleshooting the problem, you will need to gather information from the computer.
4. Gather Data from the Computer
The next step is to inspect the computer. Data gathered from the computer can be used
to confirm the data obtained from the customer. The data can be used to provide
additional insight and direction.There are several software tools available that a
technician can use to test the network. Each of these utilities will provide information
that can help narrow down the possible problems on the network:
Ping is used to check network connectivity. It sends a packet to the
specified address and waits for a reply.

34 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Nslookup is used to query Internet domain name server. It returns a

list of hosts in a domain or the information for one host.
Tracert is used to determine the route taken by packets when they
travel across the network. It shows where communications between
your computer and another computer are having difficulty.
Net View is used to display a list of computers in a workgroup. It
shows the available shared resources on a network.
5. Evaluate Problem & Implement Solution: If the network problem still exists after quick
solutions have been implemented, you must complete additional research to identify
other possible solutions. You should prioritize the possible solutions from the easiest
to implement to the most difficult to implement.
Evaluate each solution and implement it individually. If a proposed solution
doesn't correct the problem, reset the computer back to the original state and
try another proposed solution. If you make two or more changes without
solving the problem, you may make it more difficult to solve.
6. Close with the Customer: After repairs to the network have been completed, complete
the work order and close with the customer.
If possible, verify the network solution with the customer.
Demonstrate how the repairs have fixed the problem. Have your
customer test the solution.
Complete the work order and submit documentation for invoicing.
Include the steps done, the solution, and the time needed for the repair in your final
documentation. This documentation should be maintained by the customer in case this
problem happens again. Record everything that took place in your own notes.
Information from each repair is very useful for future troubleshooting.
Identify common network problems and solutions
Network problems can be attributed to hardware, software, connectivity issues, or some
combination of the three. You will resolve some types of network problems more
often than others. Common printer problems and possible causes to consider:
Problem: Computer is not able to connect to a popular website.
Check DNS settings, hardware and/or software firewall settings.
Problem: Computer has an IP address of 169.254.x.x.
Check to make sure the DHCP server is operational and can be pinged.
Problem: Computer is not able to connect to the network.
Check for loose network cables.
Problem: Computer is not able to print using the network printer.
Check user permissions and status of network printer.

35 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

Self Check
1. Check your own computers configuration. What commands can you use?
Keep a record of these configurations for more activities to follow.
2. Check your own computer connection to the network. What commands can
you use?
3. Use the ping command to find other computers on your network. Test your
connection to the DNS server, Default Gateway, and WINS server, if they
are available on your network.
4. Use the ping command to find other computers that are not on your network.
5. Use the tracert command to find out how many routers you need to go
through to access a website.
6. What does the acronym PING stand for?
7. What is the PING command used for?
8. What does the acronym DNS stand for?
9. What is the purpose of DNS?
10.What does the acronym TCP/IP stand for?
11.List the general order of events for testing network connectivity.
12.What is involved in connecting a computer to a Local Area Network (LAN)?
Feedback
1. You should have used either of the following commands to check your
computers configuration. Note that the second command will display more
information:

ipconfig
ipconfig/all

2. The results you get will vary, depending on your IP Address:

ping 127.0.0.1 This will give a very fast response, and just proves that IP
is installed. It is fast because the network adaptor or dial-up adaptor is not
even used.
ping x.x.x.x, where x.x.x.x is the IP address of your own computer.
ping NameOfComputer, where NameOfComputer is the actual name of your
computer. For example, in Windows, this name can be found from going to
Start, Control Panel, System Properties. Or, from the ipconfig/all
command, it is beside Host name.

3. Use the results from the command ipconfig/all to enter the correct IP address.

36 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

ping x.x.x.x, where x.x.x.x is the IP address of the computer you wish to
view.
ping NameOfComputer and type in the name of the computer you wish to
view, rather than its IP address.

4. ping AddressOfWebsite and type in the address of the website you wish to view
rather than its IP address. For example:

ping www.tafe.nsw.edu.au
ping x.x.x.x, where x.x.x.x is the IP address of the machine hosting the web
server. To determine the IP address of a machine hosting the website, just
ping the domain name, and the ping reply will give you the IP address it is
actually pinging after resolving the name.

5. Tracert AddressOfWebsite and type in the address of the website you wish to
view rather than its IP address. For example:

tracert www.tafe.nsw.edu.au
ping x.x.x.x, where x.x.x.x is the IP address of the website page. You will
probably not be able to find this, but in some cases when you first open a
website page, the IP address may be displayed in the status bar of your
computer.

6. PING stands for Packet Internet Groper.

7. The PING command is used to check connectivity to the computer you are
pinging. For example, the command ping 192.168.0.1 will send a response back
if it can find the computer on the network with the IP address of 192.168.0.1.

The response will send back a time out response if the computer or website is not
found.

Another example is ping www.abc.com.au. This ping command will firstly

use DNS to resolve the name www.abc.com.au to an IP address, then ping
the machine at that IP address. That is, the response will always come from
the machine, not the website or page. We will still get a response from the
machine if it is up and running. The web server itself could be down.

This way we know if we cant get a page on our browser, but we can still
ping the name, that everything is working except the actual web server.

37 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

8. Domain Name System (note that Server and Service are also used.)
9. DNS translates domain names into the numeric IP address so the computer
systems can understand it.
10. The acronym TCP/IP stands for Transport Control Protocol/Internet Protocol.
11.

1. Check all physical connections: cables into the back of the computer, cables
into hubs, switches and routers.
2. Check the cables themselves; they may be damaged or incorrectly wired, or
somebody could have introduced an unlabelled crossover cable into the
network room.
3. Check that all drivers are installed for the network card.
4. Check that the network client software is installed.
5. Check all the IP configurations on the computer. This will include, IP
address (with unique host portion), subnet mask, DNS, default gateway and
WINS.
6. Check that the computer has a unique name on the workgroup/domain.
7. Check that the correct name of the workgroup or domain is entered.

In summary: these do not need to be in this exact order you should however
specify:

Physical connections
All IP configurations and related software.
Name of the workgroup/domain.

12.

To connect a computer to a LAN:

1. Check physical connections that the network card and cables are secured,
and the network card driver is installed.
2. Check the cables themselves (as above); they may be damaged, or
incorrectly wired, or somebody could have introduced an unlabelled
crossover cable into the network room.
3. Check that the network client is installed.
4. Check that the IP address is entered along with the correct subnet mask.
5. Check that the workgroup the computer is a member of is entered correctly.
6. If others need to access files or a printer attached to the computer, then
install the printer: File and Print service.
7. If the network is configured on a Domain, then check:
38 | P a g e P r e p a r e d B y H a f t a m u H a i l u
 MAICHEW POLYTECHNIC COLLEGE
DEPARTMENT OF INFORMATION TECHNOLOGY

a. The DNS address

b. if DHCP is enabled if required or that the IP address and subnet mask
are correctly entered for the network.
c. WINS address if connecting to older versions of Windows; WINS
does the equivalent of DNS for older Windows versions.

39 | P a g e P r e p a r e d B y H a f t a m u H a i l u