General discussion

Locked

Logon script / share visability

By DJehan ·
I am trying to sort out one mess of a network, including users home directories. We have a logon script that maps drives, but the users home dir's are simply folders underneath a share. I have been following posts on this topic, but so far to no avail.

If I use "net use h: \\server-name\share\%USERNAME%", I get an Error 50 from NT. If I use "net use h: \\server-name\share\users" it works fine, but the client can see ALL directories, even those assigned $.

So my questions are;
1) How is USERNAME defined, and where?
2) Am I better off creating a new share and starting from scratch ?
3) Why does the $ not hide the dirs from other users?

I need to be able to map a drive directly to the users home dir on the server, hence my frustration.

I'm not an NT guru, so any help gratefully appreciated.

Thanks

Darren

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Logon script / share visability

by DJehan In reply to Logon script / share visa ...

UPDATE

I now understand that the %USERNAME% environment variable is not available on the W95 clients, hence the reason NT fails on this (I assume).
However, I also tried the "net use h: \\servername\share\userdirectory" and that also failed as well.

I have now mapped the users home directory in User Manager (Profiles) and in the logon script, used "net use h: /HOME" which DOES work. However the W95 explorer can see all users directories, although access is restricted correctly.

How can I take this to the final stage and have "h" mapped directly to the directory ?

Server is NT4 SP6, clients are W95.

Cheers

Collapse -

Logon script / share visability

by erikdr In reply to Logon script / share visa ...

AFIK *not*. W9x is restricted in this respect, it can only map a driveletter to a share and not (like NT Workstation) to a subdir one level lower.

You could experiment a bit with the SUBST command, this basically does what you need - but it costsruntime performance and has its drawbacks to.

Have fun,

<Erik> / The Netherlands

Collapse -

Logon script / share visability

by DJehan In reply to Logon script / share visa ...

The question was auto-closed by TechRepublic

Collapse -

Logon script / share visability

by NetTek In reply to Logon script / share visa ...

Mapping to a users home directory in NT is called a deep net use. It does not work by default in Win9x. NET USE H: /HOME will only create a drive mapping to the share that contains the home directories, not the home directories themselves. To make it work, you would have to first take ownership of a users home directory. Then move the users home directory from the default home directory share to another non-shared directory. Then create a hidden share for the users home directory. Then restore rights for the user (they disappear when you take ownership). Then set up the users personal logon script to map to that hidden share. A lot of work.

%USERNAME% variable will not work for 9x. I do not know if 9x has a similar variable, but it wouldn't work because NT wouldn't recognize it.

The reason why the $ did not hide the share is because you have two shares: The directory that contains the users home directory, and the actual users home directory. Because the directory that contains the users home directory is shared, you can see all the directories inside it. The $ you place on the users individual home directory hides it in network neighborhood, but does not hide it inside another share.

Collapse -

Logon script / share visability

by DJehan In reply to Logon script / share visa ...

The question was auto-closed by TechRepublic

Collapse -

Logon script / share visability

by Magetower In reply to Logon script / share visa ...

Looks like you are looking for a simple answer.

The following presumption is being made:
1. You wish to maintain the current file structure.

The first thing to do is to share out each individual user home directory using a $ to hide the share. Use the users ID to name the share. (e.g. jdoe$)

Next using User Manager on the server modify the users account. Go into the profiles area and change the home directory to match the share you just created.

Verify that this works by logging the user off then on again. Then remove the share for the overall Homes directory when you complete what you wanted. This will cut off anybody else from viewing the list of user home directories.

You should only have to use the login script to map the home drive if the server login profile does not work.

Collapse -

Logon script / share visability

by DJehan In reply to Logon script / share visa ...

The question was auto-closed by TechRepublic

Collapse -

Logon script / share visability

by Magetower In reply to Logon script / share visa ...

Looks like you are looking for a simple answer.

The following presumption is being made:
1. You wish to maintain the current file structure.

The first thing to do is to share out each individual user home directory using a $ to hide the share. Use the users ID to name the share. (e.g. jdoe$)

Next using User Manager on the server modify the users account. Go into the profiles area and change the home directory to match the share you just created.

Verify that this works by logging the user off then on again. Then remove the share for the overall Homes directory when you complete what you wanted. This will cut off anybody else from viewing the list of user home directories.

You should only have to use the login script to map the home drive if the server login profile does not work.

Collapse -

Logon script / share visability

by DJehan In reply to Logon script / share visa ...

The question was auto-closed by TechRepublic

Collapse -

Logon script / share visability

by DJehan In reply to Logon script / share visa ...

This question was auto closed due to inactivity

Back to Windows Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums