× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Adam,

Just to clarify your final statement, is the QIBM_QTV_TELNET_CLIENT
application only for telnet from another system?

No. QIBM_QTV_TELNET_CLIENT is the Telnet *CLIENT*. It's not for telnets from another system... it's for telnets *TO* another system via the TELNET CL command.


In other words, does Client Access use this?

No. Client Access uses the telnet *SERVER*, not the client. Client Access is an example of "telnet from another system". (Whereas the telnet client is for telnetting *to* another system.)


And no, we wouldn't want to secure telnet from another system, the
only traffic using this is from other LPARs on the same system and is
all over the internal VLAN anyway.

As far as I know, LPARs are considered "other systems". Each one looks and feels like a different computer. I understand what you're saying, they're all running on the same physical hardware, you think of them as the same computer.

However, software generally does not. They appear to be completely different computers to most (if not all) software.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.