If you get to the point where you want to put the Client Access approach to
rest I have another method you could try. I just wrote an article for
MCPressOnline showing how to make RPG talk to a desktop PC that will be
published in the next issue of "MC|RPGDeveloper Online"
(http://www.mcpressonline.com/mc/publications/MCDev).

Basically it entails installing a small Java "daemon" on each PC you want to
communicate with, and the Java app simply waits for Data Queue entries to
process and execute. ON the server side there is an RPG component that
simply writes a PC command (like the one you reference) to the Data Queue -
pretty straight forward. In a future article I hope to show how to nicely
package a Java-to-iSeries-communicating-application so it can simply be
downloaded and installed by clicking a link within a page being served by
Apache running on the i5 (digressing...).

Looks like the next edition is due on Oct 31st so hopefully your process can
wait that long if you wish to go this route. All the source is included.

HTH,
Aaron Bartell
http://mowyourlawn.com


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Kuznitz
Sent: Thursday, October 18, 2007 1:27 PM
To: Midrange Systems Technical Discussion
Subject: Trying to get Incoming Remote command to work in XP

I'm running into a problem getting the Incoming Remote command to work in
XP.

I have it working fine in '98 so I know the AS/400 side is setup correctly.

I have tested port 512 with Port Detective and it says it's blocked. Port
Detective test the port from the PC to the outside world. I have put an
exception in the windows firewall to allow port 512 and to allow the program

cwbrxd.exe. I have also turned off the windows firewall.

I have turned off the Client Access Express Remote Command service and
checked
to see if any other programs were using port 512 with a program called
Active
Ports. It shows nothing is using port 512.

I have checked with the ISP Road Runner in Southern California and they say
they don't block any ports.

In XP sp2 I have setup a user with Administrative Rights that the Remote
Command is using with the password in all upper case.

In services for "Client Access Express Remote Command I have set the Log On
to
use the same Account as the User that the remote command is using with the
password in all upper case.

I have added the user in Control Panel, Administrative Tools, Local Security

Policy, User Rights Assignment:

Act as part of the operating system
Create a token object
Create permanent shared objects
Increase scheduling priority
Log on as a batch job
Log on as a service
Log on locally
Replace a process level token

I have taken the remote command and run it from a command line with the same

user. It runs fine.

I have tried logging in under the same user and running the Remote Command.
It
hangs.

I am not getting any error in V4r4 running Client Access Express V5r1 with
the
latest service pack. The system is waiting on a timed wait.

I can understand it not connecting with port 512 blocked. I can't
understand
what is blocking port 512 unless Road Runner isn't giving me the true scoop.


I have also tried this on a different ISP - Megapath.net. Port 512 is still

blocked.

What else could be blocking port 512 in XP?

Thank you,

Gary Kuznitz



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].