Re: Firewall and SSL blues

[Larry Bolhuis <lbolhuis@xxxxxxxxxx>]

Pete,

How many times does the fix turn out to be such a simple thing!?  I once 
had a customer attempt to convince me to bill them only for the time to 
correct the problem, not for the time to determine what was wrong (and 
it was their fault!)  

Reminds me of the guy who repaired the widget machine. Seems the machine 
was turning out bad widgets so he was called in.  He examined the 
widgets, examined the machine, then took out a screwdriver and turned a 
screw on the machine. Sure enough the machine was now ticking off 
perfect widgets.  He sent them a bill for $1000.  They called and 
complained that no way they would pay $1000 for that tiny adjustment! 
"All you did was turn one tiny screw!" and they demanded he re-bill 
them.  So he did: 'Turning a screw:  $1, Knowing which way and how far 
to turn said screw:  $999'

 - Larry

Pete Helgren wrote:

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

--
Larry Bolhuis                   IBM eServer Certified Systems Expert:
Vice President                    iSeries Technical Solutions V5R2
Arbor Solutions, Inc.             iSeries LPAR Technical Solutions V5R2
1345 Monroe NW Suite 259          iSeries Linux Technical Solutions V5R2
Grand Rapids, MI 49505            iSeries Windows Integration Technical 
Solutions V5R2
                               IBM eServer Certified Systems Specialist
(616) 451-2500                    iSeries System Administrator for 
OS/400 V5R2
(616) 451-2571 - Fax              AS/400 RPG IV Developer
(616) 260-4746 - Cell             iSeries System Command Operations V5R2