RE: CA remote command server port

Thanks Todd.  I'll be giving it a try.  Chris Bipes made a similar
suggestion.  I thought that the remote port choices within the client-side
configuration just determined the means by which the software translates a
request such as remote command call to a port number.  Ultimately, the only
way in to the server for that type of function is supposed to be the port
number specifically defined to the service table.  One way or another it's
supposed to pass port 8475.  Maybe the request could pass generically
through our VPN and resolve to port 8475 on the server.  (I think I might
have just made that up.)

-----Original Message-----
From: Todd kidwell [mailto:Todd.kidwell@3cc.co.wayne.mi.us]
Sent: Monday, November 25, 2002 11:20 AM
To: midrange-l@midrange.com
Subject: RE: CA remote command server port


Jim,

I'm not sure I understand the problem, but I thought I would offer a
suggestion.  A few months ago I ran into a problem with port restrictions.
After being down for a weekend, one of the IBM techs showed me a work-around
for avoiding the host servers.

If you go into Operations Navigator and right-click on your system, you will
get a drop-down menu with several options.  Choose the one that says
"Properties".  From the Properties window, select the "Connection" tab.  At
the bottom of the window is a drop-down box titled "Where to lookup remote
port:".  Change the value from "Server" to "Local".

This works with CA Express 4.4 and 4.5.  I don't know if it works with
anything else.

HTH,

Todd