Tips for Troubleshooting Windows File and Printer Sharing 

This checklist describes typical issues encountered when setting up peer-to-peer file sharing on a Microsoft Windows network. Follow the steps below to troubleshoot and resolve these Windows file sharing problems. Many items in the checklist are especially crucial on networks that run multiple versions or flavors of Windows. Click the links provided to get more detailed troubleshooting tips.

1. Name Each Computer Correctly

On a peer-to-peer Windows network, all computers must possess unique names. Ensure all computer names are unique and each follows the Microsoft naming recommendations. For example, consider avoiding spaces in computer names: Windows 98 and other older versions of Windows will not support file sharing with computers having spaces in their name. The length of computer names, the case (upper and lower) of names and the use of special characters must also be considered.

 

2. Name Each Workgroup (or Domain) Correctly

Each Windows computer belongs either to a workgroup or a domain. Home networks and other small LANs utilize workgroups, whereas larger business networks operate with domains. Whenever feasible, ensure all computers on a workgroup LAN have the same workgroup name. While sharing files between computers belonging to different workgroups is possible, it is also more difficult and error-prone. Similarly, in Windows domain networking, ensure each computer is set to join the correct named domain.

3. Install TCP/IP on Each Computer

TCP/IP is the best network protocol to use when setting up a Windows LAN. In some circumstances, it's possible to use the alternative NetBEUI or IPX/SPX protocols for basic file sharing with Windows. However, these other protocols normally don't offer any additional functionality beyond what TCP/IP provides. Their presence also can create technical difficulties for the network. It is strongly recommended to install TCP/IP on each computer and uninstall NetBEUI and IPX/SPX whenever possible.

4. Set up Correct IP Addressing and Subnetting

On home networks and other LANs having a single router or gateway computer, all computers must operate in the same subnet with unique IP addresses. First, ensure the network mask (sometimes called "subnet mask") is set to the same value on all computers. The network mask "255.255.255.0" is normally correct for home networks. Then, ensure each computer possesses a unique IP address. Both the network mask and other IP address settings are found in the TCP/IP network configuration.

5. Verify File and Printer Sharing for Microsoft Networks is Installed

"File and Printer Sharing for Microsoft Networks" is a Windows network service. This service must be installed on a network adapter to enable that computer to participate in file sharing. Ensure this service is installed by viewing the adapter's properties and verifying that a) this service appears in the list of installed items and b) the checkbox next to this service is checked in the 'on' position.

6. Temporarily or Permanently Disable Firewalls

The Internet Connection Firewall (ICF) feature of Windows XP computers will interfere with peer-to-peer file sharing. For any Windows XP computer on the network that needs to participate in file sharing, ensure the ICF service is not running. Misconfigured third-party firewall products can also interfere with LAN file sharing. Consider temporarily disabling (or lowering the security level of) Norton, ZoneAlarm and other firewalls as part of troubleshooting file sharing problems.

7. Verify Shares are Correctly Defined

To share files on a Windows network, ultimately one or more network shares must be defined. Share names that end with a dollar sign ($) will not appear in the list of shared folders when browsing the network (although these can still be accessed). Ensure shares have been defined on the network appropriately, following the Microsoft recommendations for share naming.

 

Troubleshooting Home Network

You've carefully followed all the instructions in the network router setup guide, but for whatever reason your network isn't working. Perhaps everything functioned before and just started failing suddenly, or maybe you've spent days or weeks trying to get through the initial installation. Use these troubleshooting guidelines to isolate and solve network problems involving your router: Keep in mind there may be more than one issue involved.

Mismatched Wi-Fi Security Settings

Seemingly the most common cause of wireless network setup issues, incompatibility in settings between two Wi-Fi devices (such as the router and a PC) will prevent them from being able to make a network connection. Check the following settings on all Wi-Fi devices to ensure they are compatible:

• Network mode: A router must be enabled to support all versions of Wi-Fi used by the network clients. For example, routers configured to run in "802.11g only" mode will not support 802.11n or old 802.11b devices. To fix this kind of network failure, change the router to run in mixed mode.
  
  
• Security mode: Most Wi-Fi devices support multiple network security protocols (typically different variations of WPA and WEP). All Wi-Fi devices including routers belonging to the same local network must use the same security mode.
  
  
• Security key: Wi-Fi security keys are passphrases or sequences of letters and digits. All devices joining a network must be programmed to use a Wi-Fi key recognized by the router (or wireless access point). Many home network routers (access points) support only one key that all devices must share in common. Some newer routers can store multiple Wi-Fi security keys instead of one, however, technically allowing local devices to have different key settings (although keeping their keys all the same can simply setup and troubleshooting).

MAC Address Restrictions

Many network routers support a feature called MAC address filtering. Although disabled by default, router administrators can turn this feature on and restrict connections to only certain devices according to their MAC address number. If having difficulty getting a specific device to join the local network (particularly if it is new), check the router to ensure either (a) MAC address filtering is 'off' or (b) the device's MAC address is included in the list of allowed connections.

Loose or Disconnected Cables

Sometimes the router is turned off, or someone in the family accidentally unplugs power to it. Ensure power strips are switched on and receiving electricity from the outlet, and if applicable, that any Ethernet cables are firmly seated - the connectors should make a clicking sound when snapping into position. If the router can't connect to the Internet but is otherwise operating normally, ensure any modem cables are connected properly.

Overheating or Overloading

Downloading large files or streaming data for long periods causes a home network router to generate heat. In some cases, routers will overheat due to the sustained heavy load. An overheated router will behave unpredictably, eventually disconnecting devices from the local network and crashing. Shutting down the router and allowing it to cool down solves the problem temporarily, but if this issue occurs often, ensure the router has proper ventilation (no vents blocked) and consider moving it to a cooler location. Home routers can typically handle ten (10) or more connected clients, although if too many devices actively use the network at once, similar overloading problems can result. Even when not physically overheating, the high network activity can cause outages. Consider adding a second router to the network in these cases to better handle the load.

Wireless Signal Limitations

Because the range of Wi-Fi radio signals is limited, home network connections sometimes fail because a device's radio cannot reach the router's. Some people also have had their functioning wireless network go offline as soon as anyone in the house turned on the microwave oven. Garage door openers and other consumer gadgets inside homes also can interfere with the signals of Wi-Fi networks, particularly those that use the 2.4 GHz radio bands.
It's also common in cities for the signals of several home Wi-Fi networks to intermingle with each other. Even inside their own home, a person may discover one or more of their neighbor's wireless networks when trying to connect to their own.
To work around these wireless radio interference and range limitations, change the Wi-Fi channel number on the router, or re-position the router. Finally, consider changing your router's name (SSID) if a neighbor is using the same one.

Defective or Outdated Hardware or Firmware

It's not uncommon for routers to fail after years of regular use. Lightning strikes or other electrical power surges can also damage the circuitry of network equipment. Because they have few moving parts, trying to repair network routers rarely is practical. Set aside some budget for periodically replacing your router (and any other essential network equipment). Also consider keeping some spare cables and a cheap backup router to help with emergency troubleshooting. Before finally giving up a router, try updating the router's firmware first. Sometimes no firmware update will be available, but in other cases newer firmware may contain fixes for overloading or signaling issues.

Basic network troubleshooting

If a computer is unable to connect to a network or see other computers on a network, it may be necessary to troubleshoot the network. A network may not work because of any of the below reasons.

1. Network card not connected properly.
2. Bad network card drivers or software settings.
3. Firewall preventing computers from seeing each other.
4. Connection related issues.
5. Bad network hardware.

Solution

Because of the large variety of network configurations, operating systems, setup, etc... not all of the below information may apply to your network or operating system. If your computer is connected to a company or large network, or you are not the administrator of the network, it is recommended that if you are unable to resolve your issues after following the below recommendations that you contact the network administrator or company representative.
Note: If you are being prompted for a Network password and do not know the password, Computer Hope is unable to assist users with obtaining a new or finding out the old password.

Verify connections and LEDs

Verify that the network cable is properly connected to the back of the computer. In addition, when checking the connection of the network cable, ensure that the LEDs on the network are properly illuminated. For example, a network card with a solid green LED or light usually indicates that the card is either connected or receiving a signal. Note: generally, when the green light is flashing, this is an indication of data being sent or received.

If, however, the card does not have any lights or has orange or red lights, it is possible that either the card is bad, the card is not connected properly, or that the card is not receiving a signal from the network.

If you are on a small or local network and have the capability of checking a hub or switch, verify that the cables are properly connected and that the hub or switch has power.

Adapter resources

Ensure that if this is a new network card being installed into the computer that the card's resources are properly set and not conflicting with any hardware in the computer.

Users who are using Windows 95, 98, ME, 2000 or XP, verify that Device Manager has no conflicts or errors. Additional help and information about Device Manager and resources can be found on our Device Manager page.

Adapter functionality

Verify that the network card is capable of pinging or seeing itself by using the ping command. Windows and MS-DOS users ping the computer from a MS-DOS prompt. Unix and Linux variant users ping the computer from the shell.

To ping the card or the localhost, type either

ping 127.0.0.1

or

ping localhost

This should show a listing of replies from the network card. If you receive an error or if the transmission failed, it is likely that either the network card is not physically installed into the computer correctly, or that the card is bad.

Protocol

Verify that the correct protocols are installed on the computer. Most networks today will utilize TCP/IP, but may also utilize or require IPX/SPX and NetBEUI.

• Additional information and help with installing and reinstalling a network protocol.

When the TCP/IP protocol is installed, unless a DNS server or other computer assigns the IPX address, the user must specify an IP address as well as a Subnet Mask. To do this, follow the below instructions.

1. Click Start, Settings, Control Panel
2. Double-click the Network icon
3. Within the configuration tab double-click the TCP/IP protocol icon. Note: Do not click on the PPP or Dial-Up adapter, click on the network card adapter.
4. In the TCP/IP properties click the IP address tab
5. Select the option to specify an IP address
6. Enter the IP address and Subnet Mask address, an example of such an address could be:
   
   IP Address: 102.55.92.1
   Subnet Mask: 255.255.255.192
   
   
7. When specifying these values, the computers on the network must all have the same Subnet Mask and have a different IP Address. For example, when using the above values on one computer you would want to use an IP address of 102.55.92.2 on another computer and then specify the same Subnet Mask.

Firewall

If your computer network utilizes a firewall, ensure that all ports required are open. If possible, close the firewall software program or disconnect the computer from the firewall to ensure it is not causing the problem.

Additional time

In some cases it may take a computer some additional time to detect or see the network. If after booting the computer you are unable to see the network, give the computer 2-3 minutes to detect the network. Windows users may also want to try pressing the F5 (refresh) key when in Network Neighborhood to refresh the network connections and possibly detect the network.

Additional troubleshooting

If after following or verifying the above recommendations you are still unable to connect or see the network, attempt one or more of the below recommendations.

If you have installed or are using TCP/IP as your protocol you can ping another computer's IP address to verify if the computer is able to send and receive data. To do this, Windows or MS-DOS users must be at a prompt and Linux and Unix variant users must open or be at a shell.

Once at the prompt assuming, that the address of the computer you wish to ping is 102.55.92.2, you would type:

ping 102.55.92.2

If you receive a response back from this address (and it is a different computer), this demonstrates that the computer is communicating over the network. If you are still unable to connect or see the network, it is possible that other issues may be present.

Another method of determining network issues is to use the tracert command if you are a MS-DOS or Windows user or the traceroute command if you are a Linux or Unix variant user. To use this command you must be at the command line.

Once at the command line, assuming that the address is again 102.55.92.2, type one of the below commands.

tracert 102.55.92.2

or

traceroute 102.55.92.2

This should begin listing the hops between the computer and network devices. When the connection fails, determine what device is causing the issue by reviewing the traceroute listing.