|
Try it without you having authority to the authorization list. The point of that authorization list is to prevent mapped drives to qsys through windows explorer. Once CA Express came out, you could simply not share qsys and keep your users from mapping to qsys. Nowadays, though, it is becoming harder and harder to control what's on the client so you need to lock down the server more and more. This tool requires neither Client Access with support for mapped drives nor a drive to be configured as shared via OpsNav - it can still get to the files. Because this tool is in java using a freely downloadable as400toolbox it occurs to me that, although we're dead-bolting the front door, we may be leaving the key under the mat. Phil > > I did not have QPWServer AUTL set to exclude. I just set it now to test, > and it still allowed me access, but I have not restarted any servers, so I > suspect that the authorities have not refreshed?? > > Kevin > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
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.