× 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.


  1.  Home
  2. JAVA400-L
  3. April 2002

Secure TN5250

This is a multi-part message in MIME format...
--
To: java400-l@midrange.com
From: jamesl@hb.quik.com
X-Advert: http://emumail.com
Reply-To: jamesl@hb.quik.com
Date: Tue, 09 Apr 2002 19:37:47 EDT
X-Mailer: EMUmail
Subject: Secure TN5250

Can anybody think of a reason why a Java Telnet/TN5250 client (the one in

ThinView), known to be reliable in both normal (Port 23) and Secured (SSL on

Port 992) modes, on several different AS/400 Telnet servers, would get an
EOF
on the very first attempt to read the socket input stream after
connecting to
an AS/400 whose Telnet server, so far as I know, is identical
to the ones on
which it works fine?

If I try to connect in secured mode
to a host that isn't SSL-enabled, the
results are quite different from
this.
--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.