INFORMATION SHEET 2.1.

1
Different Types of Computer System Errors
Learning Objective:
After reading this INFORMATION SHEET, YOU MUST be able to identify Different Types of
Computer System Errors.

Has your computer ever stopped working for no apparent reason? The frustration brought
on by technological advancements can cause any sane person to yank the plug right out of
the wall. Luckily, there's a better way. Learn what to do when your computer freezes, facts
about different kinds of computer failure, the various ways to restart Macs and PCs, and
how to prevent future freezes.
Types of computer failures
The three main types of computer failures are system errors, freezing, and applications
quitting. Simply put, Mac system errors warn you with the dreaded bomb Alert box. A
system error occurs when there is a conflict between the operating system and one or more
applications, like Microsoft Word or Internet Explorer. The next type of computer failure is
freezing, also known as crashing or hanging. In this case, the computer locks up and the
mouse and keyboard become useless accessories. Freezing exists both at the individual
program level and on a system wide basis. An application suddenly quitting is the third
type of computer failure and probably the most common. This means that only one
program is effected rather than the whole system. All three types of computer failures are
frustrating if you do not know what to do, but by following these steps you will learn how to
properly unfreeze your computer.
How to prevent future freezes
nowing how to restart a computer is crucial, but it is also important to know measures to
take to prevent future freezes. The most useful steps are rebuilding your desktop, emptying
your trash, deleting excess e-mails, and cleaning out temporary files and histories.
System error 5 - Access is denied
This is a permission issue. If the net view command fails with a "System error 5 has
occurred. Access is denied." message,
1) make sure you are logged on using an account that has permission to view the shares on
the remote computer.
2) Need to cache credential: logon the same username and password on both computers or
use net net use \\computername /user:username command.

3) Make sure the Netlogon service is running.

System error 8 - Not enough storage
or System error 234 - More data is available.

is

available

to

process

this

command

Symptoms: If you attempt to start the server service manually, the following errors may be
displayed: System error 234 has occurred. More data is available. Or system error 8 has
occurred. Not enough storage is available to process this command. The event viewer shows
"Event ID: 7023.
Description: The Server service terminated with the following error: More data is available.
Or Event ID: 7001. Description: The Net Logon service depends on the Server service which
failed to start because of the following error: More data is available.
Resolutions: 1) apply (or reapply) the latest Windows NT Service pack.
2) remove any unnecessary entries from this value in the registry,

System error 51 has occurred - The remote computer is not available

Symptoms: You may receive "System error 51 has occurred. The remote computer is not
available" when using net use to map the computer drive.
Resolutions: 1. Make sure server service is running on the remote computer

System error 52 - You were not connected because a duplicate name exists on the
network.
Symptoms: you can ping a host but not net view it. When using net view \\hostname, you
get system error 52 - a duplicate name exists on the network.
Resolutions: there are two host names or alias name (cname) are pointed to the same IP. 1)
check the WINS records. 2) check DNS records. 3) Go to System in the Control Panel to
change the computer name and try again.

System error 53 - The network path was not found.

Symptom: when using net view \\ip or \\computername, you get system error 53.
Resolutions: 1) if it is domain environment, check your WINS; 2) if it is peer-to-peer
workgroup, enable NetBIOS over TCP/IP; 3) make sure the machine is running; 4) make
sure file and Printer Share enabled on remote computer; 5) make sure client for ms

networks is enabled on local computer; 6) make sure you type the correct name. 7) Make
sure no firewall running or any security setting.
VPN Case Study - Can ping VPN server but receive System error 53 using net use
Case Study - System Error 53 - The network path was not found.

System error 67 - The network name cannot be found

Symptom: When using net view \\computer or net use \\IP, you may receive above error
message.
Resolution: 1. Make sure you type the correct computer name or shared name.
2. Make sure the Workstation service is running on the local computer while Server service
is running on the remote computer.
More troubleshooting here System error 67 has occurred

System error 85 has occurred. The local device name is already in use
Cause: net use /persistent: yes is default settings for NT and win2000/XP. If you have
mapped some network drives and check the reconnect at logon, or your network uses logon
script to map network drives, the mapped network drives may show red Xs. If you enable
echo and pause the logon script or if using net use to map the same drive manually, you
may get "System error 85 has occurred. The local device name is already in use." One thing
you may want to try is using net use /persistent: no, for example, net use i:
\\servername\folder /persistent: no.
System error 1219 has occurred - The credentials supplied conflict with an existing set of
credentials
Symptoms: 1) When you log on to a domain from w2k client; 2) when attempting to join a
domain, you may receive the following error message: The credentials supplied conflict with
an existing set of credentials.
Resolutions: This may cause because of attempting to make two or more connections to
the same server using two or more sets of credentials
1. Go to windows explorer and disconnect all network drives. Then re-logon.
2. Delete the profile or copy another profile. Note: you may lost all settings and data in My
Documents when deleting or copying profile.
3. If solution 1 and 2 doesn't work, try this: 1) Log on as an administrator at any
workstation and run regedt32. 2) Select HKEY_USERS, but do not open. 3) From the

Registry menu, click Load Hive. 4) This will bring up a Load Hive dialog box. Locate the
Ntuser.dat file for the user with the errors. Select the Ntuser.dat and click Open. You may
enter any string for the Key Name. Use TEST for ease of use pertaining to the remainder of
this article. 5) Locate the Username value under the following key in the registry:
HKEY_USERS\TEST\Network\Username. 6) Delete the string for Username (leaving it
blank is sufficient). 7) Select the TEST hive that you previously loaded, click the Registry
menu, and then click Unload Hive. 8) Quit Registry Editor.
4. If you get this message when joining the domain, make sure 1) you have delete the
computer from AD; 2) delete it from DNS; 3) delete it from WINS.

System error 1231 has occurred. The network location cannot be reached.
Symptom: When using net view \\computername, you may receive System error 1231.
Resolutions: 1) make sure Client for MS Networks is enabled, 2) make sure you have
permission to access it.

System Error 1240 - The account is not authorized to login from this station.
Symptoms: 1. You may get the system error 1240 when using net view \\remotecomputer'
2. Workgroup_name is not accessible Account is Not Authorized to Log In to this Station
when attempting to browse the workgroup from a networking computer.
Resolutions: 1. Use Regedit to enable unencrypted (plain text) passwords for the SMB
client. 2. Enable Send Unencrypted Password to Connect to 3rd Party SMB Servers under
Local Security Policy. 3. Set the following policies as showing: Digitally sign client
communications
(always)
disabled
Digitally
sign
server
communications
(always)disabled
Digitally
sign
server
communications
(when
possible)
disabled
LAN Manager Authentication Level set to Send LM and NTLM - use NTLMv2 session
security
if
negotiated
(default)
send
LM
&
NTLM
responses
Secure channel: Digitally encrypt or sign secure channel data (always) - disabled
Secure channel: Require strong (Windows 2000 or later) session key - disabled
4. Contact the third-party SMB server manufacturer if you have a third-party SMB server,
such
as
DEC
Pathworks,
Samba
or
Linux.
5. If you are running Windows 9x, you may want to re-configure windows authentication for
network logons.

System error 1311 - There are currently no logon servers available to service the logon
request
Symptoms: The primary purpose of logging on with cached credentials is to enable you to
access the local workstation. However, if you have logged on by cached credentials, you may
be unable to access network resources because you have not been authenticated. For
example 1) after you log on to a w2k/xp laptop by using cached credentials, you may be
unable to access the network resources. This issue is commonly experienced by laptop
users whose computer resides in a Windows Server domain and who log on to the computer
by using cached credentials prior to being able to establish a remote access connection. 2)
You log on to a w2k/xp laptop with a domain logon option in a workgroup network. After
you establish the connection and you try to map the network drives, the operation may be
unsuccessful, and you may receive the following error message: "System Error: (1311) There
are currently no logon servers available to service the logon request."
Resolutions: To authenticate the cached credentials, 1) if it is w2k/xp, use net command,
for example, net use \\servername\sharename /user:username. 2) if xp, open Windows
Explorer>Tools>Map Network Drive.
Click Connect using a different user name, enter the username and password.

System error 1326 has occurred - Logon failure: unknown user name or bad password.
Symptom: when using net use to map a network drive, you may receive "System error 1326
has occurred. Logon failure: unknown user name or bad password." message.
Resolutions: 1) create a user account on remote computer; 2) need to enable the guest
account; 3) make sure the remote computer doesn't use auto-logon and blank password; 4)
make sure you have a folder or drive shared on the remote computer. 5) use net use
\\servername /user: username command. Make sure you type correct command (e.g. use
net use \\servername \user: username will get this error too)

System error 1331 has occurred - Logon failure: account current disable
Symptom: When using net use \\computername command, you may receive above error
message.
Resolutions: this is cache credentials issue. To fix this problem and cache the credentials,
use net use \\computername /user: username command.

System error 1385 has occurred - Logon failure: the user has not been granted the
requested logon type at this computer
Symptoms: When using net use

\\remotecomouter\ahredname, you may receive above message.

Resolution: 1. The users do not have permission to connect to the remote computer. To
resolve this problem: on the remote computer, select Administrative Tools>Local Security
Settings>Local Policies>User Rights Assignment, right-click on Access this computer from
the network>Properties>Add Users or Groups, add everyone or any users you want to be
able to access the computer from the network.
2.
refer
to
this
case:
Solved:
System error
http://chicagotech.net/netforums/viewtopic.php?t=286

1385

Logon

failure

System error 1396 has occurred - Logon Failure: The target account name is incorrect.
Symptoms:
1. when
using
net
use, you
may receive
above
message.
2. when using net view \\hostname, you may receive "System error 5 has occurred. Access
is
denied.".
However,
net
view
\\ip
works
fine.
3. You may receive above error while running logon script.
Causes: 1. SPN for the domain that is hosting the replica has not been propagated.
2.
Incorrect
target
account
name
or
the
server
is
not
online.
3. If you have DFS, make sure the DFSRoot is available.
Refer to RL060704
System error 6118 has occurred. The list of servers for this workgroup is not currently
available
SYMPTOMS: 1) After enabling ICS/ICF, you can't see any computes on My Network places.
If you try, you may get "workgroup is not accessible". 2) If you use the net view command,
you may receive "System error 6118 has occurred. The list of servers for this workgroup is
not currently available." message.
Resolutions:
1) This behavior can occur if you enable the ICF that will closes the ports for file sharing by
default. To open these ports, right-click the network connection that is firewall protected>
Properties>Advanced>Settings>Service Tab>Add, Enter 127.0.0.1) for the required Internet
Protocol (IP) number. Enter UDP ports from 135 through 139, and TCP ports from 135
through 139 one by one (the external and internal port numbers should be identical).
2) This may occur if the workgroup name and the domain name are the different.
3) No master browser. Starting Computer Browser Service on one of w2k/xp computers
should fix the problem

INFORMATION SHEET 2.1-2

Plan and Preparing Diagnostic Procedure
Learning Objective:
After reading this INFORMATION SHEET, YOU MUST be able to Plan and Prepare Diagnostic
Procedure.

PC Diagnosing
Probably the most frustrating problem computer users run into are
problems, where your computer wont boot. Equally annoying are error
messages you constantly run into during your computers startup
process. In this module you will be given a few tips on how you can
avoid some of the most common problems that happen right after your
computer turns on.

startup

Troubleshooting Plan for Personal Computers

How to Troubleshoot the Computer?
Here you will learn the basic troubleshooting methods of your computer.

Trial and error: When you find a faulty component in your computer, check it with
the other computers so that you can make sure whether the fault is in the
component or not.

Check cables: In case of any device failure, check all the cables of your computer
such as data cables, power cable, internal circuitry cables and make sure that all
these are plugged in and working fine.

Hardware settings: Check the hardware settings in the CMOS and in the device
manager of the system and make all the device drivers are up to date and all the
cards are plugged in properly.

Notice changes: When you notice a software or hardware error in your computer,
determine what was changed before the problem occurred

Event viewer: In the event viewer, you will find the error or warning messages
associated with any faulty hardware or software.

Make notes: Troubleshooting is a big learning option and we can learn a lot when we face
any kind of troubleshooting in our computer. Make notes including the error messages and
their solutions, so that you have a record on how a certain problem occurred and how did
you solve it.
Common Trouble for Computer Units
1.
2.
3.
4.
5.

Double check the power connections.

Voltage Regulator and power supply could cause power failure in the computer unit.
Check the power cords and cable connectors in your computer unit.
Unseated card. Loose cards could cause it to malfunction.
Do you have ink or toners in your printer? Check the ink toners/cartridges in your
printers.
6. Check the boot sequence configuration in the advance BIOS (Basic Input/output
Unit) setup.

Diagnosing Network Connection

These are the things to look for if a PC will not connect to the internet or network.

First check the cable connecting to the network card into the network hub.

Check the back of the computer to see if the network card light is on
Check the network cable
Check the network HUB

INFORMATION SHEET 2.1-3

Hand Tools for Testing and Repair Computer System & Network

Learning Objective:
After reading this INFORMATION SHEET, YOU MUST be able to identify and use Hand
Tools for Testing and troubleshooting Computer System & Network
Introduction

Tools and equipment play a vital role in troubleshooting; it helps the user to
determine the errors found in your computer hardware and network.
Tools used to test and repair hardware problems:
1. Screw drivers-is used to install and remove screws in your computer unit.

2. Pliers and tweezers- is used for picking small parts in your

computer unit.

3. Soldering iron- is primarily used for connecting terminals in your

power supply and circuit board with the use of a soldering lead.

4. Anti-static wrist strap, mat and spray- are used to eliminate electrostatic discharge in
your work area.

5. Lens cleaner-is used for cleaning optical media, such as DVD-ROMS and
CD-writers.

6. Thermal paste-is a paste used for heat dissipation for your processor.

Network Troubleshooting Tools

1. LAN Tester is a device used to test the network connection..

2. Crimping tool- is a device used to crimp the RJ45 connector to the UTP cable.

INFORMATION SHEET 2.1-4

Common Windows XP Diagnostic Utilities & Tools
Learning Objective:
After reading this INFORMATION SHEET, YOU MUST be able to identify and use Common
Windows XP Diagnostic Utilities & Tools

1. There are a lot of diagnostic utilities for Windows XP, both included with the system
and third-party applications, that can examine your computer for a range of
problems. Microsoft's own, included utilities have been specially trimmed to apply to

certain devices and uses, making them the best choice for all but the most
devastating of problems.
Disk Utilities
2. Many errors can be caused by hard disk problems. The Disk Cleanup, Disk
Defragmenter and Disk Error Checking utilities can assess and fix many of these
problems. All can be found under the System Tools section of the Accessories submenu. Also, running your hard drive manufacturer's specific disk diagnostic tool can
help to diagnose any read or write errors that cause application problems in Windows
XP.
Application and Memory Utilities
3. Run time errors, blue screens and other memory errors are often caused by badly
written programs or incorrect system calls. The Dr. Watson tool is great for checking
application errors and can be accessed by clicking the "Run" shortcut from the Start
menu, typing in "DRWATSN32" and pressing "Enter." Memtest86+ is another great
tool for checking your computer's standalone memory (see Resources).
Network Diagnostics
4. The Network Diagnostics Tool is included with Windows XP and provides a way to test
your Internet connection settings. You can access it from Internet Explorer by clicking
"Diagnose Connect Problems" from an error page or by selecting the tool under the
"Tools" option menu. You can also right-click any network connection from the
Network Connections menu and choose to troubleshoot the connection there to do
further network diagnostics. Also, try using a website such as Speed Test (see
Resources) to test your broadband connection speed and diagnose any speed issues.

Hardware Diagnostics
5. Under the Device Manager you can see hardware that is working improperly, because
it will have a warning icon next to it. Right-click that device and choose to
troubleshoot. This will bring up the device troubleshooting utility that will often try to
update the driver or fix an existing driver.

Malware and Adware Utilities

6. Adware, malware and viruses can infect your computer, decimate its performance
and siphon your private data from your fingertips. Since most of these malicious
programs are built to target Windows XP, it is important to regularly check for
malware. Tools such as Lavasoft's Ad-Aware or Spybot Search & Destroy are great
utilities for finding and eliminating harmful or infected applications (see Resources).
In combination with traditional anti-virus software such as Norton or McAfee, they
are essential for keeping your computer running smoothly.