RE: Mocha TN5250 connects but not Client Access

If all you are using is telnet then you don't need all those ports open,
except for the ones that authenticate the user and check the license status.


So, obviously 23/992, but also 8470/9470 and 8476/9476 for license
management and signon verification. The same is true for the Access
Connections.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Dearing
Sent: Sunday, August 09, 2015 10:30 AM
To: Midrange Systems Technical Discussion
Subject: Re: Mocha TN5250 connects but not Client Access

On Sun, Aug 9, 2015 at 10:54 AM midrange <franz9000@xxxxxxxxx> wrote:

As usual, ibm constantly changing the website makes it difficult to
find the list of ports Required - here is a 2014 version

http://www-01.ibm.com/support/docview.wss?uid=nas8N1019667

I will guarantee Mocha does not have same requirements

I don't understand why Client Access would need any ports besides the telnet
port to give you a greenscreen session. I get that client access is a lot
more than an implementation of the telnet 5250 protocol, while mochasoft,
tn5250, tn5250j, x5250, etc are just greenscreen (and maybe
printer) clients. However, if I was a network admin in a situation where I
had to give an office/factory/warehouse full of people greenscreen access to
some RPG app that didn't have a web front end, I'm not going to want any
subnets besides the ones IT uses to connect to have access to all that extra
functionality. Principle of least privilege. That basically means that I'm
going to prefer a third party 5250 client for security purposes.
--
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.