Peer to Peer Workgroup Network Error Description Solutions

In our previous articles we have configured our workgroup network. We have also listed most common errors with their possible solutions those might have occured during the workgroup configuration.

In this article we would use a step by step approach for troubleshooting workgroup.

For troubleshooting workgroup windows xp network we would use inbuilt tool of xp. To use inbuilt Networking Troubleshooter follow these steps:

• 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 SmallOffice Networking Troubleshooter.
• Answer the questions in the troubleshooter to try to find a solution.

If the troubleshooter resolves the issue, you are finished.
If the troubleshooter does not resolve the issue, than go through the process given below

Home-network structures and their configurations

Before you troubleshoot home networking issues, first determine the network structure you are using. The network structure is the arrangement or mapping of network elements such as links and nodes, and the physical connections between them. There are several common home-network structures:

Computers that are connected to a NAT device

The computers are connected to a NAT device that provides a single, shared Internet connection. A hardware network address translation (NAT) device is a broadband or satellite modem that enables the computers to obtain and share a single connection. In this configuration, computers generally receive an IP address from the NAT device. Typically, the NAT device uses the address 192.168.1.1 and assigns addresses to other computers in the range 192.168.1.x, where x is a number between 2 and 254.

Computers that are connected to a network hub

A network hub receives data through one port, and then makes it available to all ports. This enables data sharing or Internet connection between all computers that are connected to the hub. Computers that are connected to a network hub can have many configurations:

The computers have no Internet connection.

In this configuration, the computers are generally assigned IP addresses in the range of 169.254.x.y, where x and y are numbers between 1 and 254.

The computers are connected to a hub,

Where only one computer has Internet connection shared by using Internet Connection Sharing.

This connection can be a dial-up connection or a broadband connection (typically xDSL or a cable modem).
In this configuration, the computer that shares the connection generally assigns IP addresses to other computers on thehome network. The computer that is sharing the connection will have IP address 192.168.1.1 configured for the adapter that is connected to the home network. Other computers on the network will have addresses in the range 192.168.1.x, where x is a number between 2 and 254.

The computers are connected to the Internet through a broadband connection.

This configuration is also known as an edgeless network. In this configuration, the computers on the home network each have an IP address that is provided by the Internet service provider (ISP). The addresses that are used vary, depending on the ISP. The computers each have a separate dial-up connection or broadband connection to the Internet.In this configuration, the computers generally use automatically assigned IP addresses for their home network adapters.
Typically, the network adapters assign IP addresses in the range of 169.254.x.y, where x and y are numbers between 1 and 254. The computers use ISP-provided addresses for their Internet connections.

Troubleshoot basic connectivity issues

To troubleshoot basic connectivity issues and verify name resolution between computers, follow these steps in the order in which they are provided until you isolate and resolve the issue.

Step 1: Verify the physical connection between computers

The back of each network adapter in a desktop computer has visible lights. These lights indicate a good connection. If you are using a network hub, or a switch to connect the computers, make sure that the network hub or the switch is turned on and that the lights are illuminated for each client connection. This indicates a good link.

Step 2: Make sure that all computers have TCP/IP installed

This step is especially important with Microsoft Windows 95-based computers. By default, Windows 95-based computers do not have TCP/IP installed. If you are using computers that run Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition on the network, you can look for TCP/IP by using the Network item in Control Panel. If TCP/IP is not installed, you must install it to communicate with Windows XP-based computers on the network. TCP/IP is always installed in Windows XP.

Step 3: Make sure that the network configuration includes the IP addresses

Collect network configuration information from at least two computers on the network by using the adapter status. Then, make sure that the assigned IP addresses match the home-network configurations described above in the "Home-network structures and their configurations" section. Follow these steps:

• Click Start, click Run, type ncpa.cpl and then click OK.
• Locate and right-click the icon that represents this computer's connection to the home network, and then click Status.
• Click the Support tab, and then under Connection status, locate the IP addresses.

If the assigned IP addresses do not match the topology that this article described in the "Home-network structures and their configurations" section, the computer that is assigning the addresses may not be available. This is likely to be true if 169.254.x.y addresses are in a configuration where you expect a different address range.

To change the configuration so that the addresses on the home network adapter for each computer are in the same range, determine which address is correct based on the network topology. To do this, check whether one computer receives an address in the range 192.168.0.x, and another receives an address in the range 169.254.x.y. When you isolate which computer has the incorrect address, troubleshoot the computer that has the incorrect address.

Note:- For Windows 95-based computers in a network that uses 169.254.x.y addressing, you must configure IP addresses manually. For information about how to do this, see the online Help for Windows 95.

Step 4: Make sure that firewall features are not enabled on the home network adapters

Verify that the Internet Connection Firewall (ICF) or Windows Firewall (WF) feature is not enabled on the adapters that you use to connect the computers to the home network. If these features are enabled on these adapters, you cannot connect to shared resources on other computers in the network.
Note:-Edgeless networks are the exception. You can use ICF with edgeless networks if you take additional measures to enable connectivity in the home network.

Step 5: Test connectivity between computers by using the "ping" command

Use the ping command to test connectivity between two computers on the network,
On one of the computers, click Start, click Run, type command and then click OK.
At the command prompt, type ping x.x.x.x (where x.x.x.x is the IP address of the other computer), and then press ENTER. If the ping command is successful, and the computers can connect correctly
After you have verified connectivity and name resolution between computers, you can troubleshoot the connectivity for file and printer sharing.

Troubleshoot file sharing and printer sharing

After the computers are connected, you can share files and printers between computers through the home network. To troubleshoot file sharing and printer sharing, follow these steps in the order in which they are provided until you isolate and resolve the issue.

Step 1: Run the Network Setup Wizard to configure each computer in the network

To configure file and printer sharing, run the Network Setup Wizard on each computer in the network. When you are finished , go to step 2.

Step 2: Make sure that the Guest account is set up for network access

All network access to either a Windows XP Home Edition-based computer in a workgroup or to a Windows XP Professional-based computer in a workgroup uses the Guest account. Before you continue to troubleshoot, make sure that the Guest account is set up for network access.Follow these steps:

• Click Start, click Run, type command, and then click OK.
• Type the net user guest and then press ENTER.
• If the account is active, a line appears in the output of the command that has the following format:
  Account active Yes
• If the account is not active,
• type net user guest /active:yes and then press ENTER to give the Guest account network access. The following text returns after the command:
  The command completed successfully.

If you receive any other response, make sure that you are logged on as an administrator, and than confirm that you typed the command correctly before you try again. When you are finished setting up the Guest account for network access, go to step 3.

Step 3: Make sure that folder for the computer name is shared

After you have verified the file-sharing configuration and set up the Guest account for network access, make sure that the folder for each computer is shared. Follow these steps:

• To locate the computer name for each computer, click Start, click Run, type sysdm.cpl, and then click OK.
• On the Computer Name tab, under Full computer name, locate the computer name.
• To determine whether a folder is shared, click Start, click Run, type fsmgmt.msc, and then click OK.
• In the left navigation pane, click Shares. A list of shared folders is displayed in the right navigation pane.
• Locate the share folder for each computer.
• If all computer names are listed, go to step 4.

Step 4: Test the connection between computers

To test the connection from one computer to another, follow these steps:

• Click Start, click Run, type \\computername (where computername is the name of another computer on the network), and then press ENTER. A window opens that contains an icon for each shared folder on the other computer.
• Try to open one of the shared folders to confirm that the connection is working.
• If you can open a shared folder, the computers are connected. Go to step 5.
• If you cannot open a shared folder, go to step 2.
• Test the connection from the opposite direction. To do this, go to the other computer on the network and repeat steps 1 and 2 to try to open a shared folder between the computers, or between other computers to make sure that the problem is not with a particular computer on the network.
• If you can open a shared folder from each computer, the computers are connected. Go to step 5.
• If you can open a shared folder from one computer but not the other, the problem may be that the other computer cannot access the folder. Go to step 3 to troubleshoot the connection for the other computer.
• If you cannot open a shared folder from either computer, there may be a problem with the connection. Go to the "Troubleshoot basic connectivity" section and see step 5.
• If you still cannot open a shared folder, try again to test the connection with the computer name as the name of the local computer. This tests the connection locally. A window is displayed with an icon for each shared folder on the computer. Try to open one of the shared folders to make sure that you have access.
• If you can open a shared folder, the computers are connected. Go to step 5.

Step 5: Check the Network Setup Wizard log file for errors

Check the Network Setup Wizard log file for errors in any events that are not followed by successful operations. To open the log and check for errors, follow these steps:
Click Start, click Run, type %SystemRoot%\nsw.log and then press ENTER.
If you find errors in the log, search the computernetworkingnotes.com for more information about how to manually configure the computer to have the correct settings. When you are finished checking the Network Setup Wizard log file for errors, you should have connectivity for file and printer sharing.