In control panel, iSeries Access, Incoming remote command, we have it
set as Command Mode Detached, and Run as system checked. All others are
unchecked. This is on a windows 2003 server, which is basically the
same as XP Pro. Check out those settings and see if it helps.

Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----

Thank you for looking at this.

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