RE: Problem with SSL

["Justin Houchin" <justin@xxxxxxxxxxxx>]

>>>>Can you get a telnet session on port 992?
No, I did a netstat *cnn and there is no port 992 listening. But port
443 is listening.

>>>>If you do not resolve, you may want to start looking at job logs for
the
socket refusal errors, to pin down what is failing.
Are there any particular job logs I should check?


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com] On Behalf Of Mark Villa
Sent: Monday, July 22, 2002 8:26 AM
To: midrange-l@midrange.com
Subject: RE: Problem with SSL


~~~to install
~~~the Digital Certicate Manager, Crytographic Support, and the
~~~Crytographic Access Provider 128bit. When I got done installing them,
~~~the Crytographic Access Privider 128bit showed *INSTALLED while the
~~~other to showed *COMPATIBLE. Could this be a problem?
~~~

Justin,
The indicator: *COMPATIBLE is normal
it will say *ERROR if not okay.
SSL is pretty tricky.
Can you get a telnet session on port 992?
I would not trust an install until successful secure connect on some
port.
The other guys are right, you will see the prerequisite port listening
using
NETSTAT *CNN command.
If you do not resolve, you may want to start looking at job logs for the
socket refusal errors, to pin down what is failing.
I am no expert at it, but the logs told me more than once that I was not
trusted, because I did something out of step or it failed to save my
certificate settings, etc.

Also, can you turn your lock on and connect via Client Access?
The older the OS/400 version the more PTF's are needed.
My experience is with internal trust so I do not know how 3rd party
certificates may fail in this context.


Hope this is helpful,

Mark Villa in Charleston SC

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.