Você está na página 1de 41

TCP/IP Troubleshooting Tools and Strategies

Many network troubleshooting tools are available for Windows. Most are included in the product or the
Windows 2000 Server Resource Kit. Microsoft Network Monitor is an excellent network-tracing tool. The full
version is part of the Microsoft Systems Management Server product, and a more limited version is included in
the Windows 2000 Server product.
When troubleshooting any problem, it is helpful to use a logical approach. Some questions to ask are:

What does work?


What does not work?
How are the things that do and do not work related?
Have the things that do not work ever worked on this computer/network?
If so, what has changed since it last worked?

Troubleshooting a problem from the bottom up is often a good way to isolate the problem quickly. The tools
listed below are organized for this approach.

IPConfig Tool
IPConfig is a command-line utility that prints out the TCP/IP-related configuration of a host. When used with
the /all switch, it produces a detailed configuration report for all interfaces, including any configured serial
ports (RAS). Output can be redirected to a file and pasted into other documents:

C:\>ipconfig /allWindows 2000 IP configuration:


Host Name . . . . . . . . . . . . : DAVEMAC2
Primary DNS Suffix . . . . . . . : mytest.microsoft.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : microsoft.com
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink III EISA (3C579-TP)
Physical Address. . . . . . . . . : 00-20-AF-1D-2B-91
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.57.8.190
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.57.9.254
Primary WINS Server . . . . . . . : 10.57.9.254
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : AMD Family PCI Ethernet Adapter
Physical Address. . . . . . . . . : 00-80-5F-88-60-9A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 199.199.40.22
Autoconfiguration Enabled . . . . : Yes
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 199.199.40.1
DNS Servers . . . . . . . . . . . : 199.199.40.254
Primary WINS Server . . . . . . . : 199.199.40.254
Ping Tool
Ping is a tool that helps to verify IP-level reachability. The ping command can be used to send an ICMP echo
request to a target name or IP address. First, ping the IP address of the target host to see if it responds
because this is the simplest test. If that succeeds, try pinging the name. Ping uses Windows Sockets-style
name resolution to resolve the name to an address; therefore, if pinging by address succeeds but pinging by
name fails, the problem lies in name resolution, not network connectivity.

Type ping -? to see what command-line options are available. Ping allows you to specify the size of packets to
use, how many to send, whether to record the route used, what TTL value to use, and whether to set the don't
fragment flag. See the PMTU discovery section of this document for details on using ping to manually
determine the PMTU between two computers.
The following example illustrates how to send two pings, each 1450 bytes in size, to address 10.99.99.2:

C:\>ping -n 2 -l 1450 10.99.99.2


Pinging 10.99.99.2 with 1450 bytes of data:

Reply from 10.99.99.2: bytes=1450 time<10ms TTL=32


Reply from 10.99.99.2: bytes=1450 time<10ms TTL=32
Ping statistics for 10.99.99.2:

Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),


Approximate round trip times in milliseconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


By default, ping waits one second for each response to be returned before timing out. If the remote system
being pinged is across a high-delay link, such as a satellite link, responses could take longer to be returned.
The -w (wait) switch can be used to specify a longer time-out. Computers using IPSec may require several
seconds to set up a security association before they respond to a ping.

PathPing Tool
The Pathping command is a route-tracing tool that combines features of the ping and tracert commands with
additional information that neither of those tools provides. The Pathping command sends packets to each
router on the way to a final destination over a given period of time, and then computes results based on the
packets returned from each hop. Since the command shows the degree of packet loss at any given router or
link, it is easy to determine which routers or links might be causing network problems. The switches R T can
be used with Pathping to determine whether the devices on the path are 802.1p-compliant and RSVP-aware.
The following example illustrates the default output when tracing the route to www.sectur.gov.ar [200.1.247.2]
over a maximum of 30 hops:

0 warren.microsoft.com [163.15.2.217]
1 tnt2.seattle2.wa.da.uu.net [206.115.150.106]
2 206.115.169.217
3 119.ATM1-0-0.HR2.SEA1.ALTER.NET [152.63.104.38]
4 412.atm11-0.gw1.sea1.ALTER.NET [137.39.13.73]
5 teleglobe2-gw.customer.ALTER.NET [157.130.177.222]
6 if-0-3.core1.Seattle.Teleglobe.net [207.45.222.37]
7 if-1-3.core1.Burnaby.Teleglobe.net [207.45.223.113]
8 if-1-2.core1.Scarborough.Teleglobe.net [207.45.222.189]
9 if-2-1.core1.Montreal.Teleglobe.net [207.45.222.121]
10 if-3-1.core1.PennantPoint.Teleglobe.net [207.45.223.41]
11 if-5-0-0.bb1.PennantPoint.Teleglobe.net [207.45.222.94]
12 BOSQUE-aragorn.tecoint.net [200.43.189.230]
13 ARAGORN-bosque.tecoint.net [200.43.189.229]
14 GANDALF-aragorn.tecoint.net [200.43.189.225]
15 Startel.tecoint.net [200.43.189.18]
16 200.26.9.245
17 200.26.9.26
18 200.1.247.2
Computing statistics for 450 seconds:

Source to Here This Node/Link


Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 warren.microsoft.com [63.15.2.217]
0/ 100 = 0% |
1 115ms 0/ 100 = 0% 0/ 100 = 0% tnt2.seattle2.wa.da.uu.net [206.115.150.106]
0/ 100 = 0% |
2 121ms 0/ 100 = 0% 0/ 100 = 0% 206.115.169.217
0/ 100 = 0% |
3 122ms 0/ 100 = 0% 0/ 100 = 0% 119.ATM.ALTER.NET [152.63.104.38]
0/ 100 = 0% |
4 124ms 0/ 100 = 0% 0/ 100 = 0% 412.atm.sea1.ALTER.NET [137.39.13.73]
0/ 100 = 0% |
5 157ms 0/ 100 = 0% 0/ 100 = 0% teleglobe2-gw.ALTER.NET [157.130.177.222]
0/ 100 = 0% |
6 156ms 0/ 100 = 0% 0/ 100 = 0% if-0-3.Teleglobe.net [207.45.222.37]
0/ 100 = 0% |
7 198ms 0/ 100 = 0% 0/ 100 = 0% if-1-3.core1.Teleglobe.net [207.45.223.113]
0/ 100 = 0% |
8 216ms 0/ 100 = 0% 0/ 100 = 0% if-1-2.core1. Teleglobe.net [207.45.222.189]
0/ 100 = 0% |
9 207ms 0/ 100 = 0% 0/ 100 = 0% if-2-1.Teleglobe.net [207.45.222.121]
0/ 100 = 0% |
10 220ms 0/ 100 = 0% 0/ 100 = 0% if-3-1.core1.Teleglobe.net [207.45.223.41]
0/ 100 = 0% |
11 240ms 0/ 100 = 0% 0/ 100 = 0% if-5-0-0.bb1.Teleglobe.net [207.45.222.94]
0/ 100 = 0% |
12 423ms 1/ 100 = 1% 1/ 100 = 1% BOSQUE-aragorn.tecoint.net [200.43.189.230]
0/ 100 = 0% |
13 412ms 0/ 100 = 0% 0/ 100 = 0% ARAGORN-bosque.tecoint.net [200.43.189.229]
0/ 100 = 0% |
14 415ms 1/ 100 = 1% 1/ 100 = 1% GANDALF-aragorn.tecoint.net [200.43.189.225]
0/ 100 = 0% |
15 578ms 0/ 100 = 0% 0/ 100 = 0% Startel.tecoint.net [200.43.189.18]
2/ 100 = 2% |
16 735ms 2/ 100 = 2% 0/ 100 = 0% 200.26.9.245
5/ 100 = 5% |
17 1005ms 8/ 100 = 8% 1/ 100 = 1% 200.26.9.26
0/ 100 = 0% |
18 1089ms 7/ 100 = 7% 0/ 100 = 0% 200.1.247.2
Trace complete.
When Pathping is run, you first see the results for the route as it is tested for problems. This is the same path
as that shown by the tracert command. The Pathping command then displays a busy message for the next
450 seconds (this time varies by the hop count). During this time, Pathping gathers information from all the
routers previously listed and from the links between them. At the end of this period, it displays the test results.
The two right-most columnsThis Node/Link Lost/Sent=Pct and Addresscontain the most useful
information. The link between 200.26.9.245 (hop 16) and 200.26.9.26 (hop 17) is dropping 8 percent of the
packets.
The loss rates displayed for the links (marked as a | in the right-most column) indicate losses of packets being
forwarded along the path. This loss indicates link congestion. The loss rates displayed for routers (indicated by
their IP addresses in the right-most column) indicate that those routers' CPUs might be overloaded. Congested
routers can also be a factor in end-to-end problems.

Arp Tool
The arp command is useful for viewing the ARP cache. If two hosts on the same subnet cannot ping each other
successfully, try running the arp -a command on each computer to see if the computers have the correct MAC
addresses listed for each other. Use IPConfig to determine a host's media access control address. If another
host with a duplicate IP address exists on the network, the ARP cache may have had the media access control
address for the other computer placed in it. Use arp -d to delete an entry that may be incorrect. Add entries
by using arp -s.

Tracert Tool

Tracert is a route-tracing utility. Tracert uses the IP TTL field and ICMP error messages to determine the
route from one host to another through a network. Sample output from the tracert command is shown in the
ICMP section of this document.

Route Tool
Route is used to view or modify the route table. Route print displays a list of current routes known by IP for
the host. Sample output is shown in the IP section of this document. Note that in Windows 2000 the current
active default gateway is shown at the end of the list of routes. Route add adds routes to the table. Route
delete removes routes from the table.
Routes added to the table are not made persistent unless the -p switch is specified. Nonpersistent routes last
only until the computer is rebooted.
For two hosts to exchange IP datagrams, they must both have a route to each other, or they must use a
default gateway that knows of a route. Normally, routers exchange information with each other by using a
protocol such as Routing Information Protocol (RIP) or Open Shortest Path First (OSPF). Silent RIP is available
for Windows 2000 Professional, and full routing protocols are supported by Windows 2000 Server in the
Routing and Remote Access service.

Netstat
Netstat displays protocol statistics and current TCP/IP connections. Netstat -a displays all connections, and
netstat -r displays the route table and any active connections. The -n switch tells netstat not to convert
addresses and port numbers to names, which speeds up execution. The -e switch displays Ethernet statistics
and may be combined with the -s switch, which shows protocol statistics. Sample output is shown here:

C:\>netstat -e
Interface statistics:

Received Sent
Bytes 372959625 123567086
Unicast packets 134302 145204
Non-unicast packets 55937 886
Discards 0 0
Errors 0 0
Unknown protocols 1757381
C:\>netstat -an
Active connections:

Proto Local Address Foreign Address State


TCP 0.0.0.0:42 0.0.0.0:0 LISTENING
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:593 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1038 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1041 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1048 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1054 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1077 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1088 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1092 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3268 0.0.0.0:0 LISTENING
TCP 10.99.99.1:53 0.0.0.0:0 LISTENING
TCP 10.99.99.1:139 0.0.0.0:0 LISTENING
TCP 10.99.99.1:389 10.99.99.1:1092 ESTABLISHED
TCP 10.99.99.1:1092 10.99.99.1:389 ESTABLISHED

TCP 10.99.99.1:3604 10.99.99.1:135 TIME_WAIT


TCP 10.99.99.1:3605 10.99.99.1:1077 TIME_WAIT
UDP 0.0.0.0:42 *:*
UDP 0.0.0.0:88 *:*
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:135 *:*
UDP 0.0.0.0:389 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:1073 *:*
UDP 0.0.0.0:1076 *:*
UDP 0.0.0.0:1087 *:*
UDP 10.99.99.1:53 *:*
UDP 10.99.99.1:67 *:*
UDP 10.99.99.1:137 *:*
UDP 10.99.99.1:138 *:*
UDP 127.0.0.1:1052 *:*
D:\>netstat -s
IP statistics:

Packets Received = 3175996


Received Header Errors = 0
Received Address Errors = 38054
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 0
Received Packets Delivered = 3142564
Output Requests = 3523906
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 0
Reassembly Successful = 0
Reassembly Failures = 0
Datagrams Successfully Fragmented = 0
Datagrams Failing Fragmentation = 0
Fragments Created = 0
ICMP statistics:

Received Sent
Messages 462 33
Errors 0 0
Destination Unreachable 392 4
Time Exceeded 0 0
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 1 22
Echo Replies 12 1
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0
TCP statistics:

Active Opens = 12164


Passive Opens = 12
Failed Connection Attempts = 79
Reset Connections = 11923
Current Connections = 1

Segments Received = 2970519


Segments Sent = 3505992
Segments Retransmitted = 18
UDP statistics:

Datagrams Received = 155620


No Ports = 16578
Receive Errors = 0
Datagrams Sent = 17822
NBTStat Tool
NBTStat is a useful tool for troubleshooting NetBIOS name-resolution problems. NBTStat -n displays the
names that applications, such as the server and redirector, registered locally on the system. NBTStat -c shows
the NetBIOS name cache, which contains name-to-address mappings for other computers. NBTStat -R purges
the name cache and reloads it from the Lmhosts file. NBTStat RR (new in Windows 2000 and NT 4.0 SP5)
re-registers all names with the name server. NBTStat -a name performs a NetBIOS adapter status command
against the computer that is specified by name. The adapter status command returns the local NetBIOS name
table for that computer and the media access control address of the adapter card. NBTStat -s lists the current
NetBIOS sessions and their status, including statistics.

Nslookup Tool
Nslookup, added in Windows NT 4.0, is a useful tool for troubleshooting DNS problems, such as host name
resolution. When you start nslookup, it shows the host name and IP address of the DNS server that is
configured for the local system, and then displays a command prompt. If you type a question mark (?),
nslookup shows the different commands that are available.
To look up the IP address of a host, using the DNS, type the host name and press Enter. Nslookup defaults to
the DNS server that is configured for the computer that it is running on, but you can focus it on a different DNS
server by typing server name (name is the host name of the server that you want to use for future lookups).
When you use Nslookup, you should be aware of the domain name devolution method. If you type in just a
host name and press Enter, nslookup appends the domain suffix of the computer (such as
cswatcp.microsoft.com) to the host name before it queries the DNS. If the name is not found, the domain
suffix is devolved by one label (in this case, cswatcp is removed, and the suffix becomes microsoft.com). Then
the query is repeated. Windows 2000-based computers only devolve names to the second level domain
(microsoft.com in this example), so if this query fails, no further attempts are made to resolve the name. If a
fully qualified domain name is typed in (as indicated by a trailing dot), the DNS server is only queried for that
name and no devolution is performed. To look up a host name that is completely outside of your domain, you
must type in a fully qualified name.
An especially useful troubleshooting feature is debug mode, which you can invoke by typing set debug, or for
even greater detail, set d2. In debug mode, nslookup lists the steps being taken to complete its commands,
as shown in this example:

C:\>nslookup
(null) davemac3.cswatcp.microsoft.com
Address: 10.57.8.190
> set d2
> rain-city
(null) davemac3.cswatcp.microsoft.com
Address: 10.57.8.190
-----------SendRequest(), len 49
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
rain-city.cswatcp.microsoft.com, type = A, class = IN
-----------Got answer (108 bytes):
HEADER:

opcode = QUERY, id = 2, rcode = NOERROR


header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 2, authority records = 0, additional = 0
QUESTIONS:
rain-city.cswatcp.microsoft.com, type = A, class = IN
ANSWERS:
-> rain-city.cswatcp.microsoft.com
type = CNAME, class = IN, dlen = 31
canonical name = seattle.cswatcp.microsoft.com
ttl = 86400 (1 day)
-> seattle.cswatcp.microsoft.com
type = A, class = IN, dlen = 4
internet address = 10.1.2.3
ttl = 86400 (1 day)
-----------(null) seattle.cswatcp.microsoft.com
Address: 10.1.2.3
Aliases: rain-city.cswatcp.microsoft.com
In this example, set d2 was issued to set nslookup to debug mode, then address look-up was used for the
host name rain-city. The first two lines of output show the host name and IP address of the DNS server to
which the lookup was sent. As the next paragraph shows, the domain suffix of the local machine
(cswatcp.microsoft.com) was appended to the name rain-city, and nslookup submitted this question to the
DNS server. The next paragraph indicates that nslookup received an answer from the DNS and that there
were two answer records in response to one question. The question is repeated in the response, along with the
two answer records. In this case, the first answer record indicates that the name raincity.cswatcp.microsoft.com is actually a cname, or canonical name (alias) for the host name
seattle.cswatcp.microsoft.com. The second answer record lists the IP address for that host as 10.1.2.3.

Microsoft Network Monitor


Microsoft Network Monitor is a tool developed by Microsoft to make the task of troubleshooting complex
network problems easier and more economical. It is packaged as part of the Microsoft Systems Management
Server product, but can be used as a stand-alone network monitor. In addition, Windows NT and Windows 95
include Network Monitor Agent software, and Windows NT Server and Windows 2000 include a limited version
of Network Monitor. Stations running Network Monitor can attach to stations running the agent software over
the network or by using dial-up (remote access) to perform monitoring or tracing of remote network segments.
This can be a very useful troubleshooting tool.
Network Monitor works by placing the NIC on the capturing host into promiscuous mode so that it passes every
frame on the wire up to the tracing tool. (The limited version of Network Monitor that ships with Windows 2000
Server allows only traffic to and from the computer to be traced.) Capture filters can be defined so that only
specific frames are saved for analysis. Filters can be defined based on source and destination NIC addresses,
source and destination protocol addresses, and pattern matches. Once the frames have been captured, display
filtering can be used to further narrow down a problem. Display filtering allows specific protocols to be selected
as well.
Windows NTbased computers use the Server Message Block (SMB) protocol for many functions, including file
and print sharing. The smb.hlp file in the Netmon parser directory is a good reference for interpreting this
protocol.

Adding Additional IP
Addresses to a Single Network
Adapter
The information in this article applies to:

Microsoft Windows Millennium Edition


Microsoft Windows 98 Second Edition
Microsoft Windows 98
Microsoft Windows 95

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp
IMPORTANT: This article contains information about modifying the registry. Before you modify
the registry, make sure to back it up and make sure that you understand how to restore the
registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
Q256986 Description of the Microsoft Windows Registry

Summary
This article describes a method to allow more than one IP address when you are using Windows
on a computer with a single network adapter.
NOTE: This configuration may or may not work on your computer, and is not supported by
Microsoft Product Support Services.

More Information
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To add additional IP addresses, use Registry Editor to edit the registry. Go to the following
registry section:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans
\
There should be multiple subkeys with the value 0000, 0001, and so on. If the computer has
only one network adapter, click the 0000 entry. You should then see a value named IPAddress
and a value named IPMask.
For each additional IP address, add to the two values.
The IPAddress value should contain the current IP addresses. This value is a string of IP
addresses separated by commas with no embedded spaces. The IPMask value should be a list of
comma-separated subnet masks with no embedded spaces. You must add a mask value for each
IPAddress. When you are done, quit Registry Editor and then restart the computer.

Computer Hangs When You


Add a PCCard Network
Adapter by Using Add New
Hardware Wizard
The information in this article applies to:

Microsoft Windows 98 Second Edition

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
When you insert a new PCCard network adapter for the first time, if the Add New Hardware
Wizard runs and you receive the following message, when you click Yes, your computer may
stop responding (hang):
System Settings Change
To finish setting up your new hardware, you must restart your computer.
Do you want to restart your computer now?

Cause
This issue can occur because adding network hardware by using the wizard requires a system
restart to complete the networking installation. Additionally, a resource rebalance on the PCCard
device(s), is also needed. The resource rebalance cannot occur until after the current process is
complete, which does not occur if you choose to restart your computer. This causes the
installation process to be unable to answer a system-wide shutdown message, and this causes
the computer to stop responding.
Note that the wizard does not normally run if you install a device for which Windows already has
configuration information and drivers. In this case, the configuration manager may display
various messages requesting installation input.

Resolution
To work around this issue:
1.

2.
3.
4.
5.
6.

Note that the only uncompleted action is a rebalance of the device resources, so
restarting your computer may result in a successful installation. After you restart your
computer, test to determine if the your new hardware is functional, and if it is not,
continue to the next step.
Remove the device by using Device Manager in the System tool in Control Panel.
Shut down the computer.
Physically remove the PCCard device.
Restart the computer.
Insert the new adapter, and follow the instructions on the screen to complete the Add
New Hardware Wizard.

7.

When you receive the System Settings Change dialog box, click No, and then wait until
the rest of the installation process completes before restarting your computer. Note that
your pointer switches between the normal pointer and an hourglass pointer while the
PCCard resource rebalance completes.

More Information
This symptom is only likely to occur if you install a newer PCCard network adapter that requires
new configuration information and drivers from the equipment manufacturer.
If you install an adapter that uses configuration information and drivers that are already
provided with Windows, the wizard does not run, and the problem does not occur.

Hang at Startup or Shutdown


with Ndis.vxd Enabled
The information in this article applies to:

Microsoft Windows Millennium Edition


Microsoft Windows 98 Second Edition

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
Microsoft Windows Millennium Edition (Me) may stop responding (hang) during startup or
shutdown.

Cause
This issue can occur if the Ndis.vxd file is enabled and any of the following conditions exist:

You have AtGuard by WRQ, Inc., installed on your computer.


You use a Netgear 310TX (or other) network adapter.
There is a hardware conflict on the computer.

To determine if the Ndis.vxd file is enabled on your computer, see the "More Information"
section of this article.

Resolution
To determine the possible cause of the issue, start your computer in a "clean" configuration,
perform a logged boot, and then look at the last entry in the Bootlog.txt file. The last entry
should be the device or virtual device driver that is not being loaded or unloaded correctly.

Performing a Clean Boot


For additional information about how to perform a clean boot, click the article number below to
view the article in the Microsoft Knowledge Base:
Q267288 How to Perform a Clean Boot in Windows Millennium Edition

Performing a Logged Boot


To perform a logged boot:
1.
2.
3.

Restart your computer and then press and hold down the CTRL key while the computer
starts.
When the Startup menu appears, choose Logged (\Bootlog.txt).
Restart your computer.

This completes a full cycle for the log.


To review the log file, start Windows Explorer, and then double-click the C:\Bootlog.txt file.
Look at the last entry in the file.

Resolving the Issue


Third-Party Virtual Device Driver
If the cause is a third-party virtual device driver, remove the virtual device driver by uninstalling
the software it belongs to.

Network Adapter Driver


If the cause is a network adapter driver, contact the adapter's manufacturer to inquire about
obtaining an updated driver that works correctly with Windows Me.

Netgear 310TX Network Adapter


If you use a Netgear 310TX network adapter with a driver earlier than version 4.02, install the
newer driver that is located on the Windows Me CD-ROM in the Drivers folder. To install the
Netgear FA310TX 4.02 driver:
1.
2.
3.
4.
5.
6.
7.
8.

Click Start, click Settings, click Control Panel, and then double-click System.
On the Device Manager tab, double-click the Network Adapters branch to expand it.
Double-click the Netgear FA310TX device.
On the Driver tab, click Update Driver.
Click Specify the location of the driver, and then click Next.
Click Display a list of all the drivers in a specific location..., and then click Next.
Click Have Disk, and then click Browse.
Browse to the CD-ROM:\Drivers\Net\Netgear folder (where CD-ROM is your CD-ROM
drive letter).
9. Click OK, and then click OK.
10. Follow the instructions that remain on the screen to finish the installation.

Hardware Conflict
If the cause is a hardware conflict, see the following article in the Microsoft Knowledge Base for
information about how to troubleshoot hardware conflicts:
Q133240 Troubleshooting Device Conflicts with Device Manager

More Information
To determine if the Ndis.vxd file is enabled on your computer:
1.
2.
3.
4.

Click Start, click Run, type msconfig, and then click OK.
Click the Static VxDs tab.
Look for the Ndis.vxd entry. If the check box for this entry is selected, the Ndis.vxd file
is enabled.
To disable the Ndix.vxd file as a test, click to clear the NDIS check box, and then click
OK. If the computer hangs during shutdown, the change will not take effect until you
restart the computer. If disabling the Ndis.vxd file resolves the hanging issue during
startup or shutdown, the information in this article may apply.

The third-party products discussed in this article are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or
reliability.
For additional information, click the article number below to view the article in the Microsoft
Knowledge Base:

Q243199 Windows 98 Second Edition Problems with NDIS Intermediate Drivers

Network Connectivity
Unavailable After Resuming
Computer
The information in this article applies to:

Microsoft Windows Millennium Edition


Microsoft Windows 98

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
After you resume your computer that is using the NetBEUI protocol, some computers on your
network may not be visible, and network icons for previously connected computers may be
unavailable. If you double-click Network Neighborhood, only computers on the "Entire Network"
may be visible. Also, if you try to connect to another computer on your network, you may
receive one or more of the following error messages:

No network provider accepted the given network path.

Unable to browse the network, The network is not accessible.

Resolution
To work around this problem, add another network protocol such as TCP/IP.

Status
Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the
beginning of this article.

No Network Connectivity on
TCP/IP-Based Network
The information in this article applies to:

Microsoft Windows Millennium Edition


Microsoft Windows 95
Microsoft Windows 98

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
You may not be able to view or connect to any shared resources on a network that uses the
Transport Control Protocol/Internet Protocol (TCP/IP), even though your network adapter and
network server settings have been verified to work correctly.

Cause
This problem can occur if you change the Internet Protocol (IP) address for your computer to
any of the following invalid IP addresses in the TCP/IP Properties dialog box:

0.0.0.0
127.<x>.<y>.<z>
255.0.0.0
255.255.0.0
255.255.255.0
255.255.255.255

To specify any of these addresses, you must click Specify An IP Address on the IP Address tab in
the TCP/IP Properties dialog box, type the invalid TCP/IP address, click OK, click OK when you
receive the following message, and then click Cancel:
The specified IP address is not valid. Please check that the value you typed is correct. If
you believe the value is correct but you still receive this message, check with your
network administrator.

Resolution
To work around this problem, change the IP address to a valid IP address. To do so, follow these
steps:
1.
2.
3.
4.

Click Start, point to Settings, click Control Panel, and then double- click Network.
On the Configuration tab, double-click either TCP/IP or "TCP/IP-><network adapter>,"
where <network adapter> is the name of your network adapter.
On the IP Address tab, type a valid IP address in the IP Address box, and then click OK.
If you do not know a valid IP address for your computer, contact your network
administrator.
Click OK, and then click OK.

Status
Microsoft has confirmed this to be a problem in Microsoft Windows 95, Windows 98 and
Windows Me.

More Information
Networks that use TCP/IP set a unique IP address for each computer to determine its identity.
The 127.0.0.1 IP address is reserved for testing the TCP/IP stack with the PING command. The
following table lists IP addresses that are not valid for a computer, where <x.y.z> is a range of
numbers from 0 to 254.

Invalid IP address Valid (reserved) usage


----------------------------------------------------127.0.0.1

Loopback/LocalHost address

255.0.0.0

Class A subnet mask

255.255.0.0

Class B subnet mask

255.255.255.0
225.<x.y.z> -

Class C subnet mask


Class D address (multicast only)

239.<x.y.z>
240.<x.y.z> - Class E address (reserved)
254.<x.y.z>
255.255.255.255 Broadcast address

If you use any of the addresses listed above as the IP address for a computer, no other
computer can successfully communicate with it.
A subnet mask is an address for a subnetwork used to expand the range of possible IP
addresses on the network. A subnet mask acts to identify an IP address on different
subnetworks. TCP/IP uses the binary format to resolve an IP address and subnet mask.
Both the IP address and the subnet mask use binary format for each octet. An IP address
consists of four octets. The portion of the octet in binary format that is not used by the subnet
mask becomes the portion of the IP address that differentiates it from other IP addresses on the
same subnetwork. The assigned IP address and the subnet mask are combined in binary format
to create the resolved IP address in a TCP/IP network. If the resolved IP address in binary
format is all zeros or ones (for example, 11111111, or decimal 255), it is an invalid IP address.
The following table lists sample IP addresses and subnet masks for an IP address on a Class C
subnetwork. These addresses assume that the first three octets of each IP address and subnet
mask are valid.

IP address

Subnet mask

Resolved IP address Result

------------------------------------------------------------00000001 (1) 11111100 (252) 11111101 (253)

valid

00000011 (3) 11111100 (252) 11111111 (255)

invalid

For information about troubleshooting TCP/IP, please see the following article in the Microsoft
Knowledge Base:

ARTICLE-ID: Q172218
TITLE : Microsoft TCP/IP Host Name Resolution Order

Microsoft TCP/IP Host Name


Resolution Order
The information in this article applies to:

Microsoft Windows NT Server 3.5, 3.51, 4.0


Microsoft Windows NT Workstation 3.5, 3.51, 4.0
Microsoft Windows 95
Microsoft TCP/IP-32 for Windows for Workgroups
Microsoft LAN Manager
Microsoft Network Client for MS-DOS 3.0

Summary
This article discusses the different methods of host name to IP address resolutions used by
Microsoft Windows clients. The sequence of methods is different than the sequence used to
resolve NetBIOS names to IP addresses.

More Information
On a network using the TCP/IP protocol, it is necessary to convert names of resources to IP
addresses to connect to these resources. Microsoft Windows clients will follow a sequence of
methods in attempting to resolve a name to an address, stopping the search when it
successfully matches a name to an IP address.
There are two main sequences used in almost all cases: NetBIOS resolution and Host name
resolution. Clients connecting to resources on Microsoft servers, typically through Windows File
Manager or Network Neighborhood, most often use NetBIOS name resolution.
For additional information, please see the following article in the Microsoft Knowledge Base:
Q119493 NetBIOS over TCP/IP Name Resolution and WINS
Host name resolution resolves the names of TCP/IP resources that do not connect through the
NetBIOS interface. The most common example of this is a Web browser such as Microsoft
Internet Explorer. Other examples include Internet applications such as Ping, FTP, and Telnet.
Many modern database and mail applications that connect using Winsock, the Microsoft
Windows implementation of TCP/IP sockets, also use host name resolution. Examples of these
types of applications are Outlook and Exchange.
When troubleshooting name resolution issues, it is important to narrow down whether the
application is resolving a NetBIOS name or a host name.
NOTE: In the context of this article, the term "client" does not necessarily refer to a
workstation. A Windows NT server will take the role of client when it requires access to
resources that require host name resolution.
Host name resolution generally uses the following sequence:
1.
2.

The client checks to see if the name queried is its own.


The client then searches a local Hosts file, a list of IP address and names stored on the
local computer.
NOTE: The Hosts file location depends on the operating system:

3.
4.

Windows NT
Windows 95

%Systemroot%\System32\Drivers\Etc
<drive>\<Windows folder>

5.
6.
7.

Windows for Workgroups


<drive>\<Windows folder>
Windows 3.1
<drive>\<Windows folder>
MS-Client 3.0
<Boot volume>\Net
Lan Manager 2.2c Client

<Boot volume>\Net

Where %Systemroot% is the folder in which Windows NT is installed, <drive> is the


drive on which the OS is installed, and <boot volume> refers to a boot floppy disk or
drive C.
A sample hosts file, Hosts.sam, is installed with the TCP/IP protocol showing the proper
format.
8.
9.

Domain Name System (DNS) servers are queried.


If the name is still not resolved, NetBIOS name resolution sequence is used as a
backup. This order can be changed by configuring the NetBIOS node type of the client.

The Windows client will try each of these methods until it either successfully resolves the name
or exhausts these methods. Windows NT, Windows 95, and Windows for Workgroups clients
using Microsoft TCP/IP 3.11b follow this sequence. Lan Manager 2.2c or Microsoft Client 3.0
clients will not use NetBIOS name resolution as a backup.
For additional information, please see the following articles in the Microsoft Knowledge Base:
Q169141 NetBIOS and hostname resolution for MS-Client and LM 2.2c
When resolving names the client will skip methods for which it is not configured. For example, if
there is no hosts file on the system, then it will skip step #2 above and try a query to a DNS
server. If no DNS server IP addresses are entered in the client TCP/IP configuration, then the
client will skip to the next step in the sequence after DNS.
The method for changing host name resolution order differs among operating systems and
versions. These are documented in the Resource Kits for the specific operating systems, as well
as in the Microsoft Knowledge Base.
For additional information, please see the following articles in the Microsoft Knowledge Base:
Q171567 Windows NT 4.0 ServiceProvider Priority Values Not Applied
Q139270 How to Change Name Resolution Order on Windows 95 and Windows NT
Q119372 Setting the Name Resolution Search Order for TCP/IP-32

Troubleshooting
Problem: Client is unable to resolve a host name.
Troubleshooting steps:
If a client cannot resolve a host name, then it is best to verify the Host name resolution
sequence listed above that the client should be using. If the name does not exist in any of the
resources that the client uses, then you must decide to which resource to add it. If the name
exists in one of the resources, such as a DNS server or a Windows Internet Name Service
(WINS) server and the client is not resolving the name correctly, focus your attention on
troubleshooting that specific resource.
Also, confirm that the client is trying to resolve a host name and not a NetBIOS name. Many
applications have multiple methods that they can utilize to resolve names, this is especially true
of mail and database applications. The application may be configured to connect to resources
using NetBIOS. Depending on the client configuration the client may bypass host name
resolution. From there it will be necessary to either change the connection type to TCP/IP
sockets or to troubleshoot the problem as a NetBIOS issue.
Problem: Client resolves a name very slowly, or fails to resolve a name and takes a long time to
report a failure.

Troubleshooting steps:
Having DNS servers configured in a client's TCP/IP configuration, but the server is not available
to the client usually causes this. Because the TCP/IP protocol assumes an unreliable network, a
client will repeatedly attempt to connect to a DNS server before abandoning the attempted
query. The client will then attempt to query a second DNS server if one is configured and take
the same time to fail. Only then will the client step through to NetBIOS name resolution as
described above.
There are three ways to approach this issue.

If the host name is correctly entered in a host file, it will be resolved before the client
attempts to query DNS. This solution works well if DNS servers are temporarily
unreachable and there is a small number of host names that need to be resolved .
Manually configuring Hosts files for numerous clients may be prohibitive. -orIf DNS servers are available, but the DNS Server addresses in the clients TCP/IP
configuration are incorrect, then correcting these addresses will allow the clients to
contact the DNS servers immediately. Even if a DNS server reports that it cannot
resolve a name, this will happen much faster than if the client cannot reach a DNS
server at all. -orIf DNS servers are configured on the client, but these servers are permanently
unavailable, then remove the IP addresses of the DNS servers from the client
configuration. The client will then bypass the DNS lookup without delay. -orIf records in the DNS database are missing or incorrect, then there will be a delay as
DNS servers query other DNS servers before reporting that they cannot resolve the
name. This will usually cause a delay of just a few seconds.

For additional information on TCP/IP and name resolution, please see the following white paper
available on the Microsoft anonymous ftp server:
File Name: Tcpipimp2.doc
Location : ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/
Title : "Microsoft Windows NT 3.5/3.51/4.0: TCP/IP Implementation Details TCP/IP
Protocol Stack and Services, Version 2.0. "

Device Manager Displays Error


Code 10 for PCMCIA Network
Adapter
The information in this article applies to:

Microsoft Windows 98

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
After you install Windows 98, Device Manager may display an exclamation point in a yellow
circle next to the PC Card (PCMCIA) network adapter, with a status of "Error Code 10" in the
adapter's properties.

Cause
This behavior can occur on a Digital HiNote Ultra II laptop when the PC Card network adapter
uses memory that the computer's Basic Input/Output System (BIOS) has reserved.
Windows 98 determines a free range of memory and then assigns that range to the network
adapter for use. The network adapter driver may not be able to use the assigned range if it is
reserved by the BIOS.

Resolution
To work around this issue, you may be able to exclude the memory range that is being reserved
by the BIOS. To do this, follow these steps:
1.
2.
3.
4.
5.
6.
7.
8.
9.

Click Start, point to Settings, and then click Control Panel.


Double-click System.
On the Device Manager tab, double-click Computer.
Click the Reserve Resources tab, and then click Memory.
Click Add, type CA000 in the Start Value box, and then type CB000 in the End Value
box.
Click OK, and then click OK.
Click the PC Card network adapter, and then click Remove.
Click OK, and then click Close.
Restart your computer.

Err Msg: Unable to Open Port


The information in this article applies to:

Microsoft Windows 95
Microsoft Windows 98

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
When you try to use the Angia Personal Computer Memory Card International Association
(PCMCIA) modem, you may receive the following error message:
Unable to open port

Cause
This behavior can occur because the software included with the Angia PCMCIA modem alters an
entry in the System.ini file.

Resolution
To resolve this issue, edit the System.ini file to correct the entry that has been altered. To do so,
use the following steps:
1.
2.
3.
4.
5.

Click Start, click Run, type sysedit in the Open box, and then click OK.
On the Window menu, click System.ini.
In the [Boot] section of System.ini, edit the "Comm.drv=" line to read:

6.
7.

On the File menu, click Save, and then quit System Configuration Editor.
Restart your computer.

Comm.drv=Comm.drv

References
The third-party product discussed in this article is manufactured by a vendor independent of
Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or
reliability.

Yellow Exclamation Point Is


Displayed Over the IDE
Controller in Device Manager
The information in this article applies to:

Microsoft Windows 98
Microsoft Windows 98 Second Edition
Microsoft Windows Millennium Edition

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp
IMPORTANT: This article contains information about modifying the registry. Before you modify
the registry, make sure to back it up and make sure that you understand how to restore the
registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
Q256986 Description of the Microsoft Windows Registry

Symptoms
When you dock a laptop in an ICH2-M I/O Controller Hub, when you view the device in Device
Manager, a yellow exclamation point may be displayed on the IDE controller (and possibly the
network adapter). When you view the properties of the device, the following message is
displayed:
This device is either not present, not working properly, or does not have all the drivers
installed. (Code 10)
Try upgrading the device drivers for this device.

Cause
The ICH2-M I/O Controller Hub is a new device and it not directly supported by Windows 98 or
Windows Millennium Edition (Me). Therefore, the device is detected incorrectly.
ICH2-M is a multi-function controller which includes a PCI-PCI bridge. The PCI-PCI bridge is
incorrectly detected as a positive decode bridge. However, this bridge has the functionality of a
subtractive decode bridge. A subtractive bridge passes unclaimed input/output (I/O) and
memory cycles to the devices behind it, but a positive bridge does not.

Resolution
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To override the detection of the PCI bridge as positive bridge, follow these steps:
1.
2.

Start Registry Editor (Regedit.exe).


Locate and click the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\PCI
3.

On the Edit menu, click Add Value, and then add the following registry value:
Value Name: 24488086
Data Type: Binary
Value: 00 00 04 00

4.

Quit Registry Editor.

More Information
ICH2-M has multiple devices and functions. It contains a PCI-PCI bridge, a PCI-IDE controller, a
USB controller and an LPC (similar to an ISA) bridge. The ICH2-M PCI-PCI bridge behaves like a
subtractive decode bridge. It passes through all the cycles that are not claimed by the PCI-IDE
or USB controllers. Although it behaves like a subtractive decode bridge, software detects it as a
positive decode bridge. This behavior occurs because the ICH2M PCI-PCI bridge supports the
I/O window and memory window registers in its PCI configuration space (which retains the
values written by software).

No Logon Script When


Connecting with Dial-Up
Networking
The information in this article applies to:

Microsoft Windows 98
Microsoft Windows 95
Microsoft Windows Millennium Edition

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
On a Windows 95-based or Windows 98-based computer with the Client for Microsoft Networks
installed and configured to log on to a Windows NT domain, the following error message may
occur when you attempt to log on to the domain as part of the Windows startup and logon
process:
No domain server was available to validate your password. You may not be able to gain access
to some network resources.

In addition, if you attempt to use Dial-Up Networking to connect to your Windows NT network,
the following symptoms may occur, even though the Log On To Network option is selected in the
Dial-Up Networking connection you are using:

If you have a Windows NT login script configured, your login script may not be
processed when you connect to the network using Dial-Up Networking.
User profiles and system policies, if so configured, may not be updated or downloaded
from the network server.

Cause
These symptoms may occur if there is a network adapter present in the computer, but the
computer is not physically connected to the local area network (LAN). This may be the case
when you are logging on from a remote location with a portable computer that contains a PC
Card network adapter, but is not currently connect to the LAN.
When Windows starts, it checks for the presence of a network adapter. If one is found, it
attempts to log on to the Windows NT domain, if so configured, when you first log on to
Windows. Regardless of whether or not this initial attempt succeeds, Windows attempts to log
on to the domain only once during your Windows session.
If Windows does not detect the presence of a network adapter in the computer when you start
Windows, it does not attempt to log on to the Windows NT domain when you first log on to
Windows. If you later connect to the network using Dial-Up Networking, and have the Log On To
Network option enabled, Windows attempts to log on to the Windows NT domain and process
your login script. Again, this occurs only once during your Windows session, so if you disconnect
your Dial-Up Networking connection and then later reconnect without either restarting Windows

or logging off and logging on again, Windows does not repeat your domain logon and does not
process your login script again.

Resolution
To resolve this issue, use any of the following methods:

Before you log on to Windows on a computer that is not connected to the LAN, remove
the network adapter from the computer. This prevents Windows from attempting to log
on to the Windows NT domain when you first log on to Windows. Later, when you
connect to your network using Dial-Up Networking, Windows attempts to log you on to
the Windows NT domain and process your login script (if any).
Create a separate hardware profile for when you want to work while not connected to
the LAN. In the new hardware profile, disable the network adapter in Device Manager.
When you start the computer, you can choose between the two hardware profiles you
created. When your computer is not connected to your LAN, choose the hardware
profile in which the network adapter is disabled.
For additional information about these procedures, please see the following articles in
the Microsoft Knowledge Base:
ARTICLE-ID: Q141600
TITLE : How to Manually Create Hardware Profiles for Laptop Computers
ARTICLE-ID: Q128919
TITLE : Resources for Disabled Devices Not Freed Up

If your computer has a docking station that you always use when connected to your
LAN, and that you never use when you are not connected to the LAN, you can disable
the network adapter in the Undocked hardware profile, instead of creating a new profile
as described above.
Also, if the network adapter can be installed in the docking station instead of in the
laptop computer itself, you can install the network adapter in the docking station
instead of manually disabling it in the Undocked profile.
When you are not connected to the LAN, you may be able to bypass the initial Windows
logon by clicking Cancel in the Windows logon dialog box. In this case, you are not
logged on to the network or to the Windows NT domain unless and until you log on
using Dial-Up Networking. However, if you have user profiles enabled for your
installation of Windows, you should not use this method, because you may not receive
your user-specific settings unless you are logged on to Windows as yourself.

Common TCP/IP problems


Unable to map service name
Cause: The specified service name is not defined in your /etc/services file.
Unable to resolve host name
Cause: The specified host name is not defined.
Connection Refused
Cause: No one is listening at the target address. This indicates that the server program is not running
on the specified host system or it is using a different port number.
Fix: Check that client and server use the same port number or start the server program.
Address already in use
Cause: The port number the server program wants to use is already in use. Either the server is
already active, another server is using the same port number (caused by bad service name/port
number mapping) or there are still sockets stuck in TIME_WAIT state.
Fix: Check the port number the server program wants to use. If there are sockets in TIME_WAIT state
(probably caused by a crashed server process) you need to terminate all client processes and wait for
a minute until the operating system releases the port. You can use netstat to check for used sockets.

Error Message: MPREXE Not


Responding
The information in this article applies to:

Microsoft Windows Millennium Edition


Microsoft Windows 98 Second Edition
Microsoft Windows 98
Microsoft Windows 95

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

SYMPTOMS
When you log on to Windows, or after you install Windows, you may receive the following error
message, and your computer may stop responding (hang):
MPREXE not responding

CAUSE
This behavior can occur for any of the following reasons:

Your password list (.pwl) file is damaged.


A service or program that loads during the startup process conflicts with another service
or program.
You are using user profiles.
There is a hardware conflict on your computer.
A hardware driver on your computer is missing or damaged.
If profiles are enabled, Windows may not be able to contact the primary domain
controller's Netlogon share when looking for a Config.pol file. (Windows checks for a
Config.pol file even if policies are not used.)
Your primary domain controller (PDC) is not local to your Windows 95/Windows 98
clients.
A single user profile is corrupted.
Your network adapter is not correctly seated.
You are using a reserved word for your user name.

RESOLUTION
To resolve this issue, use the following methods. After each method, test to see if the issue is
resolved. If the issue continues to occur, use the next method.

Damaged Password List File


To re-create your password list file, use the following steps.
NOTE: If you are using a personal certificate, you should export it before renaming your .pwl

file. If you do not do so, it may be unavailable when you send e-mail messages. For more
information, see the following article in the Microsoft Knowledge Base:
Q190296 Unable to Use Personal Certificates in Outlook Express
1.
2.
3.
4.
5.
6.

Click Start, point to Find, and then click Files Or Folders.


In the Named box, type *.pwl, and then click Find Now.
Right-click the Username.pwl file, and then click Rename, where Username is the
name you use to log on to Windows.
Rename the Username.pwl file to Username.old, and then press ENTER.
Restart Windows.
When your computer restarts, you are prompted for a user name and password. If you
want, you can choose to create a null password. If you create a null password, you are
no longer prompted to log on when Windows starts. To create a null password, leave
the password box blank, click OK, and then click OK to confirm the password.

Conflicting Service or Program


To prevent a conflict with a service or program, "clean" boot your computer. For additional
information about clean booting, see the following articles in the Microsoft Knowledge Base:
Q156126 Troubleshooting Windows 95 Using Safe Mode
Q192926 How to Perform Clean-Boot Troubleshooting for Windows 98
Q281995 How to Troubleshoot Using the Msconfig Utility in Windows Me

User Profiles Are Being Used


To disable user profiles, follow these steps:
1.
2.
3.

Right-click Network Neighborhood, and then click Properties.


On the Access Control tab, click Share-Level Access Control, and then click OK.
Restart your computer.

Hardware Conflicts
To resolve hardware conflicts, follow these steps:
1.
2.
3.
4.

Click Start, point to Settings, and then click Control Panel.


Double-click System, and then click the Device Manager tab.
Double-click any device that displays a yellow exclamation point or red X.
Click to select the Disable This Device check box, and then click OK. Repeat steps 3
and 4 for each device that contains a yellow exclamation point or red X.

Missing or Damaged Driver


Download the latest drivers for your hardware from your hardware manufacturer. For
information about how to download the latest drivers for your hardware, view the
documentation included with your hardware, or contact your hardware manufacturer.

Enable Load Balancing


To prevent Windows from contacting the primary domain controller, enable load balancing. For
additional information about enabling load balancing, click the article number below to view the
article in the Microsoft Knowledge Base:
Q197986 How to Configure Windows 95 Policies with Load Balancing

Remote PDC

Enable load balancing on the Windows clients. For additional information about enabling load
balancing, click the article number below to view the article in the Microsoft Knowledge Base:
Q197986 How to Configure Windows 95 Policies with Load Balancing
NOTE: Even if you do not use policies for your clients, Windows checks the PDC's Netlogon
share for a policy file. If your PDC is not local to the client, or is across a slow wide area network
(WAN) link, it could cause a long delay during the logon process.

Corrupted User Profile


Log on as a user who is not currently experiencing the issue. Locate the affected user's profile in
the Windows\Profiles folder. Move that user's folder to another location. Log off and then log on
as the affected user to re-create the user profile.

Incorrectly Seated Network Adapter


A network adapter that becomes inoperable or unseated can also cause this error message. Try
to reseat, replace, or reinstall the network adapter.

Reserved Word Used as a User Name


The error message can also occur if you use one of the following reserved words as your user
name:

UX
CON
COM1
COM2
COM3
COM4
PRN
LPT1
LPT2
LPT3
LPT4

Change your user name to something other than a reserved word.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the
beginning of this article.

REFERENCES
For additional information about Mprexe.exe issues, see the following articles in the Microsoft
Knowledge Base:
Q151708 XCLN: Page Fault in Mprexe.exe When Starting Client
Q154092 Err Msg: MPREXE Caused an Invalid Page Fault in Kernel32.dll
Q166898 OL97: Windows 95 Service Pack 1 and Password Issues

Computer with Plug and Play


Network Adapter Is Not Found
on Network
The information in this article applies to:

Microsoft Windows 98

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
After you upgrade to Windows 98 on a Microsoft Windows 95-based computer with a Plug and
Play Network Interface Card (NIC) installed, your computer may not be visible in Network
Neighborhood to other computers on the network.

Cause
This problem occurs because the NetBEUI and IPX/SPX-compatible protocols may not bind to
the Windows 98 server component (Vserver.vxd) if a resource used by the network adapter,
such as an interrupt request line (IRQ), is reassigned by Plug and Play Configuration Manager
during system initialization. Under these conditions, the computer does not announce or register
its name on the network.
Your computer also does not internally register or export server and browser names to the
network. As a result, the computer does not appear in Network Neighborhood, it does not
recognize datagrams addressed to itself, and it does not allow remote computers to initiate
connections.

Resolution
A supported fix is now available from Microsoft, but it is only intended to correct the problem
described in this article and should be applied only to systems experiencing this specific
problem. This fix may receive additional testing at a later time, to further ensure product
quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that
you wait for the next Windows 98 service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the
fix. For a complete list of Microsoft Product Support Services phone numbers and information
about support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
NOTE: In special cases, charges that are normally incurred for support calls may be canceled, if
a Microsoft Support Professional determines that a specific update will resolve your problem.
Normal support costs will apply to additional support questions and issues that do not qualify for
the specific update in question.
The English-language version of this fix should have the following file attributes or later:

Date

Time

Version

Size

File name

-------------------------------------------------02/26/99 07:09pm 4.10.2000

112,912 Vserver.vxd

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files
may also contain additional files.

Status
Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the
beginning of this article. This problem was corrected in Windows 98 Second Edition.

More Information
When the NetBEUI or IPX/SPX-compatible protocol is installed, your computer may not be listed
in Network Neighborhood. If you attempt to connect to your computer by typing "net view
\\computername" (without the quotation marks) or "net use * \\computername\sharename"
(without the quotation marks) at the command prompt of another computer on the network,
you may receive the following error message:

Error 53: The computer name specified in the network path cannot be located. Make sure you
are specifying the computer name correctly, or try again later when the remote computer is
available.

If you type "net view" (without the quotation marks) at a command prompt shortly after
Windows 98 is started, you may receive the following error message:

Error 6118: The computer(s) sharing resources in this workgroup cannot be located. The
computer(s) might have been restarted. Wait a few minutes, and then try again. If the problem
persists, make sure your network-adapter settings are correct.

If you attempt to connect to the computer using Start, Run, and typing \\computername\share,
and then clicking OK in Windows 98, you may receive the error message:

The network name cannot be found.

If you attempt to map a network connection to the computer in Windows 98, you may receive
the error message:

The computer or sharename could not be found. Make sure you typed it correctly, and try again.

PROTOCOL SCENARIOS
The following scenarios assume that the Microsoft Client for Microsoft Networks is installed.
If only the IPX/SPX-compatible protocol is installed, other computers may not be able to browse
or connect to your computer. This occurs because the IPX 'NMPI' (Microsoft Name Management
Protocol on IPX) server-name announcement and SMB host browser announcements are not
broadcast.

If "NetBIOS support for IPX/SPX-compatible Protocol" is also enabled (this is the default for
Microsoft Windows 95, not Windows 98), the SMB host browser announcements are sent since
the NetBIOS transport typically binds (note that there is a distinction between NetBIOS support
for IPX/SPX and NetBEUI). In this situation, the computer can be browsed by other computers
using NetBIOS, but not by those without NetBIOS. In mixed Windows 95 and Windows 98
environments, enabling this can be a temporary solution to the problem, but it is only a partial
solution in environments with computers that are not NetBIOS capable.
With the NetBEUI protocol installed, the Add Name Query and Add Group Name values for the
names listed below that are normally registered by the "server" components of Windows 98 are
not sent.
For additional information about Windows 98 and Windows 98 Second Edition hotfixes, click the
article number below to view the article in the Microsoft Knowledge Base:
Q206071 General Information About Windows 98 and Windows 98 Second Edition
Hotfixes

Network Adapter Appears in Network


Properties When Disabled
The information in this article applies to:

Microsoft Windows 98

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
After you create a Hardware Profile with your network adapter or dial-up adapter disabled, the
adapter may still appear on the Configuration tab in Network Properties. The adapter may still
be visible even after you restart your computer.

Cause
This behavior can occur because the adapter is not removed unless you uninstall it. While it is
disabled, the adapter is still visible.

Status
This is by design.

Possible Problems with


Windows 98 Realtek Network
Adapter Driver
The information in this article applies to:

Microsoft Windows 98

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
If you use a Realtek network adapter, the network adapter may send an occasional corrupt data
packet.

Cause
This behavior can occur if you are using the Rtl8029.sys driver included with Windows 98.

Resolution
To resolve this issue, download an updated driver for your Realtek network adapter from the
following Realtek Web site:
http://www.realtek.com.tw
The third-party contact information included in this article is provided to help you find the
technical support you need. This contact information is subject to change without notice.
Microsoft in no way guarantees the accuracy of this third-party contact information.

More Information
The drivers included with Windows 98 are:
Rtl8029.sys 35,168 bytes
Rtl8129.sys 23,552 bytes
The third-party products discussed in this article are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or
reliability.

Network Configuration Is
Retained After Uninstalling
Network Components
The information in this article applies to:

Microsoft Windows Millennium Edition


Microsoft Windows 98 Second Edition
Microsoft Windows 98
Microsoft Windows 95

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
After you change the settings for some network components (such as TCP/IP), your changed
settings may not be retained when you next view the settings. This issue can occur even after
you remove and reinstall network components.

Cause
This issue occurs because some network settings (such as TCP/IP settings) are stored in the
sub-enumeration key of the network adapter bus enumerator in the registry and are accessed
from the Driver Information database (in Windows 95 or Windows 98) or the Hardware
Information database (in Windows Millennium Edition).

Resolution
To work around this issue:
1.
2.
3.

4.

Remove the network components that you want to reset. Click Start, point to Settings,
click Control Panel, and then double-click Network.
Click the network component that you want to remove, and then click Remove.
Click OK, and then restart your computer in Safe mode.
To restart the computer in Safe mode, for Windows 95 press the F8 key when "Starting
Windows 95" is displayed on the screen. For Windows 98 and Windows Millennium
Edition (Me), hold down the CTRL key during the boot process.
Locate the hidden Drvdata.bin and Drvidx.bin files in the Windows\Inf folder. Rename
these files to Drvdata.old and Drvidx.old.
If the hidden Drvdata.bin and Drvidx.bin files are not listed, you must disable the
hidden files setting. To do so, in Windows Explorer, click Folder Options on the Tools
menu, click the View tab, and then click to select the Show hidden files and folders
check box.

5.

For information about how to rename a file, click Start, click Help, click the Index tab,
type renaming, and then double-click the "Renaming files" topic.
Restart your computer. You see the message "Windows is now building the Driver
Information database" in Windows 95 and Windows 98 or "Windows is now building the
Hardware Information database" in Windows Me.

6.

Reinstall the network components that you removed.

More Information
For additional information about the Driver Information database or the Hardware Information
database, click the article number below to view the article in the Microsoft Knowledge Base:
Q275499 Troubleshooting Device Driver Issues by Using the Driver Information
Database

Troubleshooting Device Driver


Issues by Using the Driver
Information Database
The information in this article applies to:

Microsoft Windows Millennium Edition


Microsoft Windows 98 Second Edition
Microsoft Windows 98
Microsoft Windows 95

SUMMARY
This article describes the process that Windows Millennium Edition (Me), Windows 98 Second
Edition, Windows 98, and Windows 95 use to handle hardware devices and those devices'
drivers, and also describes how to troubleshoot the installation or re-installation of device
drivers.
For example, when you install or update a driver for a specific hardware device, the device may
not function correctly. If you try to install the driver for the device again, the device may still not
function correctly. This article describes what occurs when you install a device, and also
describes how to re-install the device driver after a failed installation attempt by rebuilding the
Driver Information or Hardware Information databases.

MORE INFORMATION
When you install a hardware device on your computer, the device passes information through
the basic input/output system (BIOS) to the operating system (Windows). Windows then
determines which driver Information (.inf) file to use to install the driver for the device, and
Windows determines the location of that .inf file. This process (bus enumeration) is the first step
in identifying the device; the operating system is notified through the BIOS that a device is
attached and is using a particular bus.
Windows then checks the registry to determine if that particular bus has an enumeration key
and if the enumeration key matches the hardware identifier that the device supplied through the
BIOS. If the enumeration key exists, the information is then used to install the appropriate
driver for the device. If there is no enumeration key, Windows adds the key to the registry with
the proper enumeration information (the hardware identifier, the hardware guide, and the
driver/inf information), which was supplied by the device hardware through the BIOS.
When additional drivers are installed for the device by either changing or updating the driver,
additional subkeys are added in the registry under that bus enumerator for that device.
NOTE: To view the history of the drivers that have been installed for a particular device, use the
Microsoft System Information utility:
1.
2.

Start the Microsoft System Information utility; click Start, point to Programs, point to
Accessories, point to System Tools, and then click System Information.
To view the drivers' history, double-click Components, and then click History.

In Windows 95, Windows 98, and Windows 98 Second Edition, the Driver Information database
contains all of the drivers that are listed under the enumerator for that device's bus. In Windows
Me, the same data is in the Hardware Information database. These databases are comprised of
the Drvdata.bin and Drvidx.bin files and are located in the Windir\Inf folder.
When drivers are updated or changed, a pointer in the Driver Information database or Hardware
Information database is changed; however, there is no check to determine if mismatched files

were installed during the driver installation. To work around this issue, you can rebuild the
Driver Information database or Hardware Information database to eliminate any pointers that
may cause mismatched files to be installed.
NOTE: Before you perform the following steps, ensure that you have the original installation
media (diskettes or CD-ROM) for the devices that you want to remove because you may be
prompted for the installation media when Windows restarts.
Before you rebuild the Driver Information or Hardware Information database:
1.
2.
3.

Start Windows in Safe mode.


Click Start, point to Settings, click Control Panel, and then double-click System.
Click the Device Manager tab, remove all of the instances of the device in question
from the device tree, and then click Close. If you are prompted to restart your
computer, click No.

To rebuild the Driver Information or Hardware Information database:


1.

2.

Rename the Drvdata.bin and Drvidx.bin files.


1. Click Start, point to Find, and then click Files Or Folders.
2. In the Named box, type drvdata.bin, and then click Find Now.
3. Right-click the Drvdata.bin file, click Rename, type a new name for the
Drvdata.bin file (for example, Drvdata.xxx), and then press the ENTER key.
4. Repeat steps a through c for the Drvidx.bin file, and then quit the Find tool.
Restart your computer normally.

After you restart your computer in normal mode, you are notified that Windows is building the
Driver Information database or the Hardware Information database. Your Plug and Play devices
are detected again, those devices' busses are enumerated again, and then Windows receives
the device information through the BIOS and prompts you to install the default driver for the
device. You may also be prompted to insert a disk for the device. If the driver that you want to
install is different than the default driver, you can choose the driver that you want to install.

No Network Adapter Listed


When Using Internet
Connection Sharing Wizard
The information in this article applies to:

Microsoft Windows 98 Second Edition


Microsoft Windows Millennium Edition

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

SYMPTOMS
When you try to establish Internet Connection Sharing by using a cable or DSL modem, you
may not have the option to select the Ethernet card as the Internet Connection.
You may receive a prompt to install a Dial-Up Networking adapter, or choose one.

CAUSE
This issue can occur if the Windows-based computer has one network adapter installed. Because
the cable or DSL modem acts as an Enthernet adapter, ICS uses that adapter for the network.

RESOLUTION
To resolve this issue, install a network adapter for the network.

STATUS
This is by design. To use Internet Connection Sharing (ICS) with a High Speed Connection
(Enthernet, DSL, Cable modem, etc.), the computer needs to have an adapter for the private
network (Intranet), and the public network (Internet). This requires at least two network
adapters.

Changes Remain After You


Click Cancel in Network
Properties
The information in this article applies to:

Microsoft Windows 98
Microsoft Windows 95

If this article does not describe your hardware-related issue, please see the following Microsoft
Web site to view more articles about hardware: If this article does not describe your hardwarerelated issue, please see the following Microsoft Web site to view more articles about hardware:
http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

Symptoms
If you change your domain in the properties for the Client for Microsoft Networks network client
or change your preferred server in the properties for the Client for NetWare Networks network
client, click OK, and then click Cancel, your changes remain in effect.
This behavior can occur if you have either an Intel EtherExpress 16 or Intel EtherExpress Pro 10
network adapter and the following network protocols installed: Network Basic Input/Output
System Enhanced User Interface (NetBEUI), Internetworking Packet Exchange/Session Packet
Exchange (IPX/SPX), and Transmission Control Protocol/Internet Protocol (TCP/IP).

Resolution
To work around this behavior, type your original domain or preferred server information in the
properties for the network client, click OK, and then click OK.

Status
Microsoft is researching this problem and will post new information here in the Microsoft
Knowledge Base as it becomes available.

Você também pode gostar