why all the Wingate sessions will block in ONE minute ?

[takusa100]

i had built a wingate 6.0.4 server for NAT service, and had made user restrictions,means the PC users must open GateKeeper.exe and input their username & pwd for the auth,or they can't access the Internet. the machine works well before. but these days there is a strange thing happening: user who has been authenticated before ONE minute can't access the internet. And this user's auth item will disappear in the server "Client Activity" list. now if he reauth the GateKeeper.exe . he can access in one minute. just one minute, it would be cutted.
about the block time ,i calculated . it would be around 1 minute,almost 1"30.
god,what a strange thing ,how can i deal with it ?

[adrien]

Hi

The Remote Control Service may be timing out inactive connections (i.e. the GateKeepers).

Check the sessions tab for the Remote Control Service, and make sure that timeouts are disabled.

Regards

Adrien

[takusa100]

hi,
sure, i'm sure it is unchecked . the problem occured suddenly.
last week ,it worked well. now i have reinstalled the wingate, problem is still . the NAT function seemed no problem, when i had tried to close the user auth. everyone can access normally. In my LAN ,there are some arp spoof viruses burst out,now it's under my control , is it relative about that problem ? if yes,why does it take effect to the Remote Control Access session only ? thanks for your response!

Regards
takusa

[adrien]

Hi

If you enable logging in the Remote Control Service for session termination, you will get an exit code when the client sessions terminate.

That should allow us to figure out why the connections are being closed.

Could you post back the exit code of these sessions that are closing early?

Adrien

[takusa100]

thanks for your good idea , i try to do this according to what your said .
for the stabilization, i had closed all logs.:)

another point i noticed ,the GateKeeper.exe was not close normally. the Gatekeeper.exe of client had no any changes like online before, even error dialogs. i dont know whether the situation like this should be logged .
Later i will show the log files . thanks again .

regard
takusa

[takusa100]

hi,adrien
list below is pruned logs of the Remote Control Service,i can see that the auth session would be terminated around 1 minute.and at this period,no operations had been done about the client PC. so need your exact analysis and opinions .

anyway ,thank you so much.

//part log
13:39:24 10.33.89.20 lisl 0000416678 Created:
13:39:25 10.33.89.20 lisl 0000416678 Requested: WinGate Login: Retrieve System Info
13:39:25 10.33.89.20 lisl 0000416678 Failed authorisation:
13:39:25 10.33.89.20 lisl 0000416678 Failed authorisation:
13:39:25 10.33.89.20 lisl 0000416678 Requested: WinGate Login: Get local IP Information
13:39:25 10.33.89.20 lisl 0000416678 Requested: WinGate Login: Get all licences
13:40:32 10.33.89.20 lisl 0000416678 Traffic 2510 131 0 0 68s
13:40:32 10.33.89.20 lisl 0000416678 Terminated exit code 0
13:46:49 10.33.88.18 songyf 0000425109 Created:
13:46:50 10.33.88.18 songyf 0000425109 Requested: WinGate Login: Retrieve System Info
13:46:50 10.33.88.18 songyf 0000425109 Failed authorisation:
13:46:50 10.33.88.18 songyf 0000425109 Failed authorisation:
13:46:50 10.33.88.18 songyf 0000425109 Requested: WinGate Login: Get local IP Information
13:46:50 10.33.88.18 songyf 0000425109 Requested: WinGate Login: Get all licences
13:47:43 10.33.95.15 wuwh 0000426132 Created:
13:47:43 10.33.95.15 wuwh 0000426132 Requested: WinGate Login: Retrieve System Info
13:47:43 10.33.95.15 wuwh 0000426132 Failed authorisation:
13:47:43 10.33.95.15 wuwh 0000426132 Failed authorisation:
13:47:43 10.33.95.15 wuwh 0000426132 Requested: WinGate Login: Get local IP Information
13:47:43 10.33.95.15 wuwh 0000426132 Requested: WinGate Login: Get all licences
13:47:57 10.33.88.18 songyf 0000425109 Traffic 2510 123 0 0 68s
13:47:57 10.33.88.18 songyf 0000425109 Terminated exit code 0
13:48:22 10.33.90.213 xub 0000426940 Created:
13:48:22 10.33.90.213 xub 0000426940 Requested: WinGate Login: Retrieve System Info
13:48:22 10.33.90.213 xub 0000426940 Failed authorisation:
13:48:22 10.33.90.213 xub 0000426940 Failed authorisation:
13:48:22 10.33.90.213 xub 0000426940 Requested: WinGate Login: Get local IP Information
13:48:22 10.33.90.213 xub 0000426940 Requested: WinGate Login: Get all licences
13:48:50 10.33.95.15 wuwh 0000426132 Traffic 2560 121 0 0 67s
13:48:50 10.33.95.15 wuwh 0000426132 Terminated exit code 0
13:49:30 10.33.90.213 xub 0000426940 Traffic 2610 123 0 0 68s
13:49:30 10.33.90.213 xub 0000426940 Terminated exit code 0

[adrien]

Hi

Exit code 0 means normal termination (as far as the server thinks).

So that means GateKeeper disconnected.

I think maybe GateKeeper gave up waiting for something, and due to policies it wasn't going to get it. that indicates a problem possibly in GateKeeper we need to look into.

You are using GateKeeper just for authentication of your clients?

there is another smaller application that we have that is much better for this. allows people to log in, and change password, but that's it, and runs in the system tray. It's much smaller as well.

Adrien

[takusa100]

hi ,adrien

i had used the gatekeeper for the client authentications only . and the small software you meant is QbikAuth.exe ? yes ,it can re-authenticate,but problem still existed and will too many re-auth sessions burst make the server unstable ?
i puzzled about why this problem came out suddenly. the config of the wingate server hadn't modified for a long time.the server runs normally before. i really hope to solve this strange problem . thanks.

regards
takusa

[adrien]

hi

It shouldn't bother Wingate if there are a lot of QbikAuth sessions coming and going.

But it is interesting why they are disconnecting.

Do you have any packet capture software? It would be interesting to see if the clients are actually disconnecting, or whether something else is disconnecting them.

Regards

Adrien