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
/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
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.
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
will get this error too)
System error 1331 has occurred - Logon failure: account current disable
When using net use \\computername command,
you may receive above error message.
is cache credentials issue. To fix this problem and cache the credentials, use
System error 1385 has occurred - Logon failure: the user has not been granted
the requested logon type at this computer
Symptoms: When using net
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 1385 - Logon failure
System error 1396 has occurred - Logon Failure: The target account name is
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
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
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.
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>
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
3) No master browser. Starting Computer Browser Service on one of w2k/xp
computers should fix the problem