"Connect Network Drive" Caches First Credentials Supplied
This article was previously published under Q154738
This article has been archived. It is offered "as is" and will no longer be updated.
When you connect to a remote resource using the Connect As and Reconnect AtLogon options within either File Manager or Windows Explorer, Windows NTcaches the first set of credentials supplied, even if these credentials areinvalid and fail to provide access to the remote resource. Subsequentattempts to access the remote resource with valid credentials will give theuser access to the resource, but do not change the cached credentials usedwhen reconnecting.
Be sure to provide the correct set of credentials when filling in theMap Network Drive dialog box.
Microsoft has confirmed this to be a problem in Windows NT version 4.0. Weare researching this problem and will post new information here in theMicrosoft Knowledge Base as it becomes available.
Steps to Reproduce the Problem
- Open Windows Explorer and click Map Network Drive.
- Specify the standard UNC \\<servername>\<sharename>.
- Specify a <DomainName>\<UserName> in the Connect As field,misspelling either the DomainName or the UserName.
- Click the Reconnect At Logon check box.
- Click OK.
- You can now correct your mistake from step 3 by typing theproperly spelled DomainName or UserName. Also type the password.
- Click OK. You should now be mapped to a resource.
- Log off and then log on again.
- During the logon sequence, you will be prompted to providecredentials to reconnect to the resource. Note that the misspelledDomainName or UserName is displayed, and you cannot change eitherone. You must click Cancel at this point. Also, you should click the"Do not Try to Restore this Connection in the Future" check box.
Article ID: 154738 - Last Review: 12/04/2015 15:12:59 - Revision: 1.1
Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition
- kbnosurvey kbarchive kbnetwork KB154738