RE: File shares and IFS

["ian" <ian@xxxxxxxxxxxxxxxxx>]

We use the IFS quite a lot in our systems.

We do not use Ops nav at all, other than to set the initial share for the
specific folder (i.e. read, read/write).
You do not need to set a share for root.

After you create the folder initially on the iSeries (presumably with MKDIR)
you can then set authorities specifically for Users, Groups etc with the
WRKLNK command

When using WRKLNK and navigating to your folder, option 9 then can be used
to set/exclude access to the folder.
Its more like Unix (which I do not understand) than iSeries, except you can
use *PUBLIC, groups, specific iSeries User ID's, etc in the authorities.

After setting that, we normally put a shortcut onto the Users desktop
(Windaz), to the folder. Standard Windaz authorities access then applies, as
directed through the NetServer server.

I think..

Regards,

Ian Patterson
Grange IT Limited

-----Original Message-----
From: midrange-l-bounces+ian=grangesystems.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+ian=grangesystems.com@xxxxxxxxxxxx]On Behalf
Of vhamberg@xxxxxxxxxxx
Sent: 20 April 2005 20:15
To: Midrange Systems Technical Discussion
Subject: Re: File shares and IFS


You have to use file shares for someone on Windows to see the directories in
the IFS. You set up shares with Navigator but, IMO, no one should use
Navigator to view files through these shares - instead, they should use
Windows Explorer with either a mapped drive or use the network name of the
iSeries and go from there, just like any other Windows networking setup. In
fact, except for folks that need to administer NetServer (the thing that
provides Windows networking), I might even remove that function from users
on their PCs.

You can put security on directories and their contents, someone suggested.
Then these users would be authenticated with OS/400 security and could go
only where you let them go.

-------------- Original message --------------

> Hello.
>
> I have what I think is a simply fixed problem, but I do not know the
> solution. We are setting up archiving on our ISeries for our invoices. We
> have created PDFs from them, and right now I am storing them in a
> subdirectory off the ROOT directory and I am creating shortcuts through
> Windows Network Neighborhood for the users. I am keenly aware that this is
> not the most secure way to do this, more likely it is the least secure
way.
> I have read some posts about file shares through ISeries Navigator. What I
> am seeking is the absolute most secure way to have the users access these
> files. With the setup the way it is now, any one of them could navigate
> up a level and have access to the ROOT directory itself, which I don't
> want. I just want them to be able to have access to the one directory
> where these files reside, and that is ALL. No ability to navigate up a
> level, nothing like that at all. Is file shares the way to go for this,
> and if so, is it possible to set these up so it is just a shortcut on the
> desktop instead of having the users open up ISeries Navigator each time?
> Please advise. Any help is greatly appreciated. Thanks!
>
> Bill Howie
> Programmer/Analyst
> Coastal Pet Products, Inc.
> Voice: 330-821-7363 x359
> bill.howie@xxxxxxxxxxxxxx
--
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/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.