Re: Diagnosing ACS Connection issues

Hello John,

Am 17.07.2022 um 18:58 schrieb Jon Paris <jon.paris@xxxxxxxxxxxxxx>:

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.

The necessary ports are well documented by IBM. I'd try to telnet to each of the ports in question, and see if the connection opens. This is a basic test method to learn if a TCP port is accessible or not.

Unfortunately, Microsoft and Apple, as well as major Linux distros have decided that installing a telnet client by default is no longer necessary, so you need to take action before.

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.

Interesting.

From the same location users who have installed Code for IBM i can use the 5250 terminal in that to sign on.

Did you try a standalone 5250 emulator for checking? A demo version of Mocha will do. Try with and without TLS, on the appropriate ports, and let us know the outcome.

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.

I expect a (future) programmer to not be a pussy about text terminals. Most of them aren't biased in a similar way in the Linux world, and IBM i *is* a TUI platform at its heart, just like Linux. I don't know why this double-standards thinking exists. When it comes down to "basics" the interesting question is: what are basics, and what is not? I'm sure this is a highly subjective topic. Just saying.

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

See above.

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

I don't know Code for I, so I can't tell.

:wq! PoC