Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SSL Telnet from one AS/400 to a second AS/400

243 views
Skip to first unread message

soma1...@yahoo.com

unread,
Mar 6, 2008, 5:27:15 PM3/6/08
to
Is it possible to do SSL telnet from one AS/400 to another AS/400?

Our users sign on to the local AS/400 with Personal Communications.
Then they select a menu option that does a telnet in a CLP. Looking
to change this to a secure connection.

Would look like this...
TELNET RMTSYS(CUSTOMER) PORT(992)

Cert Store and certificates are defined and assigned to the telnet and
FTP server on the customer AS/400. I receive the following messages
in QTVTELNET.
"A remote host did not respond within the timeout period."
"SSL Handshake exceeded timeout limit for client...".

I am able to do secure FTP.
FTP RMTSYS(CUSTOMER) PORT(990)

Thanks!

jacko

unread,
Mar 7, 2008, 7:32:30 AM3/7/08
to

Do you have a CPF message or a return code??

This link might help once loaded look for SSL return codes.

http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/rzaiw/rzaiw.pdf

soma1...@yahoo.com

unread,
Mar 7, 2008, 11:43:00 AM3/7/08
to
> http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/rzaiw/rzaiw.pdf- Hide quoted text -
>
> - Show quoted text -

I opened up a case with IBM after posting the original question and
they stated the only way you can do this is with a PC client. There's
no support for a secure telnet client on the iSeries and there are no
plans to implement one.

Davide Grandi

unread,
Mar 9, 2008, 5:52:05 PM3/9/08
to
<soma1...@yahoo.com> wrote:

> On Mar 7, 7:32 am, jacko <jkings...@cityofnorthport.com> wrote:

...


> I opened up a case with IBM after posting the original question and
> they stated the only way you can do this is with a PC client. There's
> no support for a secure telnet client on the iSeries and there are no
> plans to implement one.

Maybe it's a bit akward but you could run a (local) ssh tunnel server on
your as that remap a local port (on 127.0.0.1) to a remote ssh port.

So you (plain) TELNET on a local port and the ssh tunnel connects it to
the remote as/400.

The 'cons' is that, AFAIK, the tunnel server destination is fixed or, at
best, require some dynamic reconfiguration in order to change the
destination address.

Best regards,

Davide
--
Ing. Davide Grandi
davide...@mclink.it

0 new messages