Connecting to a Local Share Using Cached Credentials Is Unsuccessful in Windows NT 4.0 SP4 and SP5

ID: Q231934


The information in this article applies to:


SYMPTOMS

When you log on to a Windows NT computer using cached domain account information, you cannot connect to share points defined on the local computer using your cached credentials.

If you try to connect to a local share using cached credentials, you are prompted for a password. After you type a password, the connection attempt is unsuccessful and you receive a "bad password" or "unknown user name" or error messages. However, you can still connect to local share points using locally defined user accounts.


CAUSE

This problem is a result of the application of the LSA2-FIX security hotfix. The LSA2-FIX is a Windows NT 4.0 post-Service Pack 3 hotfix that is also included in Service Pack 4 and Service Pack 5.

When the LSA2-FIX is applied, connections to share points are allowed only if a domain controller is available to revalidate your cached credentials. This is incorrect behavior. Your cached credentials should be accepted as valid, and the connection attempt should succeed, as long as your domain account has appropriate access rights to the share point.

For more information about the LSA2-FIX security hotfix, please see the following article in the Microsoft Knowledge Base:

Q184017 Administrators Can Display Contents of Service Account Passwords


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

   Date      Time    Size     File Name    Platform
   ------------------------------------------------
   99/05/06  02:47   47,888   Msv1_0.dll   x86
   99/05/06  02:45   79,632   Msv1_0.dll   Alpha 

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


WORKAROUND

To work around this problem, connect to local share points using a locally defined user account after you log on with cached domain account credentials. For example, type the following command:

net use \\computername\sharename /user:computername\username password


STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0.


MORE INFORMATION

This problem affects Windows NT 4.0 systems running:

Additional query words:


Keywords          : kbbug4.00 kbfix4.00 
Version           : winnt:4.0 SP4,4.0 SP5
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: July 20, 1999