why the GateKeeper.exe can't log out immediately ?

[takusa100]

i used the GateKeeper.exe to authenticate the internet user. but i found a question: After i authenticated successfully,i click the "Go Offline" button,the user must be logged out, but now the client pc still can view the webService and anonther services,just like the user was still online.

i remembered the wingate Ver 5 worked well on this point.

thx ,
takusa[/code]

[adrien]

Hi

depending on the browser, it may still have connections open through the proxy to the server.

since WinGate 6.0 added persistent connections (i.e. Connection: Keep-Alive) support, browsers may keep the connections open for a long time if talking to the same site.

If the browsers are configured to connect to the proxy, then they can keep the connections open a very long time, and use the same connection to get requests from many sites.

Adrien

[takusa100]

but i just used the NAT function in WG6,not the proxy.and besides some web connections, another TCP conns like some p2p software still worked .one my colleague said he can make the outBound connections one morning by using the BitComit after logging on the GateKeeper once and then log out immediately,and i can see his traffics after he went offline actually.i think maybe it's too long.

thks ,
takusa

[takusa100]

Excuse for my too many questions.

i have about 150 users by using gatekeeper.exe authentication to access the internet. but one question confused me for a long time:(Version 5 didn't appeared this problem yet)
for example , last yesterday i configured the WG Server well with few persons were online, WG worked well .
But in this morning .i tried the GateKeeper.exe authentication,when i clicked the "Go Online" button ,it was no any response,after for a while ,the gatekeeper said like "No Data received from the Server,check the server and port....";sometime it could be connected ,but the response time was not short as the normal .

any almost all users had encountered this situation,and told can't authenticate.

takusa

[adrien]

but i just used the NAT function in WG6,not the proxy.and besides some web connections, another TCP conns like some p2p software still worked .one my colleague said he can make the outBound connections one morning by using the BitComit after logging on the GateKeeper once and then log out immediately,and i can see his traffics after he went offline actually.i think maybe it's too long.

thks ,
takusa

WinGate has the concept of machines and users. A machine is associated with an IP address. So, when a user accesses WinGate from an IP, if that user authenticates, then normally (unless you have that IP address listed as a multi-user IP) the machine is associated with that user, and any other subsequent traffic is deemed to be from that same user.

Whilst there is any traffic happening from that user's IP, the association between the machine and that user will remain, and any new sessions will still be deemed to be that user.

So, if you have a GateKeeper connection, you will be authenticated as a user, if GateKeeper disconnects, existing other sessions will remain, and new sessions will be shown as assumed.

if your policies allow "user may be assumed", then new sessions will still be allowed to be created.

Existing connections are not destroyed when you log out with GateKeeper either.

Adrien

[adrien]

Excuse for my too many questions.

i have about 150 users by using gatekeeper.exe authentication to access the internet. but one question confused me for a long time:(Version 5 didn't appeared this problem yet)
for example , last yesterday i configured the WG Server well with few persons were online, WG worked well .
But in this morning .i tried the GateKeeper.exe authentication,when i clicked the "Go Online" button ,it was no any response,after for a while ,the gatekeeper said like "No Data received from the Server,check the server and port....";sometime it could be connected ,but the response time was not short as the normal .

any almost all users had encountered this situation,and told can't authenticate.

takusa

Hi

Check the history database file. This file shouldn't be allowed to grow too big. We have found that this seems to be the main reason WinGate locks up occasionally. You can delete the files by

1. Stop the WinGate engine
2. Delete History.dcx and History.dbx from the WinGate folder
3. Start WinGate again.

Adrien