nt4 only maps to share and not below.

[Mike Moseng]

I thought I'd ask the experts about this one. Hope you can help! We
seem to be having a problem with our NT 4 workstations mapping home
folders. For example we set H: to \\server\users$\username as the home
folder mapping. This works fine for all 2000/xp workstations as they
get "username on server\users$ (H" in my computer and explorer. The
nt4 boxes don't get the full mapping. What they get is "user$ on
server (H" and when you click on it a message box says access
denied. Now if you open a command prompt you can see H:\username and
are able to access the folder from there. Also, if you do a start >
Run and type \\server\user$\username you get a window and can browse,
add folders etc. Perhaps I could move the NT boxes to a OU and do a
net use to map the home folders (or use novell and do the same for
that matter, but we are migrating away from it) but there must be a
fix. Can't find anything on technet or google. Any suggestions?
TIA

 

[Pegasus \(MVP\)]

I thought I'd ask the experts about this one. Hope you can help! We
seem to be having a problem with our NT 4 workstations mapping home
folders. For example we set H: to \\server\users$\username as the home
folder mapping. This works fine for all 2000/xp workstations as they
get "username on server\users$ (H" in my computer and explorer. The
nt4 boxes don't get the full mapping. What they get is "user$ on
server (H" and when you click on it a message box says access
denied. Now if you open a command prompt you can see H:\username and
are able to access the folder from there. Also, if you do a start >
Run and type \\server\user$\username you get a window and can browse,
add folders etc. Perhaps I could move the NT boxes to a OU and do a
net use to map the home folders (or use novell and do the same for
that matter, but we are migrating away from it) but there must be a
fix. Can't find anything on technet or google. Any suggestions?
TIA

As you discovered, WinNT will not map drive letters to folders
within a defined share, only to the share itself. The traditional
way of mapping home shares is to create one share for each
user instead of a common share for all users.

 

[Mike Moseng]

As you discovered, WinNT will not map drive letters to folders
within a defined share, only to the share itself. The traditional
way of mapping home shares is to create one share for each
user instead of a common share for all users.

So... if I have multiple users on the same nt box they will all need
their own share? Yet if the same folks logon to a 2000/xp no problemo.
I would have thought this was fixed in 2000 / 2003 AD, or at least a
workaround? Thanks for the info, but I was kind of hoping for a more
elegant solution. You know, the eternal optimist!

 

[Lanwench [MVP - Exchange]]

So... if I have multiple users on the same nt box they will all need
their own share? Yet if the same folks logon to a 2000/xp no problemo.

Yes, because they can handle mapping to a subfolder.

I would have thought this was fixed in 2000 / 2003 AD, or at least a
workaround?

It's about the client, not workstation, in this case. Look into the SUBST
command.

Thanks for the info, but I was kind of hoping for a more
elegant solution. You know, the eternal optimist!

Can you upgrade the NT4 boxen to 2k/XP? Really best to keep all workstations
as identical as possible - you can't really make use of roaming profiles
with your current config. I'd put everyone on the same workstation OS and
keep the software build as identical as possible between computers for ease
of roaming/admin.

 

[Mike Moseng]

Yes, because they can handle mapping to a subfolder.


It's about the client, not workstation, in this case. Look into the SUBST
command.


Can you upgrade the NT4 boxen to 2k/XP? Really best to keep all workstations
as identical as possible - you can't really make use of roaming profiles
with your current config. I'd put everyone on the same workstation OS and
keep the software build as identical as possible between computers for ease
of roaming/admin.

Unfortunately we have about 20 NT wkstns left that can't be upgraded
due to compatibility issues.

I did find a solution. DFS! and mapped a "root" to the shares. Works
for now. I still am looking for an active directory or wkstn solution
subst wont work with all who log on the box.

 

[Pegasus \(MVP\)]

So... if I have multiple users on the same nt box they will all need
their own share? Yet if the same folks logon to a 2000/xp no problemo.
I would have thought this was fixed in 2000 / 2003 AD, or at least a
workaround? Thanks for the info, but I was kind of hoping for a more
elegant solution. You know, the eternal optimist!

Creating a share for each user is not such a big deal as
you might think. If you have a list of all users in c:\users.txt
then this simple batch file will do it:

@echo off
for /F %%a in (c:\users.txt) do (
md d:\Users\%%a
net share %%a=d:\users\%%a
)