Re: I am trying to get RUNRMTCMD running -- MIDRANGE-L

The reason for the "other" ports (hope I state this correctly)
RUNRMTCMD is not a Client Access cmd. It is for remote command
execution from as400 to either sna or ip systems. For ip, it uses rexec, an
ip cmd
who "well-known" port is 512. (see cfgtcp menu, option 21 Related Tables,
then opt 1 for service table entries for all the ports used by the 400 (not
by CA
on a pc). I can use the same runrmtcmd to a NT not using Client Access and
it
would work the same way. The 8475 port in CA doc is when CA starts the
rmtcmd
(sending the remote cmd to the as/400) from the apar:
SERVER:  Remote Command
DEFAULT PORT:  8475 (9475)
DESCRIPTION:  Remote command server is used to send commands
  from a PC to an AS/400 and for program calls

the port 5788 "may be" the negotiated port after talking to the "well known"
port. If you do a NETSTAT cmd on AS400, you will see all your Client Access
connections. They first connect on well known port 23 (telnet) and then are
re-directed
to a randomly assigned port. I am guessing remote command works the same.
Your router/firewall allows port 23 & any job initiated thru 23 & redirected
to another port.
<btw-not a router expert>
hth
jim

----- Original Message -----
From: "Gary Kuznitz" <docfxit@theoffice.la>
To: <midrange-l@midrange.com>
Sent: Wednesday, April 10, 2002 10:11 PM
Subject: Re: I am trying to get RUNRMTCMD running


> Hi Vernon,
>
> I figured out the problem.  I had put an entry in a router for port 512.
> Evidently I must have forgot to save the entry and there must have been a
> power failure.  The router comes back up by itself but it lost the entry I
put in.
> What I don't understand is why the AS/400 sent out a remote command with
> a destination port of 5788.  I also don't understand why either port 512
or port
> 5788 is not on the "TCP/IP Ports Required for Client Access" web page at:
> http://www-
> 912.ibm.com/s_dir/slkbase.NSF/fd9885170ed46f758625680b00020373/acc1
> 2fda96496e4b8625668f007ab75f?OpenDocument
>
> Acording to that page the Remote Command is using port 8475.  When I
> capture the TCP packets 8475 is never used.  I have proved it is actually
using
> port 512.
>
> Thanks,
>
> Gary
>
> Comments below...
>
> On 10 Apr 2002 at 14:39, Vernon Hamberg wrote:
>
> > Need details.
> >
> > Is it fialing?
>
> Yes.  I get an error saying:
> A remote host refused an attempted connect operation.
> Command did not complete successfully.
>
> > What rexecd are you using? CAE Incoming remote command?
> Yes.  CWBRXD
>
> > Is this an *IP or *SNA conneciton?
> *IP
>
>
>
> > At 11:37 AM 4/10/02 -0700, you wrote:
> > >Hi,
> > >
> > >I am trying to get RUNRMTCMD running.  I see when I call the program
> > >it's sending it out from port 512 on the AS/400 running v4r4 to a
> > >destination port of 5788.  When I run the program on the PC it
> > >listens on port exec which is really 512 running CA v5r1.
> > >
> > >Does anyone know how to match these ports up?
> > >
> > >TIA,
> > >
> > >Gary
> > >_______________________________________________
> > >This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> > >mailing list To post a message email: MIDRANGE-L@midrange.com To
> > >subscribe, unsubscribe, or change list options, visit:
> > >http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email:
> > >MIDRANGE-L-request@midrange.com Before posting, please take a moment
> > >to review the archives at http://archive.midrange.com/midrange-l.
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list To post a message email: MIDRANGE-L@midrange.com To subscribe,
> > unsubscribe, or change list options, visit:
> > http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email:
> > MIDRANGE-L-request@midrange.com Before posting, please take a moment
> > to review the archives at http://archive.midrange.com/midrange-l.
> >
> >
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>