Secure TN5250

[jamesl@xxxxxxxxxxx]

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