yet another H drive mapping problem

[ssphoenix]

Don't know what am I doing wrong but I've gone to several of your posts and cannot get the H drive to work.

I've tried several ways.

\\servername\users\username (share as username)
\\servername\users\username (share as username$)

then I use the command

net use H: /home in the \winnt\system32\repl\import\script folder

someone posted earlier that you can connect to a share or hidden folder. Does not work for me. Either way, does not connect to the username folder. It only connects to users but not the home users folder.

In the User Manager for Domain I have H and \\servername\users\%username% in the to field.

what am I missing?

help would be greatly appreciated.

 

[Voyager1]

You've got your URLs a bit wrong. Once the folder has been shared (in your example username$), then you should not mention the upper folder anymore.

When you create the user's account in user manager, you specify "\\servername\users\%username%" as the home folder, and user manager creates the folder for you. Then you go out and share the folder as "username$" (a hidden share). Now, go back to User Manager and change the home directory to "\\servername\%username%$". This will take it directly to the user's folder without regard to the "users" folder. In a login script, the "NET USE H: /HOME" command should now work.

Once the folder has been shared, drop the "users" folder from the address.

Hope this helps... - Bill

"You can get anything you want out of life, if you'll just help enough other people get what they want" - Zig Ziglar

 

[ssphoenix]

Thanks for your reply. I've got the share part right soon after I posted the message. However, from Win85 pc's the mapping does not take place.
Currently I am migrating from novell. I took out the novell script that maps the H drive. For some reason it does not map the drive.

Only works if I do it from dos.

 

[rnewton]

Remember that Win95/Win98 clients have a problem seeing any shares that have more than 12 characters in their shared name. It is best to adhere to the 8.3 format when naming shares regardless of what the OS can see locally to avoid problems across the network.