|
We use client access for tn5250 emulation across campus but do not install
any other part of client access. A very few people get the file transfer
also. You don't need to install all the functions of the fat client if you
don't need it.
Sent from my iPad
On Aug 9, 2015, at 3:59 PM, midrange <franz9000@xxxxxxxxx> wrote:old.
Welcome to fat client versus thin client, an argument that is decades
The extra features in CA are the result of customers requesting thesees.
functions.
Btw-fewer ports used (by itself) does not = better security.
CA gives admins the tools to secure various features and what the user
telnet
Mocha fills a need for some customers as well.
Jim
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Dearing
Sent: Sunday, August 09, 2015 11: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
port to give you a greenscreen session. I get that client access is a lotI
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
had to give an office/factory/warehouse full of people greenscreenaccess to
some RPG app that didn't have a web front end, I'm not going to want anyextra
subnets besides the ones IT uses to connect to have access to all that
functionality. Principle of least privilege. That basically means thatI'm
going to prefer a third party 5250 client for security purposes.list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,unsubscribe,
or change list options,list
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
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.