10-22-2002, 06:16 AM
I am at V5R2. My RUNRMTCMD is failing with the message "A remote host refused an attempted connect operation." When I go into Client Access - Administration System and try to add system and user, I get an error message "The system Specified is not an Administration System" Can anyone tell me what the problem could be? Thanks.
10-22-2002, 06:16 AM
(Note: In my response below, where "Client Access" is used, if the client version is V5R2 or later, replace this with "iSeries Access" or "iSeries Access for Windows.") First, the explanation and fix. The message "A remote host refused an attempted connect operation" is a TCP/IP-specific message that you might see when running any command (in general) that uses TCP/IP to connect to another system. It means that the system you specified to run the command on (i.e. the PC) rejected the connect attempt. In this case, RUNRMTCMD sent a message to the PC saying "I want to talk to the Incoming Remote Command server," and the PC said "Sorry, it's not available right now" and rejected the request. Evidently the Incoming Remote Command server program on the PC is not running. (In the case of Windows 9x/Me, this is cwbrxd.exe; in the case of Windows NT/2k/XP, this is the Client Access Remote Command service.) To find out exactly how to start this server program on the PC, read the pertinent info in the User's Guide installed with iSeries Access for Windows. Secondly, your post pointed out a point of confusion. Registering users with the Administration system is related to "Application Administration," a feature of Client Access that allows you to restrict specific users from performing various Client Access tasks on various host systems. It has nothing to do with Incoming Remote Command (RUNRMTCMD on the host side). If the PC you wish to send a command to using RUNRMTCMD is running Windows 9x/Me, then (besides running cwbrxd.exe), you do need to set-up security entries to allow Incoming Remote Command requests to be run on that PC. To do this, open Client Access Properties from the Control Panel, and select the Incoming Remote Command tab -- then add security entry(s) there as needed. If the PC is running Windows NT/2k/XP, the security mechanism used to authenticate users and allow command requests to be run is simply the Windows security/logon mechanism. Any user that can logon locally to the PC may run a command on that PC using RUNRMTCMD (once the Client Access Remote Command service is started), as long as their username and password specified on RUNRMTCMD is correct for that PC.
Powered by vBulletin® Version 4.1.5 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.