Windows NT Shares Inaccessible with Net Use in Login Script

 Last reviewed: August 1, 1997
Article ID: Q161051
The information in this article applies to:
  • Microsoft Windows 95
  • Microsoft Windows 95 OEM Service Release versions 2, 2.1

SYMPTOMS

When NET USE commands are used in a Windows NT login script to connect to Windows NT servers in various domains, you may not be able to access those drives.

A network drive may appear in Windows Explorer, but when you click the drive, an error message such as "No files found" or "Access denied" may appear. If you disconnect the network drive and then reconnect to the same resource, you can then access the files on the drive.

Also, the following error message may occur when a login script with NET USE commands is being used: 

   Profile error 4: The file cannot be created. The volume may not 
   support long file names.  Some of your profile settings may not be 
   available. Do you want to see this message in future?

CAUSE

This symptom can occur if all of the following conditions exist:

  • The Windows NT domains are organized into a Multiple Master domain model, in which there are at least two Master (account) domains trusted by the Resource domains.
  • User accounts with the same user name, but different passwords, exist in more than one of the Master domains.
  • The NET USE command in the login script is attempting to map a drive to a share on a server that is a member of a Resource domain.

RESOLUTION

You can work around this issue by ensuring that user account names are unique across all Master Domains, so that duplicate user names do not occur.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows 95. A fix to this problem is in development, but has not been regression tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Technical Support for more information about the availability of this fix.

MORE INFORMATION

This problem occurs when different user accounts exist in different Master domains, but with the same user name. For example: 

    Domain    User name   Password   Full name
    --------------------------------------------
    MASTER1   JOHNSMIT    abcdefg    John Smith
    MASTER2   JOHNSMIT    tuvwxyz    John Smiter
Under these conditions, the logon domain name is not included in the user account information sent by Windows 95 when the NET USE command is issued. Therefore, the user name is not necessarily resolved to the correct user account in the correct domain. The NET USE command may finish without errors, but the command is processed for the wrong user account. If the passwords are different, the password is incorrect for that account, and access is denied.

Additional query words: 95
Keywords : osr2 win95 kbnetwork
Version : 95
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.