Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Users not being logged off

Feb 07 04 6:09 am

Hi there,
This is setup:
Wingate5.22 on winNT 4.0 server with users connecting via java applet. User list is based off wingate user database not windowsNT database.
Quite often users will loggoff on the java applet but will still be able to surf the internet after that.
I even had one laptop user saying that after logging off and restarting windows he could still surf the internet without logging into wingate.

From the server I can often see when users are not logged off even though they have clicked loggoff on the java applet.

Wingate just doesnt seem to release the user and this causes a major problem for us because we charge users for internet time - they are getting over charged because they are staying logged on even though they think they've logged off.
I have set scheduler to automatically logoff eveyone at 1am but even staying on for 1hour too much is unacceptable when we are charging users per hour.
I often have to manually terminate wingate sessions from the server.

If wingate has not released/logged off the user then they will be able to open IE and surf the net without the wingate java screen appearing.

At first I thought it was simply a user problem but it is now a regular occurence on a several machines.

Thank You

Feb 09 04 1:53 am

Further to this i notice that in gatekeeper the word (assumed) is next to users that haven't been logged off.
My system policy is that users must be authenticated not assumed. It seems like wingate is letting users continue using their account even once they've logged off because it just assumes the user is still on.
This is a serious problem.
I need wingate to fully release the username when they click loggoff otherwise the user accounting gets messed up when people are being charged for time they're not using.
cheers


WyldCyde

Apr 02 04 10:33 am

Any updates on this issue? I have one machine on our network doing the same, while others work fine.

Apr 06 04 5:31 am

yeah, it seems to only happen on certain machines.
no one has reported it lately so that might be good news.
Post a reply