# Re: Letting Java Out

Li Gong (gong@games.eng.sun.com)
Tue, 6 Jan 1998 15:48:55 -0800

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: David Hook: "JCE 1.2"
- Previous message: Jan Luehe: "Re: JCE availibility?"
- Maybe in reply to: Tim Nicholls: "Letting Java Out"

    Date: Tue, 6 Jan 1998 15:48:55 -0800

    Message-Id: <199801062348.PAA00822@games.eng.sun.com>

    From: Li Gong <gong@games.eng.sun.com>

    To: "Tim Nicholls" <TNICHOLLS@mercuryvmd.com>

    Subject: Re: Letting Java Out

    In-Reply-To: Tim Nicholls's mail of , 6 January, 1998

The problem appears to be that the IE/NS browswers do not recognize
the firewall proxy as the host from which the applet came from.
If you have to solve the problem today, you have to ticker with the
browser software.

Later this year, JDK1.2 model allows such connections, and Java
Activators should help you upgrade existing browsers to newer JDKs.
You can check out both the JDK1.2 beta and the Java Activators at
java.sun.com.

Cheers.

Li

Tim Nicholls writes:
> Hi,
>
> My company and I are having a problem letting our Java Applets out through
> our Checkpoint Firewall-1.
>
> We are using a Java applet as a form front-end to an oracle system running
> on windows nt 4.0. When a client connects internally there's no problem,
> but when someone tries to load the page from the other side of the firewall,
> the Java applet refuses to load, the Java console window shows a
> java.io.Exception, and a unsigned Java applet window appears with the
> message "FRM:9999 cannot connect to 144.141.2.100:8001"
>
> We have checked to ensure that the firewall rule base allows Java through,
> and we can access Java applets on other people's sites all right. We have
> also allowed ports in the range 8000-10000.
>
> Any help please?
>
>
> Tim M Nicholls
> Network Engineer
> Mercury VMD Ltd.
> http://www.mercuryvmd.com
> mailto:tnicholls@mercuryvmd.com
>

- Next message: David Hook: "JCE 1.2"
- Previous message: Jan Luehe: "Re: JCE availibility?"
- Maybe in reply to: Tim Nicholls: "Letting Java Out"