RE: Mapping a network file to IFS

Vern,

Thank you for the information.

Worked perfect.

I guess now all I have to do is make sure the authority for remote users is
setup correctly.

Thanks.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Vern Hamberg
Sent: Wednesday, May 07, 2003 11:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: Mapping a network file to IFS


Nick, you need to create file share for the root of the IFS - this is not a
part of any install - probably a security issue. Or a specific share to the
arms folder. Either way, the easiest way is with OpsNav - I think I had a
recent post on doing this - go to the archives, open the May messages, then
go to the author index and find my name - Vernon Hamberg. If you don't find
that, NetServer administration is somewhere under File Systems in OpsNav.
Try the help text, too.

I usually create a share clled root that is mapped to '/' - you could
create one called arms that is mapped to '/arms'

HTH

Vern

At 03:09 PM 5/7/2003 -0400, you wrote:
>I have the following software:
>OS = 5.1
>Client Access = 5.0
>PC = Windows XP
>
>
>I am trying to map a network drive and keep getting the message
>
>         The network path \\amslocal\root\ams could not be found.
>
>The ams folder exists as part of the root directory in the IFS along with
>QDLS, QCA400 and so on.
>
>My host files (hosts, LMHOSTS) which are located in
>C:\WINDOWS\system32\drivers\etc have the following entry:
>
>         10.0.0.2       amslocal
>
>
>I have no problem starting workstation sessions using the 'amslocal' name
>rather then the IP address. I also have no problem viewing the IFS though
>the AS400 Operations Navigator.
>
>Any suggests.
>
>Nick


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.