What might cause a signed applet, which otherwise (i.e. when not firewalled)
loads and executes, to fail to load (leaving the dreaded 'X" in the upper
left corner of the window designated to it by the browswer) under Java 1.5
when behind a firewall whereby port 80 is wide open?

I thought applets loaded through port 80? What, in a firewall configuration
of this sort, might cause the firewall not to find the applet -- it is a
simple class file residing on a server other than the one that is being
called up in the browser (and when NOT behind a firewall, it always comes up
fine). Thanks, Ike