目前没有可用的登录主机处理登录请求1311

微软工程师在处理问题troubleshooting的时候，常常要求用户抓包上传日志，但有些环境涉密，不允许这么做，那么该如何处理呢？其实尝试在命令行状态中（DOS窗口），根据命令行返回的error code，就可以很容易搜索到解决方法。比如，像是这个例子”1311 目前没有可用的登录主机处理登录请求 “

SQL 客户端程序无法连接？我的用户又找到我了。ou管理员抱怨说前些天还没有问题啊，不知道今天怎么就不行了。

 

客户端是来自信任域的工作站，要连接到本子域中的一台sqlserver上的共享目录。先找到这台服务器的管理员，询问了server ip and sharename，分别从两个不同网段连接没有问题。再测试本域的sql的用户，没有问题。看样子问题在对方那边。

联系到故障用户，从用户的工作站上尝试在GUI下以serverIpaddresssharename 的方式连接，提示无法找到网络路径。尝试用net use serverIpaddresssharename  /user:username password的方式连接，系统给出了错误信息：“1311 目前没有可用的登录主机处理登录请求。”（繁体的信息是这样的：目前没有可登入的伺服器，所以无法处理登入要求。）奥？什么意思？嗯……看看这个username是哪里的帐户，在域中查找该帐户，不存在。以域管理员MMC连接到sqlserver上的用户和组管理单元(lusermgr.msc)，是本地帐户。

这让我想起来在使用dameware远程连接时也遇到过这样的错误，尝试用下面的命令行却连接成功了！什么原因呢？

net use \\serverIpaddress\sharename /user:sqlserverNetbiosName\username password

System error 1311 – There are currently no logon servers available to service the logon request

症状: 使用缓存进行登陆的主要目的就是允许您访问本地工作站，但是如果您使用缓存的验证信息登录，由于并没有进行域的验证过程，可能导致您无法访问网络资源。例如：

1. 由于各种原因，导致您使用缓存的验证信息登陆到win2k/winxp的工作站。这个问题在很多Windows Server域中的笔记本用户，离开网域的环境，用缓存登陆到本地后，试图创建远程访问连接时，经常遇到 。
2. 您在工作组的网络环境中使用域登陆选项，登录到 win2k/winxp的工作站。

此时你如果试图连接并且MAP网络驱动器的时候，可能无法成功，系统会给出提示：“System Error: (1311) There are currently no logon servers available to service the logon request.”随即察看 一下故障工作站的网络参数设置，啊哈，是网域中经常容易犯的错误。客户端的IP地址是动态获取的，那么对应的dns ip & dns suffix也都是随着IP获取的，可是这些关键的参数都错了。ip不是网域dc的ip，suffix也不对。您看到的文章来自活动目录seo http://adirectory.blog.com/category/system-network-administration/

当client登录到域的时候，需要通过dns进行一系列查询动作，如果在指定的dns上无法查询到登陆dc，就会通过LDAP发出查询dc的请求，第一个响应此请求的dc，负责当前client的登录动作，如果仍然没有dc响应，将使用上次成功登陆到域后，缓存在本地的凭证，进行本地登陆（尽管看起来，您的确是选择了登录到域）。

遂告知信任域的管理员，将参数更正，再次尝试连接sharefolder，成功了。用户也反映，“登陆快多了”

 

一些常见命令行返回的错误信息及解决方法如下：

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 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\LanmanServe\ ParametersNullSessionPipes

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

System error 67 – The network name cannot be foundSymptom: When using net view computer, you may receive above error message.Resolution: make sure you type the correct computer name or shared name.

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: servernamefolder /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您看到的文章来自活动目录seo http://adirectory.blog.com/category/system-network-administration/

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 doesnt 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_USERSTESTNetworkUsername.
   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 emotecomputer
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.

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 servernamesharename /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 doesnt 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 useservername 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 remotecomouterahredname, 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 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 6118 has occurred. The list of servers for this workgroup is not currently available

SYMPTOMS:

1. After enabling ICS/ICF, you cant 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 

gnaw0725 注：以上信息错误转自  http://www.chicagotech.net）