× 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. MIDRANGE-L
  3. June 2015

RE: SSL Telnet Configuration problems.

Mike,

I had similar issues.
Now working.
Problem was that my PC did not have the correct CA (Certificate Authorities) to go along with our wild card certificate on our iSeries which resides in DCM.
Had to use IBM Key Management Utility to fix/repair/import the CA on my PC.

I'll put together some notes for the resolution, along with notes from IBM PMR.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Monday, June 22, 2015 3:20 PM
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
Subject: SSL Telnet Configuration problems.

I have been trying on and off for a while to get SSL for Telnet configured. Every time I run into a brick wall and give up .
So I decided to give it another attempt. I followed a document that Rich at Kisco has on his blog and thought I had it.
However, when I try to start my 5250 session, it immediately fails and the flashing error code is 420-The partner closed the socket before the protocol completed..

After digging around I found that you can get to a job log for QTVTELNET in Iseries Navigator and I managed to find this with an error of
CPDBC82- No certificate is available for SSL.

If I click on Security Information under the Communication menu on my session, under the Connection tab, I see my Certificate I created. This shows an expiration in the year 2020.

Anybody know what I might be missing?

Thanks

Mike
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.
--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.