Drive Mapping from NW6 to Microsoft Client for Netware WIN98 Machine
Rich Atwater
through DOS and then load the Microsoft Client for Netware Networks to
attach and login to the network, which then allows us to download any
necessary files (including Client32) and set them up. However, since moving
to NW6, the drive mappings do not appear correctly and we have to do some
manual steps in order to make sure things work the way they used to. We use
a container login script, and we've also copied that to the NET$LOG.DAT file
located in the SYS:PUBLIC folder on the server. We have three drive
mappings: one to the server's VOL1 volume, one to the server's SYS volume
and a search drive to the server's SYS:PUBLIC folder. When I go into Windows
Explorer after logging in, all three drives show up as being mapped to SYS.
If I go to a DOS window, and map the drive manually, the same way the login
script is setup to do, it maps it. The user account has the necessary rights
(read and file scan to necessary folders on the volumes). Here's a copy of
the section of the login script that we're using. I will also put in the
variations I've tried with no success:
* The following lines exit the OS Batch Install User from the login script
IF LOGIN_NAME="INSTUSER" THEN
DOS SET DIRCMD="/P /O:GNE"
DOS SET USER="USER"
MAP INS S1:=<ourservername>\SYS:\PUBLIC
MAP F:=<ourservername>\VOL1:
MAP I:=<ourservername>\SYS:
@I:\PUBLIC\OSSETUP.BAT
EXIT
END
For the each of the drive mappings, we've also tried these variations:
MAP INS S1:=<ourservername>\SYS:PUBLIC
MAP INS S1:=<ourservername>_SYS:\PUBLIC
MAP INS S1:=<ourservername>_SYS:PUBLIC
MAP INS S1:=<ourservername>/SYS:\PUBLIC
MAP INS S1:=<ourservername>/SYS:PUBLIC
And they've all just given us the SYS volume. Not mapping to Public as a
search, or in the line with VOL1, not mapping to VOL1.
Any suggestions/ideas?
Can someone let me know if this client (the one that Microsoft Provides with
Windows 98 2nd Edition) uses the container login script found in NWADMIN, or
the NET$LOG.DAT file so I know where to make changes for this?
Thank you,
Rich
Craig Wilson
if VOL1 is NSS while SYS is traditional. Not sure how their client would handle
NSS>
Rich Atwater wrote:
--
Craig Wilson
CNE3, 4, 5 - MCSE - CCNA
NSC Sysop (http://support.novell.com/forums/)
Tech Writer - http://www.ithowto.com
(I Peter 4:10)
Rich Atwater
same machine the same way I had detailed in the login script using that same
client. Do you know which login script it's reading from? The one in NWADMIN
or the NET$LOG.DAT? That may help me, as I can make changes and keep trying
things as long as I know for sure which one to change.
Thanks,
Rich
"Craig Wilson" <craig_d...@yahoo.com> wrote in message
news:3FD7B971...@yahoo.com...
Craig Wilson
directory.
But I have not used that client for probably 7-8 years, so I can't speak too
much about how it works.
Microsoft does have an pseudo NDS client that is named something slightly
different that will read the NDADMIN settings, but I have not used that one much
either.
You may want to try the MS forums since this forum is designed mostly for
Client32 and most readers are far less familiar with the MS Client.
Generally I keep Client32 on a local FTP Server (Actually a Novell Box), which
allows for the fast downloading of the client from any machine on which I may
need the client.
hsp...@yahoo.com
I have a similar problem, but my users can not see any NSS volumes. Any
ideas?
Hector
Craig Wilson
context as well as IPX is configured on the server.
The MS forums is the best forum for questionsn about their client.
Few people use that client here.
You could also consider using Native File Access and then using the MS
Client for MS Networks to attach to your NW6 server.
hsp...@yahoo.com wrote:
--