RE: Problem with SSL

["Justin Houchin" <justin@xxxxxxxxxxxx>]

Ok,
        I was just in NETSTAT watching port 443. It has been idle for
about 5:00 min. So I went to the web browser and hit
https://192.168.0.6.
I immediately went back to NETSTAT and did a refresh. It's GONE. It is
like as soon as I hit the port the job quit. I have checked the job
logs(WRKOUTQ) and nothing. Do you guys think it is a PTF issue? How do I
check this? I am running V4R5. Here is the connection status for https
port......
Connection identification:

   Remote host name  . . . . . . . . . . . . . . :

     Remote internet address . . . . . . . . . . :     *

     Remote port . . . . . . . . . . . . . . . . :     *

   Local host name . . . . . . . . . . . . . . . :   reliatek.com

     Local internet address  . . . . . . . . . . :     192.168.0.6

     Local port  . . . . . . . . . . . . . . . . :     https

   Associated user profile . . . . . . . . . . . :   QTMHHTTP

 TCP programming interface information:

   State . . . . . . . . . . . . . . . . . . . . :   Listen

   Connection open type  . . . . . . . . . . . . :   Passive

 Timing information:

   Idle time . . . . . . . . . . . . . . . . . . :   000:00:01.532

     Last activity date/time . . . . . . . . . . :     07/22/02
08:45:58
   Round-trip time . . . . . . . . . . . . . . . :   .000

   Round-trip variance . . . . . . . . . . . . . :   .075


Bytes out . . . . . . . . . . . . . . . . . . . :   0

   Outgoing bytes buffered . . . . . . . . . . . :     0

   User send next  . . . . . . . . . . . . . . . :     0

   Send next . . . . . . . . . . . . . . . . . . :     0

   Send unacknowledged . . . . . . . . . . . . . :     0

   Outgoing push number  . . . . . . . . . . . . :     0

   Outgoing urgency number . . . . . . . . . . . :     0

   Outgoing window number  . . . . . . . . . . . :     0

 Bytes in  . . . . . . . . . . . . . . . . . . . :   0

   Incoming bytes buffered . . . . . . . . . . . :     0

   Receive next  . . . . . . . . . . . . . . . . :     0

   User receive next . . . . . . . . . . . . . . :     0

   Incoming push number  . . . . . . . . . . . . :     0

   Incoming urgency number . . . . . . . . . . . :     0

   Incoming window number  . . . . . . . . . . . :     8192
Retransmission information:
   Total retransmissions . . . . . . . . . . . . :   0
   Current retransmissions . . . . . . . . . . . :   0
 Send window information:
   Maximum size  . . . . . . . . . . . . . . . . :   0
   Current size  . . . . . . . . . . . . . . . . :   0
   Last update . . . . . . . . . . . . . . . . . :   0
   Last update acknowledged  . . . . . . . . . . :   0
   Congestion window . . . . . . . . . . . . . . :   0
   Slow start threshold  . . . . . . . . . . . . :   0
 Precedence and security:
   Precedence  . . . . . . . . . . . . . . . . . :   0
 Initialization information:
   Maximum segment size  . . . . . . . . . . . . :   536
   Initial send sequence number  . . . . . . . . :   0
   Initial receive sequence number . . . . . . . :   0







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


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



_______________________________________________
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.