On Mon, 9 Nov 2015, James Rich wrote:

I've got a bit of a puzzle here. Existing SSL telnet connections work fine, but trying to start a new SSL telnet connection either doesn't work at all, or in one case, took 20 minutes to connect. I've checked that the certificates are ok and both the CA certificate and the server certificate are ok until next year. Firewall isn't the problem as this is occurring over the LAN as well, plus as I mentioned, existing SSL telnet connections are working just fine. Any ideas where I should look?

A little more information on this puzzle. Suddenly SSL connections are working, with no apparent changes at all. Nothing was restarted, no error messages ever logged. But for nearly 24 hours new SSL connections either wouldn't start at all or would be extremely slow to start. Doing a NETSTAT revealed that the iSeries was receiving bytes from the client but showed zero bytes sent. We are still scratching our heads over this. We don't know why it stopped working or why it suddenly started working. The one oddity is that many of the new connections are now coming in under QCTL instead of QINTER. Any more thoughts?

James Rich

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-2019 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].