Windows System error codes

System error  5 - Access is denied

This is a permission issue. If the net view command fails with a 5 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.

8 Not enough storage is available to process this command
or 234 More data is available.

Symptoms: you can ping a host but not net view it. When using net view \\hostname, you get 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 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. 8) If your computer is loaded NetWare IPX or NWLink, you may receive 53. You may want to disable the NWlink or move it lower than TCP/IP in in network binding order.

VPN Case Study Can ping VPN server but receive 53 using net use

Case Study - 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 67

85 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 85 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.

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.

1231 The network location cannot be reached.

Symptom:  When using net view \\computername, you may receive 1231.

Resolutions: 1) make sure Client for MS Networks is enabled, 2)  make sure you have permission to access it.

Symptoms: 1. You may get the 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.

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: : (1311) There are currently no logon servers available to service the logon request.

1326 Logon failure: unknown user name or bad password.

Symptom: when using net use to map a network drive, you may receive 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)

1331 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.

1385 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: 1385 Logon failure http://chicagotech.net/netforums/viewtopic.php?t=286