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

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.

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

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.

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

How to enable NTLM 2 for Windows 9x

To enable a Windows 9x client for NTLM 2 authentication, activate NTLM 2 on the client, follow these steps:

1.	Start Registry Editor by using Regedit.exe.
2.	Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
3.	Create an LSA registry key in the registry key listed above.
4.	On the Edit menu, click Add Value, and then add the following registry value: Value Name: LMCompatibility Data Type: REG_DWORD Value: 3 Valid Range: 0,3 Description: This parameter specifies the mode of authentication and session security to be used for network logons. It does not affect interactive logons. • Level 0 - Send LM and NTLM response; never use NTLM 2 session security. Clients will use LM and NTLM authentication, and never use NTLM 2 session security; domain controllers accept LM, NTLM, and NTLM 2 authentication. • Level 3 - Send NTLM 2 response only. Clients will use NTLM 2 authentication and use NTLM 2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLM 2 authentication.
5.	Quit Registry Editor.

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

No network provider accepted the given network path

System error 67 has occurred

The network name cannot be found

Symptoms

1. You can access the shared folders on a remote computer by using IP but not host name. If you use the host name, you may receive this message: “No network provider accepted the given network path”.

2. You can access the shared folders on a remote computer by using FQDN but not NetBIOS name. If you use the NetBIOS name, you may receive this message: “No network provider accepted the given network path”.

3. When you use net use to a shared resource of a remote computer, you may receive: “System error 67 has occurred. The network name cannot be found”.

4. You may have problems getting group policy updates with the "no network provider" error.

5. You can't map a folder my documents using this command: net use h: \\chicagotech\my documents. If you do, you will receive above message.

Resolution

1. Make sure you have enabled File and Print Sharing For Microsoft Networks From Properties of Local Area Connection

2. Make sure you have shared some folders or files.

3. Run “sfc /scannow”.

4. Make sure you type the correct computer name or shared name.

5. Change the Security Policy - Network security: LAN Manager authentication level: Send LM & NTLM responses.

6. To fix accessing NetBIOS name issue, you may setup Primary DNS Suffix or WINS server.

7. Make sure client for Microsoft Networks is enabled.

8. To fix mapping my documents folder, use quotation like net use H: "\\chicagotech\my documents"

9. Make sure the Workstation service is running on the local computer while Server service is running on the remote computer.

Can ping VPN server but receive System error 53 using net use

Q: I can establish VPN and ping remote computers. However, I can't access remote computer shared folders. When using net view \\192.168.1.11 or net use \\192.168.1.11 (192.168.1.11 is VPN server IP) I receive system error 53. What's the problem?

A: I would check the firewall first. Or to test it, disable the firewall if you have one.

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.

8) If your computer is loaded NetWare IPX or NWLink, you may receive system error 53. You may want to disable the NWlink or move it lower than TCP/IP in in network binding order.

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

2. Enable file and printer sharing.

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

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, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer \Parameters\NullSessionPipes

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.

Example of VBScript - Mapping a network drive based on the group

'Map a network drive if the user is a member of the group.

'Alert the user if the drive cannot be mapped.

If IsMember (objUser, "accounting") Then

If Not MapDrive ("Q:", "\\chicagotech\data") Then

MsgBox "Unable to Map Q: to AdminShare"

End If

Example of batch file - make a network drive

net use h: \\hostname\sharedname

Where is logon script located

By default, on Windows NT 3.x and 4.0 DC and workstations, the %SystemRoot%\System32\Repl\Import\Scripts folder is shared as NETLOGON for saving logon script. On Windows 2000/2003 servers, the %SystemRoot%\Sysvol\Sysvol\domainname\Scripts folder is shared as NETLOGON. On Windows 2000/XP workstation, the default location for local logon scripts is the %Systemroot%\System32\Repl\Imports\Scripts folder.

The %Systemroot%\System32\Repl\Imports\Scripts folder is not created on a new installation of Windows. Therefore, the %SystemRoot%\System32\Repl\Imports\Scripts folder must be created and shared out with the share name netlogon. 

How to synchronize the computer's clock with that of a domain

To synchronize the computer's clock with that of another computer or domain, use net time command, for example, net time \\chicagotech /set /yes.

Example of VBScript - Mapping a network drive based on the group

'Map a network drive if the user is a member of the group.

'Alert the user if the drive cannot be mapped.

If IsMember (objUser, "accounting") Then

If Not MapDrive ("Q:", "\\chicagotech\data") Then

MsgBox "Unable to Map Q: to AdminShare"

End If

Example of batch file - make a network drive

net use h: \\hostname\sharedname

How to fix the logon script not running

SYMPTOMS

If a slow network connection is detected during the initial logon process, the logon script may not run. Resolution: try one or more of the following policies.

1) go to MMC>Local Computer Policy>User Configuration>Administrative Templates>System>Group Policy, check Enable Group Policy slow link detection, and then type 0 in the Connection speed box.

2) Enable Scripts policy processing, and then select the Allow processing across a slow network connection check box.

By the default net use command map the drive persistently

Q: We use logon script to map network drives. The XP clients keep getting Windows was unable to map all of your 

network drives or the local drive is already in use, even it is able to map the drives. Why?

A: By the default net use command map the drive persistently. To fix this problem, use NET USE I: \\servername\folder /persistent: no.

IE runs slow after installing the Microsoft update

Case 1:

Re-installing XP SP2 fixed the problem - Some files may be damaged. Re-applying the SP will replace the damaged files.

Case 2:

Some people have fixed this problem by disabling the Windows Image Acquisition service, which you can do by using the following steps:

1. Click Start -> Run.

2. Type "services.msc" and hit enter.

3. Double-click "Windows Image Acquisition (WIA)".

4. Change the Startup Type to Disabled and click Apply.

5. Click the Stop button, if it is available.

6. Click the OK button.

Case 3: 

After cleaning cookies temporary file, it runs normal.

Case 4: 

I instilled latest NIC driver, that fixed the issue - After installed Microsoft update, some hardware may need to upgrade firmware or driver.

Case 5: 

I used System Restore to remove all update. It works as before.

System error 85 has occurred.

The local device name is already in use.

Logon slow

The logon script maps only some network drives

The logon script stops with error.

Symptoms

When logon domain computers, a new user may have the following issues:

1. You receive “System error 85 has occurred”.

2. Or “The local device name is already in use”.

3. Logon slow

4. The logon script maps only some network drives

5. The logon script stops with error.

 Troubleshooting:

1. DNS setup correct.

2. Computer browser works fine and you can access all network resources normally.

3. Problem: The Default User was created to map a no-existing server with persistent switch so that any new users who logon will receive above mentioned issues.

4. The mapping letter e.g. H has been used.

 Resolutions:

1. Re-create a new default user profile.

2. Use net use * /d to delete the persistent mapping.