Drive mapping?

[DaveGoTech]

We have 5.1 installed with several volumes mapped for the users. We also installed an NT server on this network to run a couple of Windows programs. I am trying to map an NT directory in the login script but can't find any info on the syntax. For example: the Server name is NTSERVER, the NT Share name of the drive is E: and the directory is DATA. I would like to map this to G on the workstations.
Any assistance would be appreciated.

 

[TheLad]

In your login script (for NT/W2K workstations only):

#NET USE G: \\NTSERVER\E$\DATA /USER=<username> <password>

or leave the username and password field out if the user in question has a username and password that matches that of his/her NetWare account. # in the login script before the command is a must! &quot;My mamma used to say that life is like a box of chocolates .... you never know what you're gonna get!&quot;

 

[DaveGoTech]

TheLad:
Our clients are WIN98, so I assume the script would be:
map root G:=\\NTSERVER\E$\DATA
(Users do have identical login names on both servers.)

 

[TheLad]

No, if memory serves you cannot use MAP to map to NT servers. Just use the following (run a COMMAND from your Win98 workstation and test it first, without the # of course ...):

#NET USE G: \\NTSERVER\E$\DATA &quot;My mamma used to say that life is like a box of chocolates .... you never know what you're gonna get!&quot;

 

[yvfwc]

What TheLad said is correct for Win98. If this is a public share for a user however, just point to that share instead of the Admin share of E$:
#NET USE G: \\NTSERVER\DATA

Cheers,

Mark ;-)

 

[DaveGoTech]

Thanks for the help. The syntax you suggested is correct. I can do this at a DOS prompt on the workstation and the drive gets mapped, but when I inserted the srting into the login script and signed-on, the statement errors saying that this is not permitted at this time because you have not logged on yet. (Note: in windows networking, Novell client is the preferred logon).

 

[TheLad]

Hmmm, you could place a batch file in the users Startup folder so that it gets run as part of that? This could be controlled so that your login script says:

if member of <group name> then
copybat.bat
end if

where copybat.bat copies the net use batch file into the users startup directory. To remove this, simply add a delete command before the if statement. &quot;My mamma used to say that life is like a box of chocolates .... you never know what you're gonna get!&quot;

 

[FredWagner]

If the mapping will not change often, do the mapping to the NT box in the user's
win98 desktop, and it will reconnect every time they boot up. We use this for Win95 boxes to connect to our Notes server running on Win2K. With our NT and Win2K workstations, the domain login script takes care of the NT mapping, but on Win95, it takes one-time manual mapping in the desktop.

Fred Wagner
frwagne@ci.long-beach.ca.us

 

[dan]

An easier way would be to map the drive in windows (after you are logged in) and check the box to connect next time you logon. (Ie. use windows mapping instead of the login script)
Dan

 

[DaveGoTech]

We would rather not use Windows drive mapping (or Novell Client mapping) as this is a 'manual' operation. There are already about 6 drives mapped in the script. There are also many clients, which are continually being upgraded/moved, etc. and we would like to automatically setup as many settings as possible, thus the reason for including this in the script.

 

[FredWagner]

If you don't want to use Local mapping, a login batch file in a Domain login script will do what you want, by including the Net Use command to do the mapping. It's slow and crude, but it does work, with late Win95 and above. But you have to have a Domain login... do you want to go to the hassle of implementing a domain, or do you already have one? Also, have you tried NDS for NT? That might make it easier to do what you're trying....

Fred Wagner
frwagne@ci.long-beach.ca.us