Windows Xp Network Troubleshooting

Windows XP Network Troubleshooting

Troubleshooting TCP/IP - Detailed Steps This article shows how to troubleshoot TCP/IP connectivity between computers on a Windows network. If you haven’t already done so, disable XP’s Internet Connection Firewall on all local area network connections, and remove all firewall programs on the network. Improperly configured firewalls are the most common cause of TCP/IP problems.

Open a Command Prompt Window For many of these steps, you’ll be typing at the command prompt. To open a command prompt window in Windows 2000 or XP, click Start | Run, type cmd in the box, and click OK. To open a command prompt window in Windows 95, 98, or Me, click Start | Run, type command in the box, and click OK. Type one command per line, and press Enter after each one to execute it. To close the command prompt window, use the exit command.

Determine the TCP/IP Settings

Determine the TCP/IP settings of each computer on the local area network. In XP, open the Network Connections folder, right click the LAN connection, and click Status | Support | Details. For example, here are the Status and Details views for the LAN connection on an Internet Connection Sharing host. In Windows 95/98/Me, click Start | Run, type winipcfg

in the box, and click OK. Select the LAN adapter from the menu, and click More Info. Here’s the winipcfg view for an ICS client running Windows Me. You can also see the TCP/IP settings from the command prompt. This is especially convenient if a computer has more than one network adapter. Use the ipconfig /all command, which is available in all versions except Windows 95. The output from this command can be long, so it’s best to write it to a file. Specify the file name in the command this way: ipconfig /all >ipconfig.txt Here’s the output for a Windows XP ICS host that’s sharing its cable modem connection:

Description of TCP/IP Settings Here are the TCP/IP settings that are used in network troubleshooting: •

•

•

•

IP Address – Unique address assigned to a network adapter. A computer with multiple network adapters has an IP address for each one, and each one must be in a different subnet. Subnet Mask – Used in conjunction with the IP address to determine which subnet an adapter belongs to. At the simplest level, communication is only possible between two network adapters when they’re in the same subnet. Default Gateway - IP address of a computer or router, on one of this computer’s local area networks, that knows how to communicate with subnets not present on this computer. For an Internet connection, the default gateway is a router belonging to your Internet service provider, and all access to sites on the Internet goes through it. For an ICS client, the default gateway is the ICS host. If you use a hardware router, it serves as the default gateway. DHCP Server – If an adapter is configured to obtain an IP address automatically, this is the address of the server that provides it. It could be your ISP, an ICS host, or a hardware

•

router. DNS Servers – IP address of one or more Domain Name Server computers. DNS servers translate Internet names (like www.practicallynetworked.com) to their IP addresses (like 63.146.109.227).

Subnets See our article on subnets for a brief description of how they work. For more details, see this Microsoft Knowledge Base article. If two computers are supposed to be on the same subnet, but aren’t, something is wrong with the network hardware or software configuration. This is most likely to happen when one of them receives an IP address of 169.254.x.x, which indicates that: • • •

It’s configured to obtain an IP address automatically. It couldn’t find a DHPC server on the network to make the assignment. Windows assigned it an Automatic Private IP Address.

See our article on Specific Networking Problems and Their Solutions for more information.

Pinging

The ping command is the basic tool for testing TCP/IP connectivity. It sends a special packet (called ICMP Echo) to a particular IP address and looks for a reply. If everything is working right, the reply comes back. If not, the ping times out in a few seconds. By default, the ping command repeats the process four times. Here’s an example of an ICS client computer pinging a Windows XP Home Edition ICS host, using the host’s IP address and its computer name. When ping fails, you’ll see one of these error messages: •

Request timed out - The IP address is valid, but there’s no

reply from it. If the IP address is on a local area network, the most likely cause is a firewall program blocking the ping. •

Unknown host or Ping request could not find host - The computer name doesn’t exist on the local area network. Make sure that NetBIOS over TCP/IP is enabled.

•

Destination host unreachable – The IP address isn’t on a local area network, and the default gateway can’t access it. Either there’s no default gateway, its address is wrong, or it isn’t functioning.

Pinging the Local Area Network Here is a series of ping commands to use in finding where a problem occurs on a local area network. Run them in the order shown, and don’t go on to the next command until all of the previous commands work properly. In this example: • •

The computer being tested is named Winxp, with IP address 192.168.1.101. There’s another computer on the network, named Win98, with IP address 192.168.1.123

Substitute the appropriate IP addresses and computer names for your network. Command

Target

What Ping Failure Indicates

ping 127.0.0.1

Loopback address

Corrupted TCP/IP installation

ping localhost

Loopback name

Corrupted TCP/IP installation

ping 192.168.1.101

This computer’s IP address

Corrupted TCP/IP installation

ping winxp

This computer’s name

Corrupted TCP/IP installation

ping 192.168.1.123

Another computer’s IP address

Bad hardware or NIC driver

ping win98

Another computer’s

NetBIOS name resolution

name

failure

To fix a corrupted TCP/IP Installation on Windows XP, follow the steps in this Microsoft Knowledge Base article. For Windows 95/98/Me, un-install the TCP/IP protocol in Control Panel | Network, reboot, and re-install it. If that doesn’t fix it, use this procedure on Windows 95 or 98.

Pinging the Internet You can also use ping to find a problem with Internet access. Run these commands in the order shown, and don’t go on to the next command until all of the previous commands work properly. Use the Default Gateway and DNS Server addresses that you got from the winipcfg or ipconfig /all command.

Command

Target

What Ping Failure Indicates

ping w.x.y.z

Default Gateway

Default Gateway down

ping w.x.y.z

DNS Server

DNS Server down

ping w.x.y.z

Web site IP address

Internet service provider or web site down

ping www.something.com

Web site name

DNS Server down or web site down

How to reset "Internet Protocol (TCP/IP)" in Windows Server 2003

SUMMARY If you click the Internet Protocol (TCP/IP) entry in the This connection uses the following items list that is displayed in the Local Area Connection properties, you may notice that the Uninstall button is unavailable (disabled). This behavior occurs because the Transport Control Protocol/Internet Protocol (TCP/IP) stack is a core component of Microsoft Windows Server 2003 and cannot be removed. In some scenarios, you may want to reinstall TCP/IP to return the TCP/IP stack to its original state. You can use the Netsh.exe utility to reset the TCP/IP stack to the same conciliation that it was when you first installed the operating system. Back to the top

MORE INFORMATION The Netsh.exe utility (netsh) is a command-line scripting tool that you can use to configure and monitor Windows Server 2003 networking. This tool gives you an interactive network shell interface.

You can use the reset command in the Internet Protocol (IP) context of this utility to rewrite the following TCP/IP-related registry keys:

• SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ • SYSTEM\CurrentControlSet\Services\DHCP\Parameters\ If you run this command, you get the same result as if you removed and reinstalled the TCP/IP protocol. Warning The netsh int ip reset command will reset all IP information, default gateway information, and DNS server information. Before you restart the computer after you run this command, you must configure your TCP/IP settings. Otherwise, you may not be able to connect to the computer remotely. Back to the top

Command syntax netsh int ip reset [log_file_name] To use the netsh command to reset the TCP/IP stack, you must specify a log file name in which the results of the command are recorded. If you enter either of the commands that are described in the "Command Samples" section of this article, the TCP/IP stack on the current computer is reset, and the activities of that action are recorded in the Resetlog.txt file that is specified in the command line. In the first example, the log file is created in the current folder; in the second example, a complete path to the Resetlog.txt log file is specified. Note If an existing log file with the same name is present in the target folder, the new log file information is appended to the end of the existing file. Back to the top

Command samples The following examples describe how to use the netsh command to reset the TCP/IP protocol stack.

Example 1 1. Click Start, and then click Run. 2. In the Open box, type cmd, and then click OK. At the command prompt, type the following command, and then press ENTER: 3. netsh int ip reset resetlog.txt NOTE: In the preceding command, "int" is the shortened form of the interface command. 4. Type exit, and then press ENTER. Example 2 1. Click Start, and then click Run. 2. In the Open box, type cmd, and then click OK. 3. At the command prompt, type the following command, and then press ENTER:

4.

netsh int ip reset c:\resetlog.txt Type exit, and then press ENTER.

To view help for the command, type the command, type a space, and then type ?. Additional help is available for commands in the sub-contexts of the netsh command. For example, to view help for the netsh commands that are described in the preceding section, type the following commands at the command prompt:

• • • •

Type Type Type Type

netsh netsh netsh netsh

?, and then press ENTER. int ?, and then press ENTER. int ip ?, and then press ENTER. int ip reset ?, and then press ENTER.

Back to the top

Example of the log file for NETSH INT IP RESET The following text is an example of the log file that is generated by netsh if you run the ip reset command. The actual log file may vary depending on the configuration of the computer on which you run the command. Typically, no actions are logged in the file if the TCP/IP registry keys have not been altered from their original configuration.

reset SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\15\RegLocation old REG_MULTI_SZ = SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\Dh cpDomain SYSTEM\CurrentControlSet\Services\TcpIp\Parameters\DhcpDomain added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{2DDD0 11E-B1B6-4886-87AC-B4E72693D10C}\NetbiosOptions added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{BAA9D 128-54BB-43F6-8922-313D537BE03E}\NetbiosOptions reset SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{BD285 9BA-B26A-4E2B-A3FE-3D246F90A81A}\NameServerList old REG_MULTI_SZ = 10.1.1.2 deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\AddressType added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\DefaultGatewayMetric added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\DisableDynamicUpdate deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\DontAddDefaultGateway reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\EnableDhcp

old REG_DWORD = 0 added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\NameServer added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\RawIpAllowedProtocols added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\TcpAllowedPorts added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011EB1B6-4886-87AC-B4E72693D10C}\UdpAllowedPorts added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\DisableDynamicUpdate reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\EnableDhcp old REG_DWORD = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\IpAddress old REG_MULTI_SZ = 12.12.12.12 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\IpAutoconfigurationAddress deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\IpAutoconfigurationMask deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\IpAutoconfigurationSeed reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\RawIpAllowedProtocols old REG_MULTI_SZ = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\SubnetMask old REG_MULTI_SZ = 255.255.255.0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\TcpAllowedPorts old REG_MULTI_SZ = 0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C36EB9-4936-B991-04DA31024C4E}\UdpAllowedPorts old REG_MULTI_SZ = 0 added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\AddressType added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\DefaultGatewayMetric added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\DisableDynamicUpdate deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\DontAddDefaultGateway reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\EnableDhcp old REG_DWORD = 0 added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\NameServer added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\RawIpAllowedProtocols added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\TcpAllowedPorts added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D12854BB-43F6-8922-313D537BE03E}\UdpAllowedPorts reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\DefaultGateway old REG_MULTI_SZ = 10.1.1.2 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\DefaultGatewayMetric old REG_MULTI_SZ = 0 added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\DisableDynamicUpdate reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\EnableDhcp

old REG_DWORD = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\IpAddress old REG_MULTI_SZ = 10.1.1.1 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\IpAutoconfigurationAddress deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\IpAutoconfigurationMask deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\IpAutoconfigurationSeed reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\NameServer old REG_SZ = 10.1.1.2,10.1.1.3 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\RawIpAllowedProtocols old REG_MULTI_SZ = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\SubnetMask old REG_MULTI_SZ = 255.255.255.0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\TcpAllowedPorts old REG_MULTI_SZ = 0 reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BAB26A-4E2B-A3FE-3D246F90A81A}\UdpAllowedPorts old REG_MULTI_SZ = 0 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGateway Default deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevoluti on Note In Windows Server 2003 Service Pack 1, you can use the netsh winsock reset command to repair Winsock. Warning Programs that access or monitor the Internet, such as antivirus programs, firewall programs, or proxy clients may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality.

Problem: Windows XP takes a long time to open a shared disk or folder on a computer running Windows 95, 98, or Me Description: This is a different problem than My Network Places taking a long time to open. This problem occurs after you double click a shared disk or folder. Possible Solutions:

•

Disable searching for scheduled tasks

This Microsoft Knowledge Base article describes a bug in Windows 2000 Professional that might also exist in Windows XP. Disable searching for scheduled tasks by deleting this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\ CurrentVersion\Explorer\RemoteComputer\NameSpace\ {D6277990-4C6A-11CF-8D87-00AA0060F5BF} · Delete stored network passwords 1. Click Control Panel | User Accounts. 2. Click your user name. 3. Click Manage my network passwords. 4. Click each entry and click Remove

Problem: Network Connection Has IP Address 169.254.x.x Description: The network card is configured to obtain an IP address automatically, and it’s connected to a network with a DHCP server: hardware router, another computer running Internet Connection Sharing, cable modem, DSL modem, etc. But it gets a 169.254.x.x IP address, which indicates that it can’t communicate with the DHCP server: Possible Solutions:

• • • •

•

Connect the computer using a different Ethernet cable or hub/switch/router port. Download and install the latest firmware for the hardware router. Disable XP’s Internet Connection Firewall on the local area network connection. The card is configured to automatically sense network speed and duplex mode, but auto-sensing is failing. Configure the speed and duplex mode manually. For example, most switches and routers use 100 Mb speed and full duplex. To make the settings, right click the network connection and click Properties | Configure | Advanced. Un-install the network card and move it to a different slot.

•

If you have a cable modem connection, turn off the computer, turn off the cable modem, and wait a few minutes. Turn on the cable modem, and then turn on the computer.

Problem: Renewing a DHCP lease fails, with error message “An error occurred while renewing interface : The system cannot find the file specified.” Problem: Network connection configured to obtain an IP address automatically has IP address 0.0.0.0 Solution: Make sure that the DHCP Client service is running:

1.

Right click My Computer, and click Manage.

2. 3. 4. 5.

Double click Services and Applications. Double click Services. Double click DHCP Client. If the Service status is Stopped, click Start. Set the Startup type to Automatic.

Thanks to Lightcap, who suggested this fix in a news group message.

Problem: Computers can ping each other by IP address, but not by name. Description: An attempt to ping a computer by name gets the message Ping request could not find host . Please check the name and try again. Solution: Make sure that NetBIOS Over TCP/IP is enabled.

Enable NetBIOS Over TCP/IP (NetBT) Windows peer-to-peer networks use the NetBIOS (Network Basic Input/Output System) applications programming interface for File and Printer Sharing. NetBIOS names identify computers on the network. NetBIOS broadcasts locate computers and shared disks and folders on the network and allow them to appear in My Network Places and Network Neighborhood. NetBIOS is not the same thing as NetBEUI (NetBIOS Extended User Interface):

• • • •

NetBIOS is an applications programming interface (API). NetBEUI is a transport protocol. File and Printer Sharing requires NetBIOS. Nothing in Windows networking requires NetBEUI.

The NetBIOS API must be enabled over one of the transport protocols: NetBEUI, TCP/IP, or NWLink IPX/SPX. Networks that use TCP/IP for File and Printer Sharing require NetBIOS Over TCP/IP, also known as NetBT. To enable NetBIOS Over TCP/IP on Windows XP and Windows 2000:

1. 2. 3. 4.

Open the Network Connections folder. Right click the local area network connection and click Properties. Double click Internet Protocol (TCP/IP). Click Advanced.

5. 6.

Click WINS. Click the Enable NetBIOS Over TCP/IP button.

To enable NetBIOS Over TCP/IP on Windows 95/98/Me:

1. 2. 3. 4.

Click Start | Settings | Control Panel | Network. Double click the TCP/IP->adapter entry for the local area network.

Click NetBIOS. The I want to enable NetBIOS over TCP/IP box is normally checked and grayed out. If it’s un-checked, click the box to put in a check mark.

Error Message: Network Cable Unplugged Description: Don’t take this message literally – there are many causes besides not having a cable physically plugged into the network card. The message really means that the network card doesn’t detect a live link to another device on the other end of the cable. Possible Solutions:

• • • •

Download and install the latest network card driver program. Check the cabling – a bad cable will prevent link detection. Substitute a cable that’s known to be good. Check the link lights on the device on the other end of the cable, whether it’s a hub, switch, router, or a NIC in another computer. It should show a live link to the NIC. If it doesn’t, try a different port. Auto-detecting speed and duplex mode can be unreliable. Set them manually. Most routers and switches use 100Mb, full duplex. Hubs can only use half duplex.

Error Message: xxxxx is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission . Description: xxxxx is a computer or workgroup name. This is a generic networking error message that doesn’t provide much, if any useful information. It should be followed by a more specific message. Error Message: The list of servers for this workgroup is not currently available. Solution: Make sure that the Computer Browser service is running on at least one Windows XP computer on the network:

1. 2. 3. 4. 5.

Right click My Computer, and click Manage. Double click Services and Applications. Double click Services. Double click Computer Browser. If the Service status is Stopped, click Start. Set the Startup type to Automatic.

Error Message: Unable to browse the network. The network is not accessible. Description: This error message appears on a computer running Windows 95/98/Me. Solution: Make sure that:

•

The user is logged on. Click Start | Log Off <user name> and log back on.

•

The Computer Browser service is running on at least one Windows XP computer on the network.

Problem: Internet Connection Sharing Clients Can’t Access Some Web Sites Description: This is a common problem when the host computer has a DSL connection that uses PPP Over Ethernet (PPPoE), due to a bug in the Windows XP PPPoE client. Solution: Many people have reported solving the problem by using the RASPPPoE client instead of XP's. It’s available for free download from its author. Problem: Computer A Can Ping Computer B, but not Vice Versa Solution: This is almost always caused by an improperly configured firewall on Computer A. Problem: XP's Network Setup Wizard Says That No Network Card Is Installed Solution: XP's Network Setup Wizard sometimes fails to recognize an installed and working network card. This is because the NIC's driver program doesn't respond correctly to all of the queries that the Wizard makes when it's looking for a NIC. Configure the card’s TCP/IP properties manually. Here’s how to do it for Windows 95/98/Me, Windows 2000, and Windows XP. Then set the workgroup name to MSHOME. Problem: One Computer Can’t Access Some Web Sites, but Other Computers Can Solution: Look for the Windows Hosts file on the problem computer:

• • •

Windows 95/98/Me: C:\Windows\Hosts Windows 2000: C:\WinNT\System32\Drivers\Etc\Hosts Windows XP: C:\Windows\System32\Drivers\Etc\Hosts

Open it with a text editor and you'll probably find lines with the names of the sites that you can't access. Delete those lines, save the file, and try again. If those are the only lines in the file, delete the file. Be sure to save it with a file name of just Hosts, with no file type. If your editor saves it as Hosts.txt, rename it to just Hosts. The Hosts file can be created by "web accelerator" programs that store name-to-IP address translations. This might speed up access by a tiny amount, but it causes problems when a site's IP address changes. Error Message - PING: transmit failed, error code 65 Description: This error message occurs when you try to ping any IP address. Solution: A firewall program has been incompletely removed. Re-install it, then remove it as described in our article on removing firewalls. Problem: A shared disk or folder doesn’t appear in My Network Places Description: The disk or folder is shared correctly on another computer, but it doesn’t appear. Solution 1: Click Add a network place and follow the prompts to add it. Browse to it through Entire Network, or specify the path name using the form \\computer\share. Solution 2: Click View workgroup computers, then click the computer that has the shared disk or folder. Error Message: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. Description: Windows XP Home Edition allows a maximum of 5 other computers to access its shared disks and folders simultaneously. Windows XP Professional allows a maximum of 10. This message appears when the maximum has been reached and another computer requests access. Solution: There’s no way to change the limit. A computer that’s already connected must close its connection before another can have access. Error Message: An error has occurred while trying to share . The Server service is not started. The shared resource was not created at this time. Solution: To start the Server service:

1. 2. 3. 4. 5. 6. 7.

Right click My Computer and select Manage. Double click Services and Applications. Double click Services. Scroll down the list of services and double click Server. Click the Start button. Set the Startup type to Automatic. Click Apply and OK.