NetStorage and Directory Map Objects

[Anonymous_User]

Due to various circumstances, we are looking to use NetStorage as a means
for users to access files on our network. We currently use Directory Map
Objects, and have modified our login scripts to map drives using the
Directory Map Objects. However, when testing out the functionality of
NetStorage I was not mapping any drives. But when I put a map statement in
the login script without using the Dir Map Objects it seems to work fine.

So, my question is can Directory Map Objects be used with NetStorage, or do
I need to modify my login scripts? Thanks for reading this.

Regards,

HFC

[Anonymous_User]

> Due to various circumstances, we are looking to use NetStorage as a means
> for users to access files on our network. We currently use Directory Map
> Objects, and have modified our login scripts to map drives using the
> Directory Map Objects. However, when testing out the functionality of
> NetStorage I was not mapping any drives. But when I put a map statement in
> the login script without using the Dir Map Objects it seems to work fine.
>
> So, my question is can Directory Map Objects be used with NetStorage, or
> do
> I need to modify my login scripts? Thanks for reading this.

HFC,

No and Yes.
The good news is you can use the <webaccess> variable to make Netstorage
specific mappings. See:
http://support.novell.com/cgi-bin/search/searchtid.cgi?10068983.htm

To make things complicated, with NW65 Netstorage has a new feature called
Directory Map. Have a look at the manual.

Peter

[Anonymous_User]

> HFC,
>
> No and Yes.
> The good news is you can use the <webaccess> variable to make Netstorage
> specific mappings. See:
> http://support.novell.com/cgi-bin/search/searchtid.cgi?10068983.htm
>
> To make things complicated, with NW65 Netstorage has a new feature
called
> Directory Map. Have a look at the manual.
>
> Peter
>
Peter,

Thank you for your reply and input. Based on the info you have given, it
would appear that I am going to have to modify login scripts, anyway. Is
that correct?

HFC

[Anonymous_User]

> Thank you for your reply and input. Based on the info you have given, it
> would appear that I am going to have to modify login scripts, anyway. Is
> that correct?

If you want to loose the Directory Map objects, yes.
Alternative map syntax can be

map x:=server:volume/path
map x:=\\serverdnsname\volume\path
map x:=\\serveripaddress\volume\path

Using server ip address is by far the fastest method when using Netstorage.

You only need to use the <webaccess> variable when you don't want to make
all mappings accessable in Netstorage. For example we show Home- and
groupdirectories, but no mappings to application data.
Netstorage offers many options to show/hide mappings. See
http://www.novell.com/documentation/nw65/netstor/data/h9izvdye.html

Peter


Peter

[Anonymous_User]

> > Thank you for your reply and input. Based on the info you have given, it
> > would appear that I am going to have to modify login scripts, anyway. Is
> > that correct?
>
> If you want to loose the Directory Map objects, yes.
> Alternative map syntax can be
>
> map x:=server:volume/path
> map x:=\\serverdnsname\volume\path
> map x:=\\serveripaddress\volume\path
>
> Using server ip address is by far the fastest method when using Netstorage.
>
> You only need to use the <webaccess> variable when you don't want to make
> all mappings accessable in Netstorage. For example we show Home- and
> groupdirectories, but no mappings to application data.
> Netstorage offers many options to show/hide mappings. See
> http://www.novell.com/documentation/nw65/netstor/data/h9izvdye.html
>
> Peter
>
>
> Peter
>
>
>
Thanks again, Peter. I think it will probably be best if I did edit my
login scripts and use the server's IP address. The reason why I was making
such an effort to avoid messing around with any of the login scripts is
because we have so many of them, in so many containers.

Regards,

HFC

[Anonymous_User]

I know the problem. But you will notice a speedup in Novell Client also.
Using IP addresses means you are avoid using NDS or SLP when processing the
login script.
I try to place as many common lines in the Org login script and refer to
that by an 'include .Org' statement in the OU login scripts.

Good luck,

Peter

> Thanks again, Peter. I think it will probably be best if I did edit my
> login scripts and use the server's IP address. The reason why I was making
> such an effort to avoid messing around with any of the login scripts is
> because we have so many of them, in so many containers.
>
> Regards,
>
> HFC

[Anonymous_User]

> I try to place as many common lines in the Org login script and refer to
> that by an 'include .Org' statement in the OU login scripts.

which is a good tip that bears repeating every once in a while...


--
Cheers!
Richard Beels
~ Network Consultant
~ Sysop, Novell Support Connection
~ MCNE, CNE*, CNA*, CNS*, N*LS