Network Troubleshooting

Troubleshooting Windows 2000 Network Services TCTP, JMTi
Troubleshooting Network Problems

The Windows 2000 network infrastructure consists of many different components and
connections, and network problems can occur in any of them. This complicates the network
troubleshooting process, because a problem can have more than one probable cause. For
example, if a user cannot access a shared folder, the problem could be the result of a faulty
network cable or incorrect user permissions. Therefore, you must be able to identify the
symptoms and causes of network problems to isolate and correct the problem.
Identifying the Symptoms and Causes of Network
Problems
. !erify that hardware components, such as cables and network adapters, are working
properly before you begin to research the symptoms and causes of network problems.
"f a network problem is hardware related, checking these components first can reduce
the amount of time spent researching software#related network problems.
"f the problem is not hardware related, you must investigate further to identify its
symptoms and causes
Identifying Error Messages
Windows 2000 often displays error messages when a network operation fails. These error
messages include a brief description of the problem that has occurred. Windows 2000 also
provides troubleshooting information for common system errors, which can assist you in
diagnosing the problem.
$lick Help in an error message to receive a detailed description of the error, suggestions
about how to resolve the error, and a list of related tools and %elp topics that may help to
prevent the error from occurring in the future.
1 of 12 Computer Engineering Department
&ou can also use the net helpmsg command to locate troubleshooting information for a
specific error message. The net helpmsg command explains why an error occurred and how
to resolve the problem.
To view an explanation of an error message that a core component of Windows
2000 generated, at a command prompt, type net helpmsg number 'where number
is the number that is associated with the error message(.
Diagnosing Network Problems by sing Troubleshooters
Windows 2000 %elp includes troubleshooters, which you can use to )uickly solve common
network configuration or interoperability problems.
*se troubleshooters to diagnose and solve technical problems with the following networking
components+
$lient ,ervice for -etWare
.ynamic %ost $onfiguration /rotocol '.%$/(
0roup /olicy and the 1ctive .irectory2 directory service
.omain -ame ,ystem '.-,(
"nternet connections
-etworking 'T$/3"/(
4outing and 4emote 1ccess
4emote "nstallation ,ervices '4",(
,erver 5anagement
Windows "nternet -ame ,ervice 'W"-,(
Diagnosing Network Problems by sing E!ent "iewer
6vent !iewer is a monitoring and diagnostic Windows 2000 administrative tool that allows
you to view logs about program, security, and system events on your computer.
&ou can use 6vent !iewer to view and manage event logs, and to gather system information
to identify when a particular service has been started, stopped, or failed to start because of
an error. 7y using 6vent !iewer, you can monitor event logs to predict and identify the
sources of system problems.
#esol!ing TCP$IP Problems
To determine whether a network problem occurred as a result of a T$/3"/ failure, you must
be able to verify T$/3"/ configuration and connectivity, test "/ configuration and "/#to#media
access control '51$( resolution, and check "/ security configuration and the "/ routing
process.
The T$/3"/ process that enables computers to communicate over a network can be divided
into four distinct steps. 7efore it sends a packet from a sending host, the T$/3"/ protocol+
. Host name resolution+ 4esolves the host name or network basic input3output
system '-et7"8,( name to an "/ address.
2. #outing Table+ .etermines the interface to use and the forwarding "/ address by
using the destination "/ address and the "/ routing table.
9. %#P Pro&ess+ *ses the 1ddress 4esolution /rotocol '14/( to resolve the forwarding
"/ address to a 51$ address. This occurs for unicast "/ traffic on shared access
technologies such as 6thernet, Token 4ing, and Fiber .istributed .ata "nterface
'F.."(.
For multicast "/ traffic on 6thernet and F..", the destination multicast "/ address is
mapped to the appropriate multicast 51$ address. 5ulticast "/ traffic on Token 4ing
uses the functional address of 0x$0#00#00#0:#00#00. For broadcast traffic on shared
access technologies, the 51$ address is mapped to 8xFF#FF#FF#FF#FF#FF.
:. sing the M%C %ddress+ ,ends the packet to the 51$ address that is resolved by
using 14/ or multicast mapping.
The T$/3"/ stack follows this se)uence when it determines how to send a packet from point#
to#point. "f the destination to be reached by an application is in the form of a -et7"8, name
or host name, name resolution is re)uired before "/ can send the first packet.
"erifying TCP$IP Configuration
When troubleshooting a T$/3"/ networking problem, begin by checking the T$/3"/
configuration on the computer on which the problem occurs. The "pconfig utility is a
command#line tool that displays current T$/3"/ network configuration values, including the+
IP address
Subnet mask
Default gateway
This information helps to determine whether the configuration is initiali;ed, or whether a
duplicate "/ address exists on a network.
Testing IP Configuration
The /ing utility is a diagnostic tool that you can use to test T$/3"/ configuration and diagnose
connection failures by sending an "nternet $ontrol 5essage /rotocol '"$5/( 6cho 4e)uest to
a target host name or "/ address.
*se the /ing utility to determine whether a particular T$/3"/ host is available and functional.
Test Configuration and Conne&tions
Step Pro&edure
Purposes $ To !erify
that''
If (ails
)* ping )+,*-*-*)
'loopback address(
T$/3"/ is correctly installed
and bound to your network
adapter.
The T$/ drivers are
damaged or missing.
The network adapter is
not working.
1nother service is
interfering with "/
2. ping the "/ address of the
local computer 'itself(
The local computer was added
to the network correctly and
does not have a duplicate "/
address
The "/ address was not
properly configured.
9. ping the "/ address of
computers on the local
network.
The computer can
communicate with a host on
the local network or it was
The destination host is on the
remote network 'different
-etwork ".(.
<=ocal network> means
computers that share the
same -et". 'logically
connected( not physically
connected.
logically attached to the
network correctly
:. ping the default gateway The default gateway is
operational and your computer
can communicate with one on
the remote network 'different
-etwork ".(.
The Default gateway was not
configured correctly.
?. ping the IP address of a
remote host 'different
-et".(
The computer can
communicate through a router.
"f the ping command is
successful after this step, steps
through : are successful by
default
The current remote host might
be turned off. 1lso the routing
table might fail.
@. ping the host name of a
remote host to verify that
the computer can resolve
a remote host name.
To resolve a computer name to
an "/ address,
if pinging by "/ address in step
? succeeds, the problem is with
host name resolution, not
network connectivity
Troubleshooting IP #outing
The first step for troubleshooting "/ routing is to verify that a default gateway is configured
and that the link between the host and the default gateway is operational.
5ake sure that only one default gateway is configured. 1lthough it is possible to configure
more than one default gateway, additional gateways are only used if the "/ stack determines
that the original gateway is not functioning.
To determine the status of the first configured gateway, delete all other gateways to simplify
the troubleshooting process.
#outing Problem Error list
No #outing Error Des&riptions Corre&tness
)* TTL Expired
in Transit.
"ndicates that the number of hops re)uired
to reach the destination exceeds the Time
to =ive 'TT=( value that the sending host
sets for forwarding packets. The default
TT= value is 92, which may not be enough
time for a packet to travel the re)uired
number of links to a destination.
*se the ping .i command to
increase the TT= value, up to a
maximum of 2??.
Note ,ome routers will drop
packets with an expired TT=. This is
known as a silent discard.
2. Destination
Host
Unreachable
"ndicates that the local system has no
route to the desired destination, or a
remote router reports that it has no route
to the destination.
"f the A.estination %ost *nreachableA
message appears, no route from the local
system exists, and the packets to be sent
were never forwarded.
"f the A4eply From IP address+ .estination
%ost *nreachableA message appears, the
routing problem occurred at the remote
router that is associated with the specified
"/ address.
$heck routing table of the local
computer. 1dd the re)uired
path to the destination -et"..
$heck routing table of the
remote router. 1dd the re)uired
path to the destination -et"..
9. Request
Timed Out
"ndicates that no A6cho 4eplyA messages
were received within the default time of
one second. This message may be the
result of network congestion, failure of the
14/ re)uest, packet filtering, a routing
error, or a silent discard. 5ost often, it
indicates that a route ba&k to the sending
host has failed, because the destination
host, one of the intermediary routers, or
the default gateway of the destination host
does not recogni;e the route back to the
sending host.
$heck the routing table of
the destination host to
determine whether it has a
route to the sending host.
Then check for the routing
tables of the individual
routers.
"f the remote routing tables
are correct and contain a
valid route back to the
sending host, use the arp
.a command to determine
whether the correct address
is listed in the 14/ cache.
"n addition, check the
subnet mask to ensure that
a remote address has not
been interpreted as a local
address
Routing Example 1+
10.0.0.0 and 172.16.0.0 networks are physically connected but logically separated
.$ and ,tudent are local to each other. .$2 and student2 are remote to .$ and
student.
.$ and student can talk to each other directly using the default routing table
maintained by each of them.
$ommunication between local and remote hosts, .$ and ,tudent2 for example, can
take place by modifying their routing table entries. 6very single host on a local
network must contain the path to the remote network "..
Net!" 10.0.0.0#2$ Net!" 172.16.0.0#16
!%1 &
10.0.0.11
'tudent1 & 10.0.0.21
!%2 &
172.16.(.21
'tudent2 & 172.16.(.22
SAME PHYSICAL NETWORK
Routing Example 2+
10.0.0.0 and 172.16.0.0 networks are physically and logically separated to each other. )he
de*ault gateway *or both o* the networks is a router. )he router must be local to both
networks.
.$ and ,tudent are local to each other. .$2 and student2 are remote to .$ and
student.
.$ and student can talk to each other directly using the default routing table
maintained by each of them.
$ommunication between local and remote hosts, .$ and ,tudent2 for example, can
take place by modifying their routing table entries. 6very single host on a local
network must be configured to use the router as its default gateway. 8nly the router
needs to maintain the path to each of the networks.
7asically, in reality there are possible to have several intermediate routers that
connect between the two networks that are far apart to each other. 6ach of the
routers needs to store the path information on how to reach the other routers.
Net!" 10.0.0.0#2$
Net!" 172.16.0.0#16
!%1 &
10.0.0.11
'tudent1 & 10.0.0.21
!%2 &
172.16.(.21
'tudent2 & 172.16.(.22
R+,)ER
10.0.0.1 172.16.(.1
DIFFERENT PHYSICAL NETWORKS
#esol!ing Name #esolution Problems
T$/3"/ for Windows 2000 allows an application to communicate over a network with another
computer by using an "/ address, or either of the following types of destination designations+
%ost name
-et7"8, name
"f you are unable to access a system by host name or -et7"8, name, a problem with name
resolution could exist on your network. &ou must determine whether it is a host or domain
name or a -et7"8, name resolution problem.
The first step in distinguishing host name resolution problems from -et7"8, name resolution
problems is to determine whether the failing application uses -et7"8, or host names. "f the
application uses host names, the problem is the result of incorrect host name resolution.
#esol!ing Host Name #esolution Problems
/roblems with host name resolution can be the result of an incorrectly configured Hosts file
or DNS ser!er, an incorrect %osts file entry or "/ address, or multiple entries for a single
host in a %osts file
Che&king the Hosts (ile
The %osts file or a .-, server resolves host names to "/ addresses whenever you use T$/3"/
utilities such as the /ing utility.
!erify that the name of the remote computer is spelled correctly in the %osts file, and in the
application that uses it for name resolution.
Nslookup tility
-slookup is a command#line utility that you can use to make .-, )ueries to test and
troubleshoot your .-, installation. -ame resolution errors can occur if .-, server or client
entries are not configured correctly, the .-, server is not running, or there is a problem with
network connectivity.
To view the host name and "/ address of the .-, server that is configured for the
local system, type nslookup at a command prompt.
"f the .-, server is offline, the .-, service is not enabled on the host computer, or if
a hardware or routing problem exists, the .efault servers are not available message
appears.
To look up a hostBs "/ address by using .-,, type the host name and press 6-T64. 7y
default, -slookup uses the .-, server configured for the computer on which it is running.
"f the .-, server cannot resolve the host name, the -on#existent domain message
appears.
"f a )uery fails as a result of connectivity issues or network congestion, or if the .-,
server is overloaded with re)uests, the Timeout message appears+
Net/I0S Name #esolution Pro&ess
Windows 2000 first checks the host computerBs internal -et7"8, name cache to resolve a
-et7"8, name to an "/ address. "f this fails to provide an "/ address, the -et7"8, name can
be resolved to an "/ address by using a broadcast, checking the =mhosts file, or )uerying a
W"-, server. The order in which Windows 2000 uses these mechanisms depends on the node
type of the client.
The default node type is hybrid or %#node, which )ueries a W"-, server, and then attempts a
local broadcast to resolve the name. "f these mechanisms are unsuccessful, the client )ueries
its %osts file. "f the %osts file does not contain the "/ address, the client )ueries its .-,
server if it is configured to use one.
Diagnosing Net/I0S Name #esolution Problems
&ou can use the nbtstat or net !iew command to diagnose -et7"8, name resolution
problems.
Nbtstat
&ou use the -btstat utility to view and register -et7"8, names on a computer running
Windows 2000. -btstat displays protocol statistics and name information used by -et7T
connections, which can help with troubleshooting -et7"8, name resolution problems.
For example, to identify the -et7"8, names that a computer has registered by using
-et7T, type nbtstat .n at a command prompt.
"n Windows 2000, you can re#register -et7"8, names with the name server after a
computer has already been started.
To re#register -et7"8, names, type nbtstat .## at a command prompt.
#esol!ing Common Net/I0S Name #esolution Errors
The most common symptom of a problem in -et7"8, name resolution is when the /ing utility
returns a -etwork /ath -ot Found '6rror ?9( error message. This message is generally
returned when name resolution fails for a particular computer name. This type of error can
also occur when there is a problem establishing a -et7"8, session.
Determining the Cause of the Error
To determine the cause of a -etwork /ath -ot Found error message, type net
!iew 11hostname at a command prompt 'where hostname is an active network
resource(.
"f this command is successful, name resolution is probably not the source of the problem.
*se the ping command with the host name to confirm that name resolution is working
properly. "f the ping command returns an *nknown %ost error message, name resolution
has failed and you must check the status of your -et7"8, session.
Checing the !tatus of a Net"#O! !ession
To check the status of your -et7"8, session, type net !iew 11IP address at a
command prompt 'where IP address is the "/ address of the network resource that
you specified when determining the cause of the error(.
"f the computer is on the local subnet, confirm that the name is spelled correctly
and that the target computer is running T$/3"/.
"f the computer is not on the local subnet, be sure that its name and "/ address
mapping are available in the .-, database, the %osts or =mhosts file, or the W"-,
database.
"f all T$/3"/ elements appear to be installed properly, use the ping command with
the remote computer to ensure that the T$/3"/ protocol is working.

Network Troubleshooting

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Network Troubleshooting

Hochgeladen von

Copyright:

Verfügbare Formate

Troubleshooting Windows 2000 Network Services TCTP, JMTi

Troubleshooting Network Problems

Das könnte Ihnen auch gefallen