RE: Secure TN5250

My only guess... You're trying to read the socket before the host has sent
any, or the host is still establishing the connection.

To test this, put a delay of like 5 seconds after you establish connection
before you read.  This is just to test if this is what is happening, not the
final solution (I would hope, but sometimes it is).

Regards,

Jim Langston

-----Original Message-----
From: jamesl@hb.quik.com [mailto:jamesl@hb.quik.com]
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?