|
Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your IT Department
Do you mean the Verify Connection Don?
If so I believe they have yes - but as I stated in my original post the base connection (which I think is all that tests) appears to work. I will ask them to check again though.
Jon P
On Jul 17, 2022, at 5:37 PM, Don Brown via MIDRANGE-L<midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Have you run the test connection from within ACS to see what fails ?
This should narrow it down.
Don
From: "Jon Paris"<jon.paris@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 18/07/2022 02:59 AM
Subject: Diagnosing ACS Connection issues
Sent by: "MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
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
athttps://archive.midrange.com/midrange-l.
Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:https://amazon.midrange.com
--
This email has been scanned for computer viruses. Although MSD has taken reasonable precautions to ensure no viruses are present in this email, MSD cannot accept responsibility for any loss or damage arising from the use of this email or attachments..
--
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
athttps://archive.midrange.com/midrange-l.
Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.