Java Applet does not show in ver 6

[Clifford]

Hello,

We were using Wingate 5.2.3 and just upgraded to Ver 6. A few of our clients PC were authenticating by Java applet and it worked fine in 5.2.3.

Version 6 does not show up the Java applet and instead gives the user a 403 'you are not authorized to view this page' error on the browser. I then tried the basic authentication and it works. The drawback is that basic does not log off the user (any other user can browse) unless the user reboots.

The Java applet seems to be the most appropriate in my context but it does not work after the upgrade.

Any one can help, please. maybe some settings are incorrect?


Clifford

[MattP]

Hi Clifford,

Do you see Java authentication as an option? If you're using the NT database you won't see the Java authentication option, instead you'll have NT authentication.

Have you bound the Remote Control Service to the internal adapter?

What do you see on the activity screen when one of the users tries to connect?

Matt

[Clifford]

yes, I see the java authentication option, just next to the basic authentication. The java option is on. The basic is off.

I'm not using the NT authentication.

There is nothing at the activity screen when user tries to browse or use the internet. Neither in the system messages nor in the firewall tabs.

[MattP]

Are you able to ping an external address from a client behind WinGate? Try yahoo as it responds to ping. What do you see on the activity screen when you do this? How are your clients connecting to the WinGate server?

Matt

[Clifford]

yes, wingate clients can ping outside address because nat ens is everyone unknown. Wingate clients have default gateway pointed to wingate machine.

They can browse if www restriction is set to everyone unknown (which I don't want). I have therefore put restriction so as to enable java authentication. The java popup is not showing up and internet explorer on wingate client is giving me a unable to display page error. That was my issue.

[mharris]

Just a note that I am having exactly the same problem (Having upgraded over the weekend and only got a working system this morning!).

The problem seems to be caused by having any assumed users (as this then never pops up the java login page). If you change the System Policy (Everyone) and select the option that users must be autheticated, the java login screen then appears as normal. The only side effect is that you then cannot have any assumed users!!
You can add a 2nd user or group to the policy but this then ignores the Everyone policy, and only the assumed users work.
As noted previously, you can use the basic authentication scheme, which then works fine.

I hope this helps add a little extra information.

Regards

Mike