× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2003

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



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.