RE: Remote Site Cannot Connect -- MIDRANGE-L

I just got off of the site (VNC) and brought up iSeries Navigator (V5R4).
Ran the Verify Connection... and everything, including Telnet verified.
Still get the same error when trying to start the PC5250 process.

Re-installing is an option. Still waiting for the network guy to see what
he can do, if anything. I'll check the SP level.

An additional note: Until a couple of weeks ago all of our remote
connections were connecting through system-generated session ids. I
re-configured (and tested!) all sessions (local and remote) to have specific
ids. I set the QAUTOCFG value to '0' (Off) and QAUTOVRT to '0' (zilch). I
re-tested all remote sessions after that; they all worked.

Jerry C. Adams
IBM i Programmer/Analyst
More people are kicked to death by donkeys than die in aircraft accidents. -
Encyclopedia of Useless Information (Personally I don't find this useless at
all; just another reason to avoid jackasses.)
--
A&K Wholesale
Murfreesboro, TN
615-867-5070

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Jones
Sent: Thursday, March 08, 2012 2:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: Remote Site Cannot Connect

You said data transfer works. Do other aspects of Client/iSeries Access
like iNav work, i.e. everything but PC5250?

Have you considered uninstalling/reinstalling iSeries Access and making sure
the latest SP is installed?

On Thu, Mar 8, 2012 at 12:16 PM, Gary Thompson <gthompson@xxxxxxxxxxx>wrote:

He wants a double latte with whipped cream?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Thursday, March 08, 2012 11:14 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remote Site Cannot Connect

I have verified the connection from the client using the cwbping utility.
Everything, including Telnet, verifies. I have connected to our
system from the client using Telnet from within the DOS command
window; I get a signon panel.

They can run the Data Transfer process. The only difference
(port-wise) is that it uses the database port (8471) rather than the

telnet port (23).

I re-booted the PC; still no love.

I asked the network guy to check out the firewall and anything else he
could think of. He'll get around to it when he can - whatever that means.

Jerry C. Adams
IBM i Programmer/Analyst
I'd like to be a pitcher. You have four days off to play golf.
That's a dream job. -Tiger Woods
--
A&K Wholesale
Murfreesboro, TN
615-867-5070

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Thursday, March 08, 2012 11:29 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remote Site Cannot Connect

Have you run a NETSTAT *CNN to see if the remote site is connecting?
If you see the telnet connection but they never get a sign on screen,
it is on the client side or the network in between. If the telnet
connections never hits, then it is one of the other servers that they
are not reaching. Have you verified your connection settings as far
as when to look up the IP address and/or port?

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Thursday, March 08, 2012 8:57 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remote Site Cannot Connect

Kirk,

I think something was lost in either the thread or in my thoughts.
The user cannot signon at the remote site because they cannot get the
PC5250 session to connect to our system. I.e., no signon panel. So,
unless I'm losing it (another distinct possibility), the job
description is not germane.

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

--
John Jones, CISSP
--
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.