Microsoft KB Archive/297278

= Authentication May Still Be Required When You Use Cached Credentials =

Article ID: 297278

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-



This article was previously published under Q297278



SUMMARY
This article describes the necessity of the authentication process even when you use cached credentials. After you log on to a computer that is running either Windows 2000 or Windows Server 2003 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.

After you establish the remote access 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.



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

The required authentication can be performed by following one of two methods:
 * You can obtain a Kerberos protocol ticket when you attempt to map the drive.
 * You can specify the credentials when you attempt to map the drive.

The process to obtain the Kerberos protocol ticket occurs in the background. Typically, you are unaware of this process, unless it is unsuccessful, in which case you can receive the error message in the Summary section.

NOTE: To return to NTLM authentication (such as, when you attempt to access a Windows NT 4.0-based computer) the workstation must still be able to locate a (Kerberos) Key Distribution Center (KDC) in its domain, and then the workstation must be unable to obtain a ticket for the target server (that is expected when the target server is a Windows NT 4.0-based computer). If a KDC cannot be located, the computer does not return to NTLM.

Specifying the Credentials When You Map a Network Drive

 * 1) Right-click My Computer, and then click Map Network Drive.
 * 2) Map the drive letter and the folder.
 * 3) Click Connect using a different user name.
 * 4) Enter the credentials in the universal naming convention (UNC) &quot;Domain\Username&quot; format.
 * 5) In the password box, enter a password.
 * 6) Click OK.

NOTE: These steps must be performed even if you use the same user name and password that had been used to log on to the workstation.

Additional query words: kerberos ntlm cached credentials

Keywords: kbenv kbinfo KB297278

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.