RE: Trying to get Incoming Remote command to work in XP -- MIDRANGE-L

You problem is that you're trying to run a interactive program from a service.

While Win 9x allows this, Win NT/2000/XP have more security.

You'll have to check the "Allow service to interact with desktop" to allow this to work.

Also, you'll need to send the username and password of the user currently logged into the Windows PC.

If you're using iSeries Access, and the user has a green screen session up. An easier solution is the
STRPCCMD.

HTH,
Charles

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

Thank you for looking at this.

On 18 Oct 2007 at 14:42, Wilt, (Wilt, Charles
<midrange-l@xxxxxxxxxxxx>) commented about RE: Trying to get
Incoming Remote command to work:

What command are you trying to run?

The command I am running is:
RUNRMTCMD CMD('C:\PROGRA~1\IRFANVIEW\I_VIEW32
S:\00147900000.TIF') RMTLOCNAME('xxx.xxx.xxx.xxx' *IP)
RMTUSER('SCANS') RMTPWD(AllUpperCase)

The RMTLOCNAME = a real IP address
The RMTPWD = a real password
Please remember, this is running fine in Win '98.

Thank you,

Gary Kuznitz

Charles

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Kuznitz
Sent: Thursday, October 18, 2007 2: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 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.

This e-mail transmission contains information that is

intended to be

confidential and privileged. If you receive this e-mail

and you are

not a named addressee you are hereby notified that you are not
authorized to read, print, retain, copy or disseminate this
communication without the consent of the sender and that

doing so is

prohibited and may be unlawful. Please reply to the

message immediately by informing the sender that the message
was misdirected.

After replying, please delete and otherwise erase it and any
attachments from your computer system. Your assistance in

correcting this error is appreciated.

--
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.

--
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.

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.