RUNRMTCMD

[Gimli]

Hallo an Alle,

kann mir bitte mal jemand bei dem Befehl: RUNRMTCMD helfen ?
Ich will von einer AS/400 V4R5M0 auf einen PC-Server zugreifen und einen RMTCMD absetzen. Ich erhalte dabei die Fehlermeldung: CPF91CC Ein ferner Host lehnte einen Verbindungsversuch ab.
Welche Voraussetzungen müssen auf dem Zielsystem (ist ein WIN2K-Server) existieren, damit der Zugriff erfolgreich ist ?

Ich bin für jeden Tipp dankbar.
Vielen Dank für Eure Hilfe, Marc

[JonnyRico]

Hi,

der Ziel-PC muss das Programm CWBXRD.exe gestartet haben. Die Datei befindet sich bei Win9x im Verzeichnis \Windows\System. Ich vermute das es dann bei Win2k unter \Winnt\System32 steht. Wenn du das Programm gestartet hast, kann es minimiert werden und ein RMTCMD abgesetzt werden.

mfg

Sascha

------------------------------

Hi besser spät als nie aber ich habe noch mal nachgesehen und jetzt brauche ich den Befehl nämlich auch unter WinXP. Also dort gibt es einen Dienst "Ferner Befehl für Client Access" (CA 5.1) Dieser muss gestartet sein und dann sollte das klappen. Die oben beschriebene *.EXE Datei gibt es nicht mehr.

[TARASIK]

Hallo,
vielleicht ist auch dies hilfreich:

Functional Area: Client Access
Subfunctional Area: Incoming Remote Command/Remote Command
Sub-Subfunctional Area: General
OS/400 Release: ALL
Product: CA400 WIN95 NETSOFT (5763XD1NS)
CA400 WIN 95 (5763XD100)
Product Release: N/A


__________________________________________________ ________________

Document Title
RUNRMTCMD Fails with MCH3401 Cannot Resolve to Object CMINIT

Document Description

Using the RUNRMTCMD command on a PC connected with SNA may fail with PWS000D (for CISC) or with
CPF91CC (on a RISC) if QSYS2 is not part of the library list. The problem occurs only when using a SNA connection such as the NetSoft Router or Microsoft SNA Server 2.11.

The OS/400 joblog shows MCH3401 - Cannot resolve to object CMINIT. Type and Subtype X'0201' Authority X'0000'.

For SNA connections, the RUNRMTCMD command uses CPIC APIs (such as CMINIT) to communicate with the remote host (in this case, your PC). CMINIT is located in QSYS2. If QSYS2 is not part of your system library list, the command cannot be run. To circumvent this problem, on the OS/400 command line type the following:

WRKSYSVAL QSYSLIBL

Select Option 2 to Change. Add QSYS2 in the library list.

gruss TARASIK

[Gimli]

<BLOCKQUOTE><font size="1" face="Verdana, Arial">Zitat:</font><HR>Original erstellt von JonnyRico:
Hi,

der Ziel-PC muss das Programm CWBXRD.exe gestartet haben. Die Datei befindet sich bei Win9x im Verzeichnis \Windows\System. Ich vermute das es dann bei Win2k unter \Winnt\System32 steht. Wenn du das Programm gestartet hast, kann es minimiert werden und ein RMTCMD abgesetzt werden.

mfg

Sascha[/quote]

Hallo Sascha. danke für Deine schnelle Antwort, aber wo bekomme ich das Programm denn her, wenn es nicht auf dem Server ist ?

[Gimli]

<BLOCKQUOTE><font size="1" face="Verdana, Arial">Zitat:</font><HR>Original erstellt von TARASIK:
Hallo,
vielleicht ist auch dies hilfreich:

Functional Area: Client Access
Subfunctional Area: Incoming Remote Command/Remote Command
Sub-Subfunctional Area: General
OS/400 Release: ALL
Product: CA400 WIN95 NETSOFT (5763XD1NS)
CA400 WIN 95 (5763XD100)
Product Release: N/A


__________________________________________________ ________________

Document Title
RUNRMTCMD Fails with MCH3401 Cannot Resolve to Object CMINIT

Document Description

Using the RUNRMTCMD command on a PC connected with SNA may fail with PWS000D (for CISC) or with
CPF91CC (on a RISC) if QSYS2 is not part of the library list. The problem occurs only when using a SNA connection such as the NetSoft Router or Microsoft SNA Server 2.11.

The OS/400 joblog shows MCH3401 - Cannot resolve to object CMINIT. Type and Subtype X'0201' Authority X'0000'.

For SNA connections, the RUNRMTCMD command uses CPIC APIs (such as CMINIT) to communicate with the remote host (in this case, your PC). CMINIT is located in QSYS2. If QSYS2 is not part of your system library list, the command cannot be run. To circumvent this problem, on the OS/400 command line type the following:

WRKSYSVAL QSYSLIBL

Select Option 2 to Change. Add QSYS2 in the library list.

gruss TARASIK[/quote]


Hallo Tarasik,

auch Dir vielen Dank für Deine schnelle Antwort, leider will ich eine TCP/IP Verbindung benutzen und habe die QSYS2 bereits in der Biliotheksliste.

[AndreasH]

Hallo Gimli,
bei Win2K muss unter Systemsteuerung / Dienste der entsprechende Dienst gestartet werden. Wie der genau für Remote Commands heisst hab ich nicht im Kopf, aber allgemein sind die Dienstnamen bei Win2K ziemlich sprechend.
Gruß
Andreas

[Gimli]

Hallo Andreas, auch Dir herzlichen Dank für Deine schnelle Antwort, aber die Dienste sind alle gestartet.

[TARASIK]

Hallo,
einen habe ich noch:

Document Information
Document Number: 8794700
Functional Area: Client Access
Subfunctional Area: Incoming Remote Command/Remote Command
Sub-Subfunctional Area: General
OS/400 Release: ALL
Product: CA400 WIN 95 (5763XD100)
Product Release: N/A


__________________________________________________ ________________

Document Title
MSGCPE3425 A Remote Host Refused an Attempted Connect Operation on RUNRMTCMD

Document Description

When issuing a RUNRMTCMD to a TCP/IP-attached PC, the error CPE3425, A remote host refused an attempted connect operation, is returned. The message implies that there was no daemon listening at that IP address on that port to accept the incoming request. Either the IP address is wrong or the daemon is not running. Security errors will return different error messages.

Resolution:

Verify that you are using the correct IP address/PC name. PING the PC using that same name or IP address. If the PING fails, you are not using the correct address.

Windows NT o Verify that CWBRXD (the incoming remote command daemon) is active.
o Press CTL-ALT-DEL and select task manager.
o Select the Processes tab.
o Look for CWBRXD in the list. If not found, then start it as described below.
o Start the Client Access Remote Command Service as documented in the Client Access for Windows 95/NT - Setup manual (SC41-3512). To link to the Client Access for Windows 95/NT - Setup manual, click below:
http://AS400BKS.rochester.ibm.com:80...CN03/CCONTENTS

Note: The above URL is case sensitive. Uppercase characters must be used as shown to reach the updated manual.

The Implementation section from the manual follows:

6.3.2.1 Implementation

To process the incoming remote command in a TCP/IP environment, use the following steps: 1 Ensure that you have correctly configured TCP/IP.

___ Windows 95 __________________________________________________ ___
| |
| |
| 1. Click on the Client Access Properties icon and go to the |
| Remote Command tab page as shown in Figure 28-1 in |
| topic 6.3.2. |
| |
| |
| You can authorize who is able to send commands to your PC by |
| specifying system names, userids and passwords. The character |
| * can be used as a wildcard for any of these fields. Be aware |
| that if someone has authority to send commands to your PC, |
| then they can run any command on your PC, including FORMAT, |
| DELETE and so on. |
| |
| |
| | Note: If you have disabled password caching under Windows |
| 95, you must explicitly configure Client Access for |
| Windows 95 for incoming commands. |
| |
| |
| |
| |
| 2. Start Incoming Remote Command Daemon by clicking on Start-Run, |
| | and then type CWBRXD. A DOS session running CWBRXD is now |
| | active on your PC. |
| |
| |
| Alternatively, you can create an icon for CWBRXD and have it |
| minimized when you run it. To create the icon, use the |
| following steps: |
| |
| |
| |
| a. Go to any empty space on your desktop and click on the |
| right mouse button. Choose New, and then click on |
| Shortcut. |
| |
| |
| b. Supply the command line as: |
| |
| |
| C:\windows\cwbrxd.exe |
| |
| |
| |
| |
| |
| c. Give the icon a name on the next panel, for example, |
| Receive Remote Commands. |
| |
| |
| d. Click on Finish. |
| |
| |
| e. Click the right mouse button on the icon you just created. |
| |
| |
| f. Click on Properties. |
| |
| |
| g. Click on the Shortcut tab. |
| |
| |
| | h. Go to the Run prompt and choose Minimized from the list. |
| |
| |
| |
| |
| | Tip: If you want to enable incoming commands at all times on |
| your PC, you can put the icon that starts the daemon in |
| | the Windows 95 Startup folder. Alternately, place a |
| | check in the box marked "Automatically Start incoming |
| | remote command" on the Remote Command tab of Client |
| | Access properties. |
| |
| |
| |
| |
|_________________________________________________ ___________________|


2 Go to any AS/400e or iSeries terminal display and activate commands for the PC. Refer to OS/400 RUNRMTCMD Command in topic 6.3.1 for some examples.

Note: We can also run the REXEC from VM, for example:

REXEC PCHOSTA CALC

You do not need to have an AS/400e or iSeries connection started to be able to receive incoming commands. A correct TCP/IP configuration is sufficient.
3 To terminate Incoming Remote Command Daemon:

| ___ Windows NT __________________________________________________ ___
| |
| | Simply stop the Client Access Remote Command service from the |
| | Service program found in the Windows NT Control Panel. |
| |
|_________________________________________________ ___________________|


| ___ Windows 95 __________________________________________________ ___
| |
| | Click on Start-Run, and then type CWBRXDSD. An MS-DOS Session |
| | running CWBRXDSD starts and terminates the session you started in |
| | step 2. You must use the CWBRXDSD command to stop the CWBRXD DOS |
| session. Do not shut down the CWBRXD DOS session by |
| double-clicking the top left hand corner or clicking the "cross" |
| at the top right hand corner. Unexpected results could happen if |
| you do so. |
| |
| |
| Alternatively, you can create an icon for CWBRXDSD and have it |
| minimized when you run it. To create the icon, use the following |
| steps: |
| |
| |
| |
| 1. Go to any empty space on your desktop and click on the right |
| mouse button. Choose New, and then click on Shortcut. |
| |
| |
| 2. Supply the command line as: |
| |
| |
| C:\windows\cwbrxdsd.exe |
| |
| |
| |
| 3. Give the icon an name at the next panel, for example, End |
| Receive Remote Cmds. |
| |
| |
| 4. Click on Finish. |
| |
| |
| 5. Click the right mouse button on the icon you just created. |
| |
| |
| 6. Click on Properties. |
| |
| |
| 7. Click on the Shortcut tab. |
| |
| |
| | 8. Go to the Run prompt and choose Minimized from the list. |
| |
| |
| |
|_________________________________________________ ___________________|


___ Note __________________________________________________ _________
| |
| You may want to terminate Incoming Remote Command Daemon to |
| prohibit anyone from issuing commands to your PC remotely. If |
| not, anyone who is authorized can issue a command to your PC and |
| do whatever they want on your PC. |
| |
|_________________________________________________ ___________________|


⌐ Copyright IBM Corp. 1995, 1997

IBM BookManager« BookServer Copyright 1989, 1996 IBM Corporation. All rights reserved.


Windows 95 o Verify that CWBRXD (the incoming remote command daemon) is active.
o Press CTL-ALT-DEL.
o Look for CWBRXD in the task list. If not found, then start it as described below.
o Start the Client Access Remote Command Service as documented in the Client Access for Windows 95/NT - Setup manual (SC41-3512). (See above.)

gruss TARASIK