Computer is not accesible. You might not have permissions to use...

network places -microsoft windows network -MSHOME -click on Computer A, it says:
"Computer A is 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 permissions"

net view \\pcname results in error "System Error 5. Access is denied."

"XXXXXXX is not accessible. You might not have permission to use
network resource. Access is denied."
http://support.microsoft.com/?kbid=913628



"Workgroup is not accessible. You may not have permission to use this
network resource. Contact the administrator of this server to see if
you have access permissions."


"Workgroup_name is not accessible. You may not have permission to use this network resource."
http://support.microsoft.com/kb/915107/en-us (guest acct)

"Workgroup Name is not accessible. You may not have permission to use this network resource."
(turn on netbios over tcp, start computer browser service)
http://support.microsoft.com/kb/318030/en-us

click Entire Network, Microsoft Network, click the workgroup name, you receive:
"Unable to access Computers Near Me. Workgroup is not accessible.
The list of servers for this workgroup is not currently available."
(pc is set as a master browser, or netbios over tcp not enabled)
http://support.microsoft.com/kb/285035/en-us

Missing Or Corrupt Hal.dll Error Resolution

Error Message

There are few different ways that the "missing or corrupt hal.dll" error may present itself, with the first listing being the most common:

• "Windows could not start because the following file is missing or corrupt:
  \system32\hal.dll.
  Please re-install a copy of the above file."
  
  
• "\System32\Hal.dll missing or corrupt:
  Please re-install a copy of the above file."
  
  
• "Cannot find \Windows\System32\hal.dll"
  
  
• "Cannot find hal.dll"

The "missing or corrupt hal.dll" error displays shortly after the computer is first started. Windows XP has not yet fully loaded when this error message appears.

Cause

Causes of the "missing or corrupt hal.dll" error include, naturally, a damaged hal.dll file or a hal.dll file that has been deleted or moved from its intended location.

Additional causes may include a damaged or missing boot.ini file or possibly a physically damaged disco duro.

Resolution

1. Restart the PC. The hal.dll error could be a fluke.
   
   
2. Check for proper boot order in BIOS. You might see the hal.dll error if the boot order in BIOS is first looking at a hard drive other than your main hard drive.
   
   Note: If you've recently changed your boot order or recently flashed your BIOS, this may be what's causing your problem.
   
   
3. Run Windows XP System Restore from a command prompt. If this doesn't work or you're receiving the hal.dll error message before you're able to complete this process, move on to the next step.
   
   
4. Repair or replace the boot.ini file. This will work if the cause of the problem is actually Windows XP's boot.ini file and not the hal.dll file, which is often times the case.
   
   
5. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the hal.dll error.
   
   
6. Restore the hal.dll file from the Windows XP CD. If the hal.dll file is truly the cause of the problem, restoring it from the original Windows XP CD may do the trick.
   
   
7. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
   
   
8. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch.
   
   Note: While this will almost certainly resolve any hal.dll errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.
   
   Important: If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.
   
   
9. Replace the hard drive. Finally, if all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.
   
   Perform a new installation of Windows XP after installing the new hard drive.

Applies To

This issue applies to the Windows XP operating system, including Windows XP Professional and Windows XP Home Edition.

NTLDR is missing

Bootrec /fixmbr
Bootrec /fixboot

Msconfig is gone

xp_emergencyutils.exe

Winlogon using 99% resources

Virus.
Run Procexp.exe to identify the process, kill it. Then without restarting the computer run combofix.exe. That it'll do it.

Explorer.exe corrupted or infected by virus

When loading windows, after welcome screen, nothing shows up.
First of all, it is recommended to perform full scan on infected HDD, you can do it connecting the Hd to another computer then do the scanning.

1. Use a virtual disk to access the infected partition, search for any file called explorer.exe and remove all of them.
2. Restart the computer in normal mode, open task manager, go to c:\windows folder, find explorer.exe and rename it. (example: lapiz.exe)
3. Open registry, goto HKLM\software\microsoft\windowsnt\winlogon. Highlight winlogon and identify on the right pane: shell, right click modify, enter lapiz.exe (as in the example)
4. Close registry, then restart the computer.
That should do it

Can't Install .NET Framework 2.0

1. Download the .NET Framework cleanup tool and choose to cleanup the version of the .NET Framework that is causing problems on your system
2. Download and install the version of the .NET Framework that you cleaned up in step 1 (such as the .NET Framework 1.0, .NET Framework 1.1 or .NET Framework 2.0)
3. (optional) Download and run the .NET Framework verification tool to double-check that all .NET Framework files are correctly installed
4. Download and install the desired .NET Framework service pack (such as .NET Framework 1.0 SP3 or .NET Framework 1.1 SP1) by running the setup package directly instead of using Windows Update. Running it directly will allow the service pack setup to display error dialogs instead of having Windows Update suppress them