Windows NT 4.0 and Novell Server with 4.11

Thread View: comp.os.netware.misc

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Dan Renfro Mon, 20 Jul 1998 00:00

#16

Author: Dan Renfro
Date: Mon, 20 Jul 1998 00:00

22 lines
1894 bytes

My company is utilizing a Novell 4.11 server.  Our workstations are
comprised of WIN 3.11, WIN 95, WIN 98, WIN NT and DOS.  All the workstations
are fine, except the machines running NT 4.0.  They all have service pack 3
installed.

What is happening is that when the system logs you in (w/Novell Intranet
Client), the network drives are map rooting (?).  When you use windows
explorer it will say "such and such" directory on R:\.  But when you go out
to the dos prompt, it shows that you are in the root, not the such and such
directory.  If you list out the directory in dos, you get a listing for the
such and such directory.  So consequently many of batch files are unable to
run.

You can go out using the map commands, and remap each drive individually.
but when you reboot, or even just exit from the dos window and come back in,
it restores the original settings.

Would anybody know how to overcome this.  I find hard to believe that this
is just a problem that has to be lived with.

Dan Renfro
danr@cicom.net

Re: Windows NT 4.0 and Novell Server with 4.11

#17

Author: Wallace Marks
Date: Mon, 20 Jul 1998 00:00

33 lines
2304 bytes

"Dan Renfro" <danr@cicom.net> wrote:

>What is happening is that when the system logs you in (w/Novell Intranet
>Client), the network drives are map rooting (?).  When you use windows
>explorer it will say "such and such" directory on R:\.  But when you go out
>to the dos prompt, it shows that you are in the root, not the such and such
>directory.  If you list out the directory in dos, you get a listing for the
>such and such directory.  So consequently many of batch files are unable to
>run.

There's an undocumented feature in the IntranetWare client to get
around this:

1. Right-click on My Computer
2. Select Properties
3. Select the Environment tab
4. Type MAPROOTOFF in the Variable box (case-sensitive, BTW)
5. Type 1 in the Value Box
6. Click on the Add button
7. Reboot

The result of this is that the Map command will now work as expected.
An explicit MAP ROOT command will actually map a root, while a plain
ol' MAP command doesn't.  I haven't tested this with v4.3, but it
works great with 4.1.

     Wallace Marks          ("`''-/").___..--''"`-._
  Systems Administrator      `6_ 6  )   `-.   (    ).`-.__.`)
National Vision Associates   (_Y_.)'  ._   )  `._ `. ``-..-'
(770) 822-2030 / 2381 Fax  _..`--'_..-_/  /--'_.' ,'
   wmarks@atlcom.net      (il),-''  (li),'  ((!.-'

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads