|
On the user's PC, do Start - Run and enter CMD. At the command prompt, enter: NET USE [driveletter] \\[servername]\[sharename] [password] /user:[username] /persistent:yes The /persistent:yes will make the share survive reboots. Re-do the command each time the password changes. If it doesn't persist across reboots, do the command w/o the /persistent parm, then just do NET USE /PERSISTENT:YES Do NET USE /? For some very rudimentary help. -----Original Message----- From: Ian Patterson [mailto:ian@xxxxxxxxxxxxxxxxxxxx] Sent: Friday, January 30, 2004 4:11 AM To: midrange-l@xxxxxxxxxxxx Subject: Automatic signon to IFS from PC Anyone have a tip or technique for the following problem: I have a PC program that needs access to the IFS. Client Access is not installed on the PC. If I initially access the IFS using Windows Explorer, and signon to the AS/400, prior to using the PC program, everything is OK If I omit this stage, there is no access to the IFS (I understand why). My PC program can detect if its not connecting to the IFS, so is there a way that I can then automatically signon & use the IFS without prompting the User ? There is not a security issue here, as its the PC program that is accessing specific IFS files, the PC User doesn't even know this. I can create any User profiles on the AS/400. The PC User does not need their own AS/400 profile. Regards Ian Patterson
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.