MODULE TITLE:

Identifying and Resolving

Network Problems
 Troubleshooting network problems
• Troubleshooting network problems can be a frustrating
experience, whether you're dealing with one PC or the
entire ball of wax.
• This is because today's networks are so complicated
that the point of failure could be virtually anywhere.
• Worse yet, your network could contain multiple points
of failure, resulting in confusing symptoms that are
hard to diagnose.
 Where can a network fail?

• When you're trying to troubleshoot something as

complex as a network, it's often best to take what you
know about the problem and gradually narrow down
the possible causes.
• With this in mind, we'll begin with simple problems
and work toward more complicated ones.
• Basically, only four things can cause a network to fail:
• A problem with the server
• A problem with a hub, router, bridge, and so on

• A problem with the cabling

• A problem with a workstation

• Once you figure out which of these four items is causing your problem, you
can begin narrowing your focus toward subcomponents.
• For example, suppose you've determined that you have a cable problem.

• You've eliminated three quarters of your network components from the list of
possible failures.
• Next, you'll want to investigate if you have a break in the cable, if an end is
loose, if you have a missing terminator, or if you have some other problem.
Let's examine the steps you'll follow in the troubleshooting process.
A starting point
• The very first thing you need to find out is which PCs
are affected.
• Are you having problems with one PC, several PCs, or
every computer on the network?
Problems with a single PC
• If a problem is occurring only with a single PC, you've
just narrowed the cause of your problem considerably.
• The next question you should ask is, "Has this PC ever
worked before at this location?" If it has worked
before and you know that nothing has changed in the
configuration, then a component may be unplugged, a
cable may be broken, or a network card may have
gone out.
• On the other hand, if the PC is brand-new, chances
are good that it's experiencing a configuration error.
• In a situation like this, your next step should be to
plug a known good laptop computer into the network
connection currently used by the failing PC.
• If the laptop connects to the network successfully,
you know there are no cable breaks or problems with
the hubs or routers the problem is with the PC itself.
• If the laptop also fails to connect, you've obviously
got a cable problem or a problem with a switching
device (such as a hub or router).
Problems with several PCs
• If you're having problems with several PCs, you need to
consider which PCs are malfunctioning.
• If they're all new, you've probably got a configuration problem.
• On the other hand, if all the PCs were working previously, you
most likely have a problem with a switching device or a cable
segment.
• At this point, you should determine what the failing PCs have in
common with one another but not with the rest of the network.
• Many times, when multiple PCs fail simultaneously, a hub has
gone bad or a cable connecting one hub to another hub has gone
bad.
• You should check whether all the PCs share a common hub or
are attached to the same cable segment.
Problems with the entire network
• If no PCs on your network can log on, you've
probably got problems with the server functioning
as your primary domain controller. You should go
to this server to begin the troubleshooting process.
Troubleshooting a PC
• Because of the complexity of PCs and our space
limitations, it's impossible for us to provide a
comprehensive guide to troubleshooting a PC.
• However, we can show you how to work through
some of the more common network problems.
Protocol mismatches
• As you may know, in order for PCs on a network to communicate,
they must share a common protocol.
• A protocol is a language that the computers on a network use to
speak to one another.
• If you notice that a workstation can see only some of the other PCs
on your network, there's a chance you may have a protocol
mismatch.
• To solve this problem, begin by double-clicking the Network icon
in Control Panel.
• When you see the Network Properties dialog box, select the
Protocols tab, as shown in Figure A.
• Then, compare the protocols listed for this PC with the protocols
installed on a PC it can't communicate with.
• If the protocols match, the PCs should be able to communicate
with each other.
• The NetBEUI protocol is an exception to this rule.
NetBEUI isn't a routable protocol.
• If a router is located between two PCs using
NetBEUI and you haven't made special
provisions, the PCs won't be able to
communicate.
• The easiest solution to this problem is to install
NWLink IPX/SPX or TCP/IP.
 ord ab
• Wit ou t T C
h th e i P/IP
TCP/IP ncreasing p
i s b e i o p u l ar
• Bec ng use ity of t
a us e o d more h e In t e
to trou f t hi s g often. rnet,
blesho rowing
• If y ot som u s a ge ,
o u s us e c om m w e'l l s
p e c o n ho w y
TCP/IP t t ha t y TCP/IP o u ho w
, the fi o u h av proble
own IP r s t th i n e a prob ms .
addres g you le m w
• If th s. should i th
e PING d o is P
• How returns ING y
ever, th , th e n T o ur
functio is mea C P /I P
nality ns only i s fu n c
c an co d oe s n ' that th t i o na l .
mmun t n e ces e proto
icate w sarily co l i s
ith the mean t
rest of h at T C
th e w o P/IP
rld.
• If the malfunctioning PC can successfully PING
itself, you should PING the address of another PC
on the same network segment as the
malfunctioning PC.
• Doing so will test your network card. If the PING
fails, the network card is malfunctioning.
• If the PING is successful, PING the same PC
using the PC's computer name rather than its IP
address.
• If this PING fails, you probably have a problem
with your WINS or DNS configuration.
• If you can successfully PING a PC by name, it's
time to PING a PC that's either on a different
network segment or in the outside world.
• For example, you might PING
http://www.xpressions.com. If this PING fails
but previous PINGs have been successful, you
probably have either an incorrectly configured
default gateway or a problem with your router.
• However, if other PCs on the segment are
functioning correctly, the problem is probably
the default gateway rather than the router.
Testing a network card
• If you suspect that you have a bad network card, you'll
need to check the card's configuration.
• To do so, open Control Panel and click the Network icon.
• When the Network Properties dialog box opens, select the
Adapters tab and double-click your network adapter.
• Many plug-and-play network cards come with special
software that you can use to manually configure the card.
•  If your network card doesn't use configuration software, it
may have jumpers on the card that control these settings.
• If your card uses jumpers, consult the manual that came
with the card to learn how to use the jumpers to make the
card's settings match the settings configured through
Windows NT.
 THE FIVE MOST COMMON NETWORK
PROBLEMS
1. 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
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.
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.
4. Software Problem: Network problems can often
be traced to software configuration such as DNS
configuration, WINS configuration, the registry etc.
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.
 Troubleshooting server problems
• Many people feel intimidated when it comes to
troubleshooting a server.
• However, you should keep in mind that Windows NT
Server and Windows NT Workstation function
identically.
• If you're capable of fixing a workstation, you're equally
capable of fixing a server.
• If your server is having trouble accessing the rest of the
network, you should apply the same troubleshooting
techniques we've discussed for troubleshooting a
workstation.
•Network Diagnostic Tool (NDT)
•The Network Diagnostic Tool (NDT) is a client/server program
that provides network configuration and performance testing to a
users desktop or laptop computer.
•The system is composed of a client program (command line or
java applet) and a pair of server programs (a webserver and a
testing/analysis engine).
•Both command line and web-based clients communicate with a
Web100-enhanced server to perform these diagnostic functions.
•Multi-level results allow novice and expert users to view and
understand the test results.
• Several studies have shown that the majority of network performance problems
occur in or near the users’ desktop/laptop computer.
•These problems include, but are not limited to, duplex mismatch conditions on
Ethernet/FastEthernet links, incorrectly set TCP buffers in the user’s computer, or
problems with the local network infrastructure.
•The NDT is designed to quickly and easily identify a specific set of conditions that
are known to impact network performance.
• A multi-level series of plain language messages, suitable for novice users, and
detailed test results, suitable for a network engineer, are generated and available to
the user.
• Finally, the test results may be easily emailed to the appropriate administrator to
assist in the problem resolution phase.
• The NDT consists of several components. Both client and
server processes are used to perform a specific set of tests.
•The server processes include a basic web browser
(fakewww) to handle incoming web based client requests
•. The server also runs a second process (web100srv) that
performs the specific tests needed to determine what
problems, if any, exist.
•The web100srv process then analyzes the test results and
returns these results to the client.
•Server, workstation and network configuration
•Workstations
•  Computers that humans use are broadly categorized as
workstations.
• A typical workstation is a computer that is configured with
a network interface card, networking software, and the
appropriate cables.
•Workstations do not necessarily need large storage hard
drives, because files can be saved on the file server.
•Almost any computer can serve as a network workstation.
•File/Network Servers

•   One or more network servers is a part of nearly every local area network.

•These are very fast computers with a large amount of RAM and storage space,

along with a one or more fast network interface card(s).

•The network operating system provides tools to share server resources and

information with network users.

•A sophisticated permissions-handling system is included, so that access to sensitive

information can be carefully tailored to the needs of the users.

•For small networks, a single network server may provide access control, file

sharing, printer sharing, email, database, and other services.

• The network server may be responding to requests from many
network users simultaneously.
• For example, it may be asked to load a word processor program to
one workstation, receive a database file from another workstation,
and store an e-mail message during the same time period.
• This requires a computer that can store and quickly share large
amounts of information.
• When configuring such a server, budget is usually the controlling
factor.
• The following guidelines should be followed:
– Fastest processor(s)
– Large amount of RAM
– multiple large, fast hard drives
– Extra expansion slots
– Fast network interface card(s)
• Network Configuration
• When you initially installed Slackware, the setup program
invoked the netconfig program.
• netconfig attempted to perform the following functions for
you:
• It asked you for the name of your computer, and the
domain name for your computer.
• It gave a brief explanation of the various types of
addressing schemes, told when they should be used, and
asked you which IP addressing scheme you wished to use
to configure your network card:
– Static-IP
– DHCP
– Loopback
– It then offered to probe for a network card to configure.
• netconfig will generally take care of about 80% of the
work of configuring your LAN network connection if
you will let it.
• Note that I would strongly suggest that you review your
config file for a couple of reasons:
1. You should never trust a setup program to properly
configure your computer. If you use a setup program,
you should review the configuration yourself.
2. If you are still learning Slackware and Linux system
management, viewing a working configuration can be
helpful. You'll at least know what the configuration
should look like. This will allow you to correct
problems due to misconfiguration of the system at a
later date.
• TCP/IP Configuration
• At this point, your network card should be physically
installed in your computer, and the relevant kernel
modules should be loaded.
• You will not yet be able to communicate over your
network card, but information about the network
device can be obtained with ipconfig -a.

# ipconfig -a
eth0 Link encap:Ethernet HWaddr 00:A0:CC:3C:60:A4
UP BROADCAST NOTRAILERS RUNNING
MULTICAST MTU:1500 Metric:1
• If you just typed /sbin/ipconfig without the -a suffix,
you would not see the eth0 interface, as your
network card does not yet have a valid IP address or
route.
• While there are many different ways to setup and
subnet a network, all of them can be broken down
into two types: Static and Dynamic.
• Static networks are setup such that each node (geek
lingo for thing with an IP address) always has the
same IP address.
• Dynamic networks are setup in such a way that the
IP addresses for the nodes are controlled by a single
server called the DHCP server.
• DHCP
• DHCP (or Dynamic Host Configuration Protocol), is a
means by which an IP address may be assigned to a
computer on boot.
• When the DHCP client boots, it puts out a request on the
Local Area Network for a DHCP server to assign it an IP
address.
• The DHCP server has a pool (or scope) of IP addresses
available.
• The server will respond to this request with an IP address
from the pool, along with a lease time.
• Once the lease time for a given IP address lease has
expired, the client must contact the server again and
repeat the negotiation.
• The client will then accept the IP address from the
server and will configure the requested interface
with the IP address.
• There is one more handy trick that DHCP clients
use for negotiating the IP address that they will be
assigned, however.
• The client will remember it's last assigned IP
address, and will request that the server re-assign
that IP address to the client again upon next
negotiation.
• If possible, the server will do so, but if not, a new
address is assigned. So, the negotiation resembles
the following:
Client: Is there a DHCP server available on the LAN?
Server: Yes, there is. Here I am.
Client: I need an IP address.
Server: You may take 192.168.10.10 for 19200 seconds.
Client: Thank you.
Client: Is there a DHCP server available on the LAN?
Server:Yes, there is. Here I am.
Client:I need an IP address. The last time we
talked, I had 192.168.10.10;May I have it again?
Server:Yes, you may (or No, you may not: take
192.168.10.12 instead).
Client: Thank you.
• Static IP
• Static IP addresses are fixed addresses that only
change if manually told to.
• These are used in any case where an administrator
doesn't want the IP information to change, such for
internal servers on a LAN, any server connected to
the Internet, and networked routers.
• With static IP addressing, you assign an address and
leave it at that.
• Other machines know that you are always at that
certain IP address and can contact you at that address
always.
• /etc/rc.d/rc.inet1.conf
• How to Check Network Interface Card (NIC) Status Using Windows 7
or Vista
•Whether the network interface card (NIC) is part of your PC’s
motherboard circuitry or attached as an expansion card, you can inspect
its status by using the Device Manager in Windows 7 and Windows
Vista.
•Follow these steps to check on the NIC hardware:
1.Open the Control Panel.
2.Open the Device Manager.
o In Windows 7, choose Hardware and Sound, and then choose the
Device Manager link beneath the Devices and Printers heading.
o In Windows Vista, choose Hardware and Sound, and then choose
Device Manager.
3. Expand the Network Adapters item to view all network
adapters installed on your PC.
 You most likely have only one
4. Double-click the Network Adapter entry to display your PC’s
network adapter’s Properties dialog box.
 The General tab in the Properties dialog box lists the device
status. Any problems detected by Windows appear in that
message box. Otherwise, the message reads This device is
working properly.
5. Click the Resources tab in the Properties dialog box.
6. Check the Conflicting Device list.
 You should see no conflicts listed. If not, the
source of the conflicts must be resolved.
Generally, it would mean removing whatever
other device is conflicting with the NIC or
reconfiguring the device.
7. Click OK to close the Properties dialog box.
8. Close the Device Manager window as well as the
Control Panel.
•The first solution for fixing a bad NIC is first to view
the suggestions listed in the Properties dialog box.
•When those suggestions aren’t helpful, one alternative is
to use another NIC.
•If you have a NIC on an expansion card, simply remove
the old expansion card and install a new one.
•When the NIC is on the motherboard, your alternative is
simply to install a second NIC as an expansion card.
•For a laptop, get a USB NIC, either wired or wireless, when the laptop’s
NIC fails.
o You will probably know when the NIC isn’t working properly before you even
open its Properties dialog box. That’s because bum devices are flagged with a
yellow icon in the Device Manager.
o If your PC came with a NIC diagnostics tool, using it would be, obviously, a
better option for checking on the NIC as well as for testing the NIC’s
condition. Check the Start button’s All Programs menu. Look for a folder
(submenu) specific to the NIC manufacturer, such as Intel, Netlink, or Linksys.
o Yes, you can have multiple network adapters in a PC. For example, a laptop
computer would have both wired and wireless NICs. When you have multiple
NICs, you can repeat these steps to review any problems or conflicts with each
of the adapters.
o To disable a NIC, open its Properties dialog box. Use
the Disable button on the Driver tab. By disabling
the device, you ensure that Windows doesn’t use it
and instead uses another NIC that functions properly.
o To deal with a hardware conflict, you must reset the
IRQ on one of the two conflicting devices. Or, you
can remove one device. See which devices can be
replaced by a comparable USB device. USB devices
don’t have the conflicts that IRQ gizmos do.
•How to Check the Network Interface Card (NIC) Status in Windows XP
•Whether your network interface card (NIC) is part of your PC’s motherboard circuitry or
attached as an expansion card, you can inspect its status by using the Device Manager in
Windows XP.
•Follow these steps to check on the NIC’s hardware in your Windows XP computer:
1.Press Win+Break to quickly summon the System Properties dialog box.
2.Click the Hardware tab.
3.Click the Device Manager button.
The Device Manager window appears.
4Expand the Network Adapters area by clicking the plus sign [+] icon.
•You see a list of all network adapters installed in your PC.
5. Double-click a network adapter entry.
•The adapter’s Properties dialog box appears. On the General tab, you see the device status.
It should say This device is working properly. If not, any specific problems are noted.
6. Click the Resources tab.
7. Review the Conflicting Device list.
No conflicts should be listed. When they are, resolve them
by looking at the source of the conflict.
8. Click the OK button to close the Properties dialog box.
9. Close the Device Manager and the Control Panel
windows.
• The first solution for fixing a bad NIC is first to view the
suggestions listed in the Properties dialog box. When those
suggestions aren’t helpful, one alternative is to use another
NIC.
• If you have a NIC on an expansion card, simply
remove the old expansion card and install a new
one.
•  When the NIC is on the motherboard, your
alternative is simply to install a second NIC as an
expansion card.
•For a laptop, get a USB NIC, either wired or wireless, when the
laptop’s NIC fails.
 You will probably know when the NIC isn’t working properly before
you even open its Properties dialog box. That’s because bum devices
are flagged with a yellow icon in the Device Manager.
 When you’re having network adapter problems in Windows XP, click
the Troubleshoot button (after Step 5) to run the NIC Troubleshooter.
 If your PC came with a NIC diagnostics tool, using it would be,
obviously, a better option for checking on the NIC as well as for
testing the NIC’s condition. Check the Start button’s All Programs
menu. Look for a folder (submenu) specific to the NIC manufacturer,
such as Intel, Netlink, or Linksys.
 Yes, you can have multiple network adapters in a PC. For example, a
laptop computer would have both wired and wireless NICs. When you
have multiple NICs, you can repeat these steps to review any problems
or conflicts with each of the adapters.
 To disable a NIC, open its Properties dialog box. Choose Disable from
the drop-down menu at the bottom of the General tab. By disabling the
device, you ensure that Windows XP doesn’t use the problem NIC and,
instead, uses another NIC that functions properly.
 To deal with a hardware conflict, you must reset the IRQ on one of the
two conflicting devices. Or, you can remove one device. My suggestion
is to see which devices can be replaced by a comparable USB device.
USB devices don’t have the conflicts that IRQ gizmos do.
•Connectivity testing with Ping, Telnet, Tracert and PathPing:
•  All of the following command line tools are accessed from the
command prompt. You can open a command prompt window by
selecting Start | All Programs | Accessories | Command Prompt.
•  You can also open the command prompt window by selecting
Start | Run - and then entering CMD.EXE into the dialog box and
pressing the Enter key or the OK button.
• Each tool in this KB is given only a very basic overview and
usage description. We would suggest that you research each of
these in more detail to learn about advanced usage.
• PING :
•  The ping command is a very simple connectivity testing tool. Ping
verifies connectivity by sending Internet Control Message Protocol
(ICMP) echo packets to a host and listening for an echo reply.
•  The ping command waits for each packet sent and prints the number
of packets transmitted and received. Each received packet is validated
against the sent packet. The default setting will send four echo packets
containing 64 bytes of data. You can use the ping utility to test both the
host name and IP address of the host for DNS resolution. A successful
IP ping and failed host name ping could indicate name resolution issues.
•