We started seeing that same error when we began rolling out XP workstations
and connecting to a 820 running V5R2. This was a little different in that
it was a client simply starting a session using iSeries Access for Windows,
but it did seem to be random. We were thinking it might be a DNS issue and
our help desk techs starting changing the connection properties to use IP
address instead of the host name and it seemed to improve. There were other
variables as well, we had received a bad batch of Gateway workstations.
I haven't heard of new instances in a year or so. Since then we also
deployed a different model of Gateways and for the last six months or so
have been deploying HP units. We also migrated to a 515 running V5R4 but
I'd be willing to bet that the images they're laying down on the
workstations are using IP address to connect.
Kevin Brake, MSSE
Applications and Business Analyst - Enterprise Solutions
Information & Technology Services
City of Goodyear
190 N. Litchfield Rd.
Goodyear, AZ 85338
Sent by: <MIDRANGE-L@xxxxxxxxxxxx>
Remote Port Failing
Please respond to
We are at V5R4 with the latest service pack for Client Access. This is
one of those problems that doesn't happen all the time, but it seems to
be happening with greater frequency. We have remote users that connect
to a web site that resides on our windows 2003 server. We then connect
to our System i using ODBC. The error message that is being displayed
more frequently is "CLIENT ACCESS CWBCO1011 - REMOTE PORT COULD NOT BE
RESOLVED." We tell the user to try again, and sometimes the connection
is made and other times it takes several tries.
I've checked out answers to this message and they all point to releases
prior to V4R2. Do you have some suggestions or can you point me in a
Any assistance would be appreciated.
S. C. Commission on Higher Education
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives