As a back door solution, give that user a copy of Mochasoft TN5250. That's
what I use when there's a cranky/clueless network admin.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Monday, March 05, 2012 2:23 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remote Site Cannot Connect
I saw the first two links, too.
There is a firewall (AVG) running, but the system admin gets rather, shall
we say, irked if I even look at his settings, and he ain't available right
now. On the other hand, the remote site (store) could connect last Friday.
I was able to connect via telnet from a DOS command window.
I ran the History Log. In addition to CWBCO1003, it showed CWBCO1011
(Remote port could not be resolved). It said something about using iSeries
Navigator to check the port, which I did, but I saw nothing in the
'Connection' tab about a bloody port (still could be the one "good" eye is
I guess I'll get with the admin tomorrow (too late in the day to hassle with
him) about AVG and other possibilities. Though, theoretically, he's told me
that all of the PCs are set-up the same way.
Jerry C. Adams
IBM i Programmer/Analyst
You can never plan the future by the past. -Edmund Burke
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, March 05, 2012 12:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: Remote Site Cannot Connect
My first google hit was
I looked at CWBCO1003 and 4 (3 suggests that also). With the reference code
you've given, it suggests that you do what you did: ping, etc.
Googling on both the CWBCO1003 (notice one letter o and two number zeros?).
and 10013 also shows this
possible firewall issue? See also
Try using telnet from DOS and see if that gets there?