Problem: Windows XP takes a long time to open a shared disk or folder on a computer running Windows 95, 98, or Me<\/b><\/p>\n
Description:\u00a0<\/b>This is a different problem than My Network Places taking a\u00a0long time to open<\/a>. This problem occurs after you double click a shared disk or folder.<\/p>\n Possible Solutions:<\/b><\/p>\n This\u00a0Microsoft Knowledge Base article<\/a><\/u>\u00a0describes a bug in Windows 2000 Professional that might also exist in Windows XP. Disable searching for scheduled tasks by deleting this registry key:<\/p>\n HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\<\/p>\n CurrentVersion\\Explorer\\RemoteComputer\\NameSpace\\<\/p>\n {D6277990-4C6A-11CF-8D87-00AA0060F5BF}<\/p>\n \u00b7 Delete stored network passwords<\/p>\n 1. Click\u00a0Control Panel<\/b>\u00a0|\u00a0User Accounts<\/b>.<\/p>\n 2. Click your user name.<\/p>\n 3. Click\u00a0Manage my network passwords<\/b>.<\/p>\n 4. Click each entry and click\u00a0Remove<\/b>.<\/p>\n Description:\u00a0<\/b>The network card is configured to obtain an IP address automatically, and it\u2019s 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\u2019t communicate with the DHCP server:<\/p>\n Possible Solutions:<\/b><\/p>\n Problem: Renewing a DHCP lease fails, with error message \u201cAn error occurred while renewing interface <name>: The system cannot find the file specified.\u201d<\/b><\/p>\n Problem: Network connection configured to obtain an IP address automatically has IP address 0.0.0.0<\/b><\/p>\n Solution:\u00a0<\/b>Make sure that the\u00a0DHCP Client<\/i>\u00a0service is running:<\/p>\n Thanks to Lightcap, who suggested this fix in a news group message.<\/p>\n Problem: Computers can ping each other by IP address, but not by name.<\/b><\/p>\n Description:\u00a0<\/b>An attempt to ping a computer by name gets the message\u00a0Ping<\/i>\u00a0request could not find host <computer name>. Please check the name and try again<\/i>.<\/p>\n Solution:\u00a0<\/b>Make sure that\u00a0NetBIOS Over TCP\/IP<\/a><\/u>\u00a0is enabled.<\/p>\n Error Message: Network Cable Unplugged<\/b><\/p>\n Description:\u00a0<\/b>Don\u2019t take this message literally \u2013 there are many causes besides not having a cable physically plugged into the network card. The message really means that the network card doesn\u2019t detect a live link to another device on the other end of the cable.<\/p>\n Possible Solutions:<\/b><\/p>\n Error Message:\u00a0xxxxx<\/i>\u00a0is 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\u00a0<\/b>.<\/p>\n Description:\u00a0<\/b>xxxxx<\/i>\u00a0is a computer or workgroup name. This is a generic networking error message that doesn\u2019t provide much, if any useful information. It should be followed by a more specific message.<\/p>\n Error Message: The list of servers for this workgroup is not currently available.<\/b><\/p>\n Solution:\u00a0<\/b>Make sure that the\u00a0Computer Browser<\/i>\u00a0service is running on at least one Windows XP computer on the network:<\/p>\n Error Message: Unable to browse the network. The network is not accessible.<\/b><\/p>\n Description:\u00a0<\/b>This error message appears on a computer running Windows 95\/98\/Me.<\/p>\n Solution:\u00a0<\/b>Make sure that:<\/p>\n Problem: Internet Connection Sharing Clients Can\u2019t Access Some Web Sites<\/b><\/p>\n Description:\u00a0<\/b>This is a common problem when the host computer has a DSL connection that uses\u00a0PPP Over Ethernet<\/i>\u00a0(PPPoE), due to a bug in the Windows XP PPPoE client.<\/p>\n Solution:\u00a0<\/b>Many people have reported solving the problem by using the\u00a0RASPPPoE\u00a0<\/a><\/i>client<\/a>\u00a0instead of XP’s. It\u2019s available for\u00a0free download<\/a><\/u>\u00a0from its author.<\/p>\n Problem: Computer A Can Ping Computer B, but not Vice Versa<\/b><\/p>\n Solution:\u00a0<\/b>This is almost always caused by an improperly configured firewall on Computer A.<\/p>\n Problem: XP’s Network Setup Wizard Says That No Network Card Is Installed<\/b><\/p>\n Solution:\u00a0<\/b>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\u2019s TCP\/IP properties manually. Here\u2019s how to do it for\u00a0Windows 95\/98\/Me<\/a><\/u>,\u00a0Windows 2000<\/a><\/u><\/i>, and\u00a0Windows XP<\/a><\/u>. Then set the workgroup name to MSHOME.<\/b><\/p>\n Problem: One Computer Can\u2019t Access Some Web Sites, but Other Computers Can<\/b><\/p>\n Solution:\u00a0<\/b>Look for the Windows\u00a0Hosts<\/i>\u00a0file on the problem computer:<\/p>\n 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\u00a0Hosts<\/i>, with no file type. If your editor saves it as\u00a0Hosts.txt<\/i>, rename it to just\u00a0Hosts<\/i>.<\/p>\n 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.<\/p>\n Error Message –\u00a0<\/b>PING<\/b>: transmit failed, error code 65<\/b><\/p>\n Description:\u00a0<\/b>This error message occurs when you try to ping any IP address.<\/p>\n\n
Problem: Network Connection Has IP Address 169.254.x.x<\/b><\/h3>\n
\n
\n
\n\n
\n
\n\n
\n\n
\n
\n
\n
\n\n
\n