RE: Client Access Incoming Remote Command

So sounds like you need to change the user ID that Incoming Remote
Command Service runs under.

Check the properties of the above service in Windows control panel.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Giusto
> Sent: Tuesday, November 22, 2005 7:46 PM
> To: MIDRANGE-L@xxxxxxxxxxxx
> Subject: Client Access Incoming Remote Command 
> 
> I have a CLP that does a RUNRMTCMD to a PC (W2K) to start a 
> .BAT file that
> does a few things and make a call to another .BAT file on a 
> drive mapped to
> a folder on the IFS.  Everything was working fine until the 
> PC crashed and
> we had to rebuild it.  I remember having trouble getting all 
> the settings
> lined up the last time to get it to work (much trial and 
> error).  What seems
> to be happening is that the mapped drive gets disconnected 
> when we issue a
> call to the .BAT file or try to copy something to the mapped 
> drive thru the
> original .BAT file started by the incoming remote command.  I 
> know the ID
> signed on to the PC has permissions to the shared folder 
> because I can run
> the .BAT file directly, but the IRC seems to be running under 
> a different
> profile which disables the mapped drive. Does anyone know the correct
> settings in client access properties or in the W2K services 
> options to keep
> the command running under the profile of the PC user (which 
> in our case is a
> valid AS400 user profile with access to the shared folder)?
> 
> TIA
> 
> -- 
> 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.
> 
>