Net Use h: /home doesn't work on NT and Win9x clients.
Posted on 2001-07-10
Here's my problem.
I have a Windows 2000 domain with mostly Windows 9x and NT 4 clients.
I created a user in a certain container. Then, I pointed
this user's home directory to a share on the Domain Controller. When I login as the user, I get an error
on the login script process (The errors are given later). The error occurs when issuing the following command on both Windows95, Windows98 and WindowsNT workstations. The error does not occur on Win2K clients.
net use h: /home
However, the error does not occur on the subsequent
net use s: \\MyServer\shared$
When I issue "net use h: /home" at the DOS prompt I
get the same error.
To further complicate things, I know the user has
rights to their home directory because when I map to
it directly, as in "net use h: \\MyServer\austins$",
the command completes successfully.
Here's the final kicker. When I make the user a part
of the "Domain Admins" group, everything works fine.
The error I get on the NT machines states the following when the user is not in the "Domain Admins" group.
"Unable to determine home directory"
The error I get on the Win9x machines states the following when the user is not in the "Domain Admins" group.
"Error 5: You do not currently have access to this file. The file may be marked read-only, or it may be part of a shared resource such as a folder, a named pipe, a queue, or a semaphore. You can use the ATTRIB command to change
the read-only attribute, or try again later when the file may be available."
I loaded the DSCLIENT on a Win9x workstation
to see if that makes a difference. It didn't. It would appear that there is a rights problem for non-Win2K clients in setting the home directory variable. You see the home directory information must be read at login, then
the environment variables "HOMEPATH", "HOMEDRIVE" and
"HOMESHARE" must be set from the user profile.
Finally the home directory itself can be mapped with
"net use <drive letter> /home".
Since placing the user in the "Domain Admins" group
solves the problem, it must be a rights issue. Any
thoughts you have on this matter are greatly
Thanks for the help.