Creating Windows 95 Home Directories on Windows NT Server

Last reviewed: May 8, 1997
Article ID: Q137979
3.50 3.51 95 WINDOWS kbinterop

The information in this article applies to:

  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft Windows 95

SYMPTOM

Your Windows 95 clients cannot connect to their home directories even though you create a profile in Windows NT User Manager that specifies the Windows 95 users' home directory and drive letter to use for the connection.

CAUSE

Windows NT is not properly configured or your script is incorrect.

RESOLUTION

To allow Windows 95 users to connect to their home directories on the server, create a logon script to connect a Windows 95 client to a home directory and configure your Windows NT Primary Domain Controller (PDC) as follows:

  1. Create a test logon script on the Windows NT PDC for Windows 95 client workstations:

    echo on net use * /HOME pause

  2. Place the script file in the SYSTEM32\REPL\IMPORT\SCRIPTS directory on the Windows NT PDC. (You may also want to set up File Replication so the logon scripts you create are available on all domain controllers.)

  3. Make sure that the test user logging on has Full control of the \SCRIPTS directory and at least Read permission on the Netlogon share (the default share of \WINNT35\SYSTEM32\REPL\IMPORT\SCRIPTS).

  4. Create a subdirectory called TEST in the shared Users directory. By default the shared Users directory is C:\USERS.

  5. Share the Test subdirectory with the share name TEST and give the test user 'Full Control' permission to the share. 6. Run User Manager for Domains and select the user for the test.

  6. From the User menu, choose Properties.

  7. Choose Profile in the User Properties dialog box.

  8. Type the test logon script name in the Logon Script Name field.

  9. Under Home Directory, in the To field type:

    \\<server_name>\TEST

    NOTE: Ignore the drive letter in the Connect field.

  10. Log on as the test user at the Windows 95 client.

    The following text appears at the command prompt:

    c:\win95>echo on c:\win95>net use * /home d: connected to \\<servername>\TEST c:\win95> pause Press any key to continue. . .

  11. On the Windows 95 client, press any key to continue. Then doubleclick the My Computer icon.

    NOTE: In My Computer, the home directory maps to D: (or the next available drive letter on the client).

  12. If the logon script executes correctly, you may delete the Echo On and Pause lines from your script resulting in your script consisting of only the following line:

    net use * /HOME

    NOTE: You may specify a drive letter in place of the Next Available Drive symbol, the star (*). You may also rename the Users\Test directory to any name; be sure to make the corresponding changes wherever this new directory name is used.

MORE INFORMATION

Using NET USE * /HOME from Multiple MS-DOS Command Prompts

If you use the NET USE * /HOME command from more than one MS-DOS command prompt in Windows 95, your current directory is going to be set incorrectly. Your current directory is going to be the root of the server containing your home directory instead of your default home directory.


KBCategory: kbinterop
KBSubcategory: ntconfig
Additional reference words: prodnt 3.50 3.51 win95 win95x winnt
Keywords : ntconfig kbinterop
Version : 3.50 3.51 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: May 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.