Error - View Single Post

**Anilrgowda** · 19-Dec-2006, 10:20 PM

Windows XP Networking

I have been recieving a lot of questions in email about networking problems, I decided to make this page to help everyone find articles relevant to the problems they are having, from simple home networking problems, the differences in networking in XP and other verions of windows, setting up internet connection sharing, troubleshooting ICS, setting up your personal firewall and any number of other problems. Hope this helps.

Cannot Map a Network Drive Under Different User Credentials

If you use the Map Network Drive Wizard to connect to a network share by using different user credentials and you use the browse functionality to locate the network share, you may receive the following error message:
The network folder specified is currently mapped using a different user name and password. To connect using a different user name and password, first disconnect any existing mappings to this network share.
You receive this error message even though you are not aware of making a different connection.

troubleshooting Home Networking in Windows XP (Q308007)

This article describes how to troubleshoot Windows XP Home Networking. When you encounter such issues, the best first step is to use the Home and Small Office Networking Troubleshooter in Help and Support Center in Windows XP. To use the Home and Small Office Networking Troubleshooter in Help and Support Center:
Click Start , and then click Help and Support .
Under Pick a Help Topic , click Networking and the Web .
Under Networking and the Web , click Fixing networking or Web problems , and then click Home and Small Office Networking Troubleshooter .
Answering the questions in the troubleshooter can guide you to a solution. If the troubleshooter does not address the particular that issue you are encountering, continue with the troubleshooting recommendations in this article.
Windows XP setting crashes dorm networks

Dartmouth students experiencing network difficulties over the past few weeks may themselves be causing the problem. According to Computing Services, laptop computers running Windows XP that are connected to the Internet through both the wireless and cable networks are crashing residence cluster connections when a "network bridging" feature is enabled.
Bill Brawley, director of user communications at Computing Services, said that the problem begins when a laptop with Windows XP switches between the wireless Internet card and an Ethernet cable connection.
"There are two sort of network interfaces then," Brawley said. "The bridge feature is handy on a home network, but on our network it bridges those two devices and sets up a loop in which packets travel between the networks, sort of a feedback loop. This messes up both networks for the whole building."
Windows XP Networking Features and Enhancements

With Windows XP, one of Microsoft's primary focuses was to improve the user and administrator experience when networking personal computers. Many of the networking features added or enhanced in Windows XP serve that end.
As more and more home computer users are adding second and third PCs, or bringing laptops home from work, the need to connect these computers together and share resources has increased. Many of the features discussed in this paper, including the Networking Setup Wizard, Network Bridging support, and Network Diagnostics, make home networking easier and more convenient.
Connecting these newly networked home computers to the Internet safely is often the next step following creation of the home network. Some of the networking features added to Windows XP makes the PC the best gateway to the Internet for the home network. These features include Internet Connection Sharing, Point-to-Point Protocol over Ethernet support (PPPOE), and Internet Connection Firewall.
Wireless LAN Technologies and Windows XP

The availability of wireless networking and wireless LANs can extend the freedom of a network user, solve various problems associated with hard-wired networks and even reduce network deployment costs in some cases. But, along with this freedom, wireless LANs bring a new set of challenges.
There are several wireless LAN solutions available today, with varying levels of standardization and interoperability. Wide industry support for interoperability and operating system support address some of the deployment questions for wireless LANs. Still, wireless LANs present us with new challenges around security, roaming and configuration. The rest of this article discusses these challenges and presents some possible solutions, focusing on how Windows XP will play an important role in providing those solutions with support for zero configuration, 802.1x security and other innovations.
Windows XP and Broadband Internet Connections

Windows XP has built–in support for the Point–to–Point Protocol over Ethernet (PPPoE). This allows a computer running Windows XP to connect to any Internet service provider whose access equipment supports PPPoE for broadband Internet connections, which includes both cable modem and Digital Subscriber Line (DSL) technologies. Configuring Windows XP for a PPPoE connection is as simple as creating a new connection using the New Connection Wizard. Internet service providers that support industry–standard PPPoE server functionality will work with the PPPoE client supplied in Windows XP.
Internet service providers (ISPs) that use broadband Internet access technologies deployed in a bridged Ethernet topology, such as cable modem or Digital Subscriber Line (DSL), need a way to distinguish individual users so that Internet usage can be accounted for, and, if appropriate, billed to individual users. Because Ethernet is inherently a shared access technology, it provides no such facilities. By combining the Point–to–Point Protocol (PPP) with Ethernet, an ISP can use Ethernet topologies and still maintain the individuality of user access as if they were using a dial–up modem. The type of access and choice of service are managed on a per–user basis, rather than a per–site or per–access device basis. The combination of PPP and Ethernet is known as Point–to–Point Protocol over Ethernet (PPPoE) and is defined in the Internet Engineering Task Force RFC 2516.
Using Group Policy Settings with Windows XP Home Networking Features

Fortunately, Windows XP supports the use of different user accounts and location-aware Group Policy settings. By using a different user account when logging on to the computer when it is connected to the home network (such as a local user account), the organization intranet policies that restrict or prohibit the ability for you to change configuration settings within the Network Connections folder do not apply.
Group Policy settings to allow the use of ICS, ICF, and Network Bridge are tied to the network to which the computer was connected when the Group Policy settings were applied. Network administrators can define Group Policy settings that restrict or disable networking features that can cause problems with network connectivity and apply to the computer when it is connected to the organization intranet. When the user takes the computer home and connects it to their home network, the organization intranet Group Policy settings are not applied, allowing the computer to perform Internet connection and bridging functions not allowed on the organization intranet.
Overview of Network Address Translation (NAT) in Windows XP

As more homes and small businesses add computers they are finding networking is an extremely powerful tool for sharing computer resources. An Internet connection is one of the more precious resources on the network and is likely to be shared. To do this and to enjoy an inexpensive, easy to manage, home or small office network, Internet gateways are being deployed. Internet gateways often provide NAT (Network Address Translation) as a means of connecting multiple hosts to the Internet sharing a single public IP address. Unfortunately, this solution breaks many types of networked applications—as will be described in this paper.
NAT Traversal technology has been created to enable network applications to detect the presence of a local NAT device. Once detected, the application can then configure the NAT, defining the appropriate mappings to solve their compatibility issues.
Windows XP Bridging and Media Support for Home Networking

Windows XP supports a wide variety of networking technologies to connect computers in a home network. In a home with multiple computers that have different types of network adapters, such as a few computers on an Ethernet hub and a few computers that use wireless, attempting to connect them together can be a challenge.
Each set of computers that cannot be directly attached together because they exist on separate hubs or cabling systems or are separate technologies define a LAN segment.
Wireless 802.11 Security with Windows XP

IEEE 802.11, 802.11a and 802.11b (also known as Wi-Fi) are wireless local area networking (LAN) standards that supply 1 megabit per second or above of bandwidth. Because these networks differ from wired LANs several issues unique to wireless LAN deployment must be addressed.
The major deployment issue for IEEE 802.11 wireless LANs is managing access to the network and privacy of the wireless traffic. The IEEE 802.11 standard defines the use of WEP pre-shared keys for access control and privacy. However, managing pre-shared keys across thousands of workstations is infeasible.The Internet Connection Firewall Can Prevent Browsing and File Sharing (Q298804)

When you enable the Internet Connection Firewall (ICF) feature, and then attempt to browse the Internet by means of My Network Places , you are unsucessful. Also, if you use the net view \\ computername command, you can receive the following error message:
System error 6118 has occurred. The list of servers for this workgroup is not currently available.
This behavior can occur because the ICF closes, by default, the ports for file sharing. The Master Browser attempts to reconnect to the client computer to send the Browse list, but the firewall prevents this reconnection attempt.
How to Troubleshoot TCP/IP Connectivity with Windows XP (Q314067)

There are utilities that can provide useful information when you are trying to determine the cause of TCP/IP networking problems under Windows XP. This article lists recommendations for using these utilities to diagnose network problems. Although this list is not complete, the list does provide examples that show how you can use these utilities to track down problems on the network.
When you troubleshoot a TCP/IP networking issue, begin by checking the TCP/IP configuration on the computer that is experiencing the problem. Use the ipconfig command to get the host computer configuration information, including the IP address, the subnet mask, and the default gateway.
How to Reset Internet Protocol (TCP/IP) in Windows XP (Q299357)

When viewing the list of components for a network interface, you may notice that the Uninstall button is disabled when Internet Protocol (TCP/IP) is selected. In Windows XP, the TCP/IP stack is considered a core component of the operating system; therefore, it is not possible to uninstall TCP/IP in Windows XP.
In extreme cases, reinstalling the Internet Protocol stack may be the most appropriate solution. With the NetShell utility, you can now reset the TCP/IP stack back to a pristine state, to the same state as when the operating system was installed.
The NetShell utility ( netsh ) is a command-line scripting interface for the configuring and monitoring of Windows XP networking. This tool provides an interactive network shell interface to the user.
In Windows XP, a reset command is available in the IP context of the NetShell utility. When this command is executed, it rewrites pertinent registry keys that are used by the Internet Protocol (TCP/IP) stack to achieve the same result as the removal and the reinstallation of the protocol.
How to Use Internet Connection Sharing (ICS)

To use ICS to share your Internet connection, the host computer must have one network adapter configured to connect to the internal network, and one network adapter or modem configured to connect to the Internet.
The connection to the Internet is shared to other computers on the local area network (LAN). The network adapter that is connected to the LAN is configured with a static IP address of 192.168.0.1 and a subnet mask of 255.255.255.0.
When you now start Internet Explorer, the client computer will attempt to connect to the Internet using the host computer's shared Internet connection.
Click here for the kb article.

Troubleshooting Internet Connection Sharing in Windows XP (Q308006)

When you use ICS, you can share one Internet connection between two or more computers. Before you install or use ICS, you should contact your Internet service provider (ISP) or read your ISP's Terms and Conditions of use policy to determine if you are permitted to share your connection.
Using the Network Setup Wizard to configure ICS has several advantages: It automatically attempts to detect the connection to the Internet, it can configure Internet Connection Firewall (ICF), and it can bridge multiple network adapters that are connected to your home network. In addition, it also logs information that is related to the configuration that was performed by the wizard in the %SystemRoot%\Nsw.log file.
To install ICS, you can use either the Network Setup Wizard, or configure the shared connection manually.
Click here for the kb article.

How to Configure a Static Client for Windows XP Internet Connection Sharing (Q309642)

This article describes how to configure a static client for Internet Connection Sharing (ICS). Windows XP ICS automatically configures internal clients so that they can access the Internet by using ICS. However, you may need to configure a host, such as a server, statically rather than allowing the host to be configured dynamically. To properly configure the host with static settings, you must provide the host with IP address and host name resolution information. Also, you must configure the ICS host (the Windows XP-based computer that is running ICS) with the name of the client so that name resolution can function properly.
Click here for the kb article.

19-Dec-2006, 10:20 PM	#1 (permalink)
Anilrgowda Administrator Posts: 18,715 Join Date: Jan 2006 Rep Power: 10 IM:	Windows XP Networking Windows XP Networking I have been recieving a lot of questions in email about networking problems, I decided to make this page to help everyone find articles relevant to the problems they are having, from simple home networking problems, the differences in networking in XP and other verions of windows, setting up internet connection sharing, troubleshooting ICS, setting up your personal firewall and any number of other problems. Hope this helps. Cannot Map a Network Drive Under Different User Credentials If you use the Map Network Drive Wizard to connect to a network share by using different user credentials and you use the browse functionality to locate the network share, you may receive the following error message: The network folder specified is currently mapped using a different user name and password. To connect using a different user name and password, first disconnect any existing mappings to this network share. You receive this error message even though you are not aware of making a different connection. troubleshooting Home Networking in Windows XP (Q308007) This article describes how to troubleshoot Windows XP Home Networking. When you encounter such issues, the best first step is to use the Home and Small Office Networking Troubleshooter in Help and Support Center in Windows XP. To use the Home and Small Office Networking Troubleshooter in Help and Support Center: Click Start , and then click Help and Support . Under Pick a Help Topic , click Networking and the Web . Under Networking and the Web , click Fixing networking or Web problems , and then click Home and Small Office Networking Troubleshooter . Answering the questions in the troubleshooter can guide you to a solution. If the troubleshooter does not address the particular that issue you are encountering, continue with the troubleshooting recommendations in this article. Windows XP setting crashes dorm networks Dartmouth students experiencing network difficulties over the past few weeks may themselves be causing the problem. According to Computing Services, laptop computers running Windows XP that are connected to the Internet through both the wireless and cable networks are crashing residence cluster connections when a "network bridging" feature is enabled. Bill Brawley, director of user communications at Computing Services, said that the problem begins when a laptop with Windows XP switches between the wireless Internet card and an Ethernet cable connection. "There are two sort of network interfaces then," Brawley said. "The bridge feature is handy on a home network, but on our network it bridges those two devices and sets up a loop in which packets travel between the networks, sort of a feedback loop. This messes up both networks for the whole building." Windows XP Networking Features and Enhancements With Windows XP, one of Microsoft's primary focuses was to improve the user and administrator experience when networking personal computers. Many of the networking features added or enhanced in Windows XP serve that end. As more and more home computer users are adding second and third PCs, or bringing laptops home from work, the need to connect these computers together and share resources has increased. Many of the features discussed in this paper, including the Networking Setup Wizard, Network Bridging support, and Network Diagnostics, make home networking easier and more convenient. Connecting these newly networked home computers to the Internet safely is often the next step following creation of the home network. Some of the networking features added to Windows XP makes the PC the best gateway to the Internet for the home network. These features include Internet Connection Sharing, Point-to-Point Protocol over Ethernet support (PPPOE), and Internet Connection Firewall. Wireless LAN Technologies and Windows XP The availability of wireless networking and wireless LANs can extend the freedom of a network user, solve various problems associated with hard-wired networks and even reduce network deployment costs in some cases. But, along with this freedom, wireless LANs bring a new set of challenges. There are several wireless LAN solutions available today, with varying levels of standardization and interoperability. Wide industry support for interoperability and operating system support address some of the deployment questions for wireless LANs. Still, wireless LANs present us with new challenges around security, roaming and configuration. The rest of this article discusses these challenges and presents some possible solutions, focusing on how Windows XP will play an important role in providing those solutions with support for zero configuration, 802.1x security and other innovations. Windows XP and Broadband Internet Connections Windows XP has built–in support for the Point–to–Point Protocol over Ethernet (PPPoE). This allows a computer running Windows XP to connect to any Internet service provider whose access equipment supports PPPoE for broadband Internet connections, which includes both cable modem and Digital Subscriber Line (DSL) technologies. Configuring Windows XP for a PPPoE connection is as simple as creating a new connection using the New Connection Wizard. Internet service providers that support industry–standard PPPoE server functionality will work with the PPPoE client supplied in Windows XP. Internet service providers (ISPs) that use broadband Internet access technologies deployed in a bridged Ethernet topology, such as cable modem or Digital Subscriber Line (DSL), need a way to distinguish individual users so that Internet usage can be accounted for, and, if appropriate, billed to individual users. Because Ethernet is inherently a shared access technology, it provides no such facilities. By combining the Point–to–Point Protocol (PPP) with Ethernet, an ISP can use Ethernet topologies and still maintain the individuality of user access as if they were using a dial–up modem. The type of access and choice of service are managed on a per–user basis, rather than a per–site or per–access device basis. The combination of PPP and Ethernet is known as Point–to–Point Protocol over Ethernet (PPPoE) and is defined in the Internet Engineering Task Force RFC 2516. Using Group Policy Settings with Windows XP Home Networking Features Fortunately, Windows XP supports the use of different user accounts and location-aware Group Policy settings. By using a different user account when logging on to the computer when it is connected to the home network (such as a local user account), the organization intranet policies that restrict or prohibit the ability for you to change configuration settings within the Network Connections folder do not apply. Group Policy settings to allow the use of ICS, ICF, and Network Bridge are tied to the network to which the computer was connected when the Group Policy settings were applied. Network administrators can define Group Policy settings that restrict or disable networking features that can cause problems with network connectivity and apply to the computer when it is connected to the organization intranet. When the user takes the computer home and connects it to their home network, the organization intranet Group Policy settings are not applied, allowing the computer to perform Internet connection and bridging functions not allowed on the organization intranet. Overview of Network Address Translation (NAT) in Windows XP As more homes and small businesses add computers they are finding networking is an extremely powerful tool for sharing computer resources. An Internet connection is one of the more precious resources on the network and is likely to be shared. To do this and to enjoy an inexpensive, easy to manage, home or small office network, Internet gateways are being deployed. Internet gateways often provide NAT (Network Address Translation) as a means of connecting multiple hosts to the Internet sharing a single public IP address. Unfortunately, this solution breaks many types of networked applications—as will be described in this paper. NAT Traversal technology has been created to enable network applications to detect the presence of a local NAT device. Once detected, the application can then configure the NAT, defining the appropriate mappings to solve their compatibility issues. Windows XP Bridging and Media Support for Home Networking Windows XP supports a wide variety of networking technologies to connect computers in a home network. In a home with multiple computers that have different types of network adapters, such as a few computers on an Ethernet hub and a few computers that use wireless, attempting to connect them together can be a challenge. Each set of computers that cannot be directly attached together because they exist on separate hubs or cabling systems or are separate technologies define a LAN segment. Wireless 802.11 Security with Windows XP IEEE 802.11, 802.11a and 802.11b (also known as Wi-Fi) are wireless local area networking (LAN) standards that supply 1 megabit per second or above of bandwidth. Because these networks differ from wired LANs several issues unique to wireless LAN deployment must be addressed. The major deployment issue for IEEE 802.11 wireless LANs is managing access to the network and privacy of the wireless traffic. The IEEE 802.11 standard defines the use of WEP pre-shared keys for access control and privacy. However, managing pre-shared keys across thousands of workstations is infeasible.The Internet Connection Firewall Can Prevent Browsing and File Sharing (Q298804) When you enable the Internet Connection Firewall (ICF) feature, and then attempt to browse the Internet by means of My Network Places , you are unsucessful. Also, if you use the net view \\ computername command, you can receive the following error message: System error 6118 has occurred. The list of servers for this workgroup is not currently available. This behavior can occur because the ICF closes, by default, the ports for file sharing. The Master Browser attempts to reconnect to the client computer to send the Browse list, but the firewall prevents this reconnection attempt. How to Troubleshoot TCP/IP Connectivity with Windows XP (Q314067) There are utilities that can provide useful information when you are trying to determine the cause of TCP/IP networking problems under Windows XP. This article lists recommendations for using these utilities to diagnose network problems. Although this list is not complete, the list does provide examples that show how you can use these utilities to track down problems on the network. When you troubleshoot a TCP/IP networking issue, begin by checking the TCP/IP configuration on the computer that is experiencing the problem. Use the ipconfig command to get the host computer configuration information, including the IP address, the subnet mask, and the default gateway. How to Reset Internet Protocol (TCP/IP) in Windows XP (Q299357) When viewing the list of components for a network interface, you may notice that the Uninstall button is disabled when Internet Protocol (TCP/IP) is selected. In Windows XP, the TCP/IP stack is considered a core component of the operating system; therefore, it is not possible to uninstall TCP/IP in Windows XP. In extreme cases, reinstalling the Internet Protocol stack may be the most appropriate solution. With the NetShell utility, you can now reset the TCP/IP stack back to a pristine state, to the same state as when the operating system was installed. The NetShell utility ( netsh ) is a command-line scripting interface for the configuring and monitoring of Windows XP networking. This tool provides an interactive network shell interface to the user. In Windows XP, a reset command is available in the IP context of the NetShell utility. When this command is executed, it rewrites pertinent registry keys that are used by the Internet Protocol (TCP/IP) stack to achieve the same result as the removal and the reinstallation of the protocol. How to Use Internet Connection Sharing (ICS) To use ICS to share your Internet connection, the host computer must have one network adapter configured to connect to the internal network, and one network adapter or modem configured to connect to the Internet. The connection to the Internet is shared to other computers on the local area network (LAN). The network adapter that is connected to the LAN is configured with a static IP address of 192.168.0.1 and a subnet mask of 255.255.255.0. When you now start Internet Explorer, the client computer will attempt to connect to the Internet using the host computer's shared Internet connection. Click here for the kb article. Troubleshooting Internet Connection Sharing in Windows XP (Q308006) When you use ICS, you can share one Internet connection between two or more computers. Before you install or use ICS, you should contact your Internet service provider (ISP) or read your ISP's Terms and Conditions of use policy to determine if you are permitted to share your connection. Using the Network Setup Wizard to configure ICS has several advantages: It automatically attempts to detect the connection to the Internet, it can configure Internet Connection Firewall (ICF), and it can bridge multiple network adapters that are connected to your home network. In addition, it also logs information that is related to the configuration that was performed by the wizard in the %SystemRoot%\Nsw.log file. To install ICS, you can use either the Network Setup Wizard, or configure the shared connection manually. Click here for the kb article. How to Configure a Static Client for Windows XP Internet Connection Sharing (Q309642) This article describes how to configure a static client for Internet Connection Sharing (ICS). Windows XP ICS automatically configures internal clients so that they can access the Internet by using ICS. However, you may need to configure a host, such as a server, statically rather than allowing the host to be configured dynamically. To properly configure the host with static settings, you must provide the host with IP address and host name resolution information. Also, you must configure the ICS host (the Windows XP-based computer that is running ICS) with the name of the client so that name resolution can function properly. Click here for the kb article.