RE: Firewall and SSL blues

Here is the solution:

It had nothing to do with the firewall.  It had to do with no default route.
I had failed to define one.  As soon as I added one to the iSeries
configuration, I connected with SSL.  That is why I could connect internally
but could not through the firewall.

Simple, simple, simple.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Pete Helgren
Sent: Friday, February 20, 2004 10:28 AM
To: Midrange Systems Technical Discussion
Subject: RE: Firewall and SSL blues


Thanks Scott,

I am using Mochasoft TN5250.

In looking at the ISA logs I get a HTTP Status Code of 155 which is telling
me that I have an invalid security certificate so that tells me (I think)
that I set up the SSL certificate wrong (I guess).  I pretty much walked
through the Certificate building process using the standard values.  I am
not using a third party certificate and, in the past, I haven't had to
install a certificate on anything but the iSeries to get Secure Telnet
working.  To my knowledge, I don't remember installing a certificate in
Mochasoft in order to connect to the iSeries.

I vaguely remember slavishly walking through the set up for a *SYSTEM
certificate and an *OBJECTSIGNING certificate but I only assigned the
*SYSTEM certificate to the Telnet application.  Maybe I missed a step?

I'll give the openssl tool a try, but what should I look for?

Pete Helgren
Value Added Software,Inc.

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