Re: Diagnosing ACS Connection issues -- MIDRANGE-L

It is actually my system they are connecting to and we have no restrictions, no need to provide names, etc. we have had similar issues in the past with other customers and it always came down to firewall issues on thinner side - but this client is insisting that this is not the case.

Jon P.

On Jul 17, 2022, at 1:49 PM, Steve McKay <samckay1@xxxxxxxxx> wrote:

Jon -

Check the QAUTOVRT and QAUTOCFG system values.

Is the ACS config set for unique workstations? On the 5250 session under
configuration enter ‘wsname*=‘.

On Sun, Jul 17, 2022 at 11:59 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

I am running a series of remote classes for a client and they are unable
to connect via ACS.

I am convinced that it is a firewall issue at their end and they are
equally convinced that it is not.

Here's the scenario.

Fire up ACS and it asks for user Id and pw. Connection appears to be made
and green screen appears but never connects.

From the same location users who have installed Code for IBM i can use the
5250 terminal in that to sign on. Trouble is that terminal is (to be
polite) pretty horrible and not really practical to work with for a group
trying to learn the basics of IBM i.

Any suggestions on what tooling I can ask them to run to attempt to
identify the blockage?

Is there another terminal option that would utilize the same connection as
Code for IBM i (assumedly SSH) as its communication vehicle?

I was hoping that their firewall restriction might be related to only
permitting secure connection ports so I've tried to get my ACS running with
SSL but sadly that was a miserable failure and the error messages make so
sense to me so I've abandoned even trying that for now.

Any thoughts ?

Jon P.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
Thanks,

Steve McKay
205-585-8424
samckay1@xxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com