Are you using a self-signed certificate for Telnet on your IBM i? If so,
you probably need to import the CA from your self-signed certificate into
your PC so it trusts it.


On Wed, Sep 16, 2015 at 10:42 AM, Mike Cunningham <mike.cunningham@xxxxxxx>

We started testing software with Windows 10 and we have not been able to
get either IBM I Client Access product to work or the newer IBM I Access
Client (java based) product to work. Both report an SSL handshake issue. I
did see a post that implied that IBM will not be supporting the older
Client Access product after Windows 8 and are shifting to the all java I
Access Client instead. But I have tried both and both report an issue with
SSL. We do have our iSeries configured to only use TLS and only use SSL and
we do not allow any unsecured telnet. Does anyone have either of these
products working under Windows 10.

Errors in I Access Client are MSGSSL004 and MSGSSL007
Errors in I Client Access are CWB01034 code 25202

Free TN5250 product for Windows does work for SSL telnet connection


Mike Cunningham
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

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-2022 by 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.