Terminal Server / Java Applet Logon Problem

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Terminal Server / Java Applet Logon Problem

Postby leedaniels » Nov 13 03 5:32 am

We're currently running Wingate 5.0.10 on a Win98se PC with most of our users running Internet Explorer off an NT Terminal Server.

I'm in the process of setting up authentication via the java applet and have noticed that once the first user logs on, the java applet doesn't load for any subsequent users thereby letting them use the internet without authentication.

Looking at the Gatekeeper activity screen, Wingate ( presumably seeing just one machine/ip for all our users ) shows all activity under the first users logon details.

Any ideas greatly appreciated.

Lee
leedaniels
 
Posts: 7
Joined: Oct 21 03 2:57 am

Postby max3do » Nov 13 03 10:21 pm

HEy buddy!
THe best part of working with wingate i like is to setting up authentication
for users....and the most confusing part.....
take 3 mechines....one server two clients....
now try testing on them....so this way u won't go confuse......
------------------------------------

lets only Talk about www.proxy....-->Properties--->polices tab-->what rights ur using...?
default rights (system polices)--->>>????????
----------------------------
don't add every one in the list.....
just one user...... try authenticat one user..... and test it..
----------------------
please tell me more about ur polices......
bye for now...
i will add this later
max3do
 
Posts: 45
Joined: Oct 17 03 9:33 pm
Location: Lahore, pakistan

Postby leedaniels » Nov 13 03 10:50 pm

System Policies set to Everyone Must be Authenticated.

WWW Policies set to Everyone Must be Authenticated.

General Tab for Java Authentication is ticked.

I only have this issue with our NT4 Terminal Server users, our few ordinary PC users have the java applet appearing correctly.

It seems to be the fact that we have 30 users running off one server/ip address. I'm presuming what drives the applet to appear is if the remote machine/ip has not yet been authenticated, hence our first Terminal Server user requires authentication and thereafter our remaining users don't.

Have you used wingate in a thin client enviroment successfully?

Thanks,

Lee :)
leedaniels
 
Posts: 7
Joined: Oct 21 03 2:57 am


Return to WinGate

Who is online

Users browsing this forum: Google [Bot] and 162 guests