Wingate hangs whole O/S when a User Account disabled

[andrewclark]

I'm running 5.2.0 - usually stable.

However to prevent a user having unlimited access I have had to disable his account periodically.

This has 2 effects:
1. It generates a lot of system Messages about his access denied
2. After less than an hour or so the whole machine freezes and has to be rebooted.

I am running Win 2000 Pro.

Any ideas - Is this a known issue?

TIA
Andrew

[Pascal]

However to prevent a user having unlimited access I have had to disable his account periodically.

This has 2 effects:
1. It generates a lot of system Messages about his access denied
2. After less than an hour or so the whole machine freezes and has to be rebooted.

Which Userdatabase are you using ? WinGate, NT or the combination method ?

[andrewclark]

However to prevent a user having unlimited access I have had to disable his account periodically.

This has 2 effects:
1. It generates a lot of system Messages about his access denied
2. After less than an hour or so the whole machine freezes and has to be rebooted.

Which Userdatabase are you using ? WinGate, NT or the combination method ?

The Wingate Database. I did switch at one point to the NT/2000 database whilst testing Wingate VPN, and synchronised the two.

[neil]

How is the user connecting? Via NAT?! When you disable his account, does he currently have any active sessions (shown in the activity panel of gatekeeper)? Do you leave Gatekeeper open the whole time?! Does this crash still happen if not?!

Regards

Neil

[andrewclark]

Neil
>How is the user connecting?
He is an "Assumed User" based on machine Name
>Via NAT?!
Yes - Windows XP without WGC loaded
>When you disable his account, does he currently have any active sessions (shown in the activity panel of gatekeeper)?
No.
>Do you leave Gatekeeper open the whole time?!
No.
Does this crash still happen if not?!
I believe so, but will check this for you tonight - as the machine freezes completely I can't be sure if I left it open last time or not. It's a fairly severe effect - on a previous occasion the crash left such a mess of corrupted Windows files I had to restore the machine completely from an image. So lets hope it doesn't make too big a mess this time!

Regards
Andrew

[andrewclark]

Neil
>How is the user connecting?
He is an "Assumed User" based on machine Name
>Via NAT?!
Yes - Windows XP without WGC loaded
>When you disable his account, does he currently have any active sessions (shown in the activity panel of gatekeeper)?
No.
>Do you leave Gatekeeper open the whole time?!
No.
Does this crash still happen if not?!
I believe so, but will check this for you tonight - as the machine freezes completely I can't be sure if I left it open last time or not. It's a fairly severe effect - on a previous occasion the crash left such a mess of corrupted Windows files I had to restore the machine completely from an image. So lets hope it doesn't make too big a mess this time!

(Update)
It definitely crashes when:
1) Gatekeeper is left open on the server
2) The client machine is on and actively requesting Internet Access.
3) Authorization failures are being Logged

I now need to check it overnight again with Gatekeeper closed but the client machine left running MSN Messenger.

Could this be some kind of buffer problem with the Logging?

Regards
Andrew

[Mendoza]

Same stupid bug make's me carzy too.
This weekend I will shave my ass with my beautifull licence and move to LINUX.This is too much.Crashes and BUGS and frezees.I had enough

[andrewclark]

Same stupid bug make's me carzy too.
This weekend I will shave my ass with my beautifull licence and move to LINUX.This is too much.Crashes and BUGS and frezees.I had enough

To be fair, I have used Wingate for years without too many problems. Complex software does tend to suffer bugs when new featues are added, and I have found the Support Staff on this board to be very helpful in resolving issues. It would be much more frustrating if they didn't care.

Now, all I need is a fix for this problem... :)

Andrew

[andrewclark]

Neil
>How is the user connecting?
He is an "Assumed User" based on machine Name
>Via NAT?!
Yes - Windows XP without WGC loaded
>When you disable his account, does he currently have any active sessions (shown in the activity panel of gatekeeper)?
No.
>Do you leave Gatekeeper open the whole time?!
No.
Does this crash still happen if not?!
I believe so, but will check this for you tonight - as the machine freezes completely I can't be sure if I left it open last time or not. It's a fairly severe effect - on a previous occasion the crash left such a mess of corrupted Windows files I had to restore the machine completely from an image. So lets hope it doesn't make too big a mess this time!

(Update)
It definitely crashes when:
1) Gatekeeper is left open on the server
2) The client machine is on and actively requesting Internet Access.
3) Authorization failures are being Logged

I now need to check it overnight again with Gatekeeper closed but the client machine left running MSN Messenger.

Could this be some kind of buffer problem with the Logging?

Regards
Andrew

Guys.

Any update on this bug? I need to be able to disable a User.

Regards
Andrew

[neil]

Unfortunately i still can't repro this. Again, last night i set up WinGate as you describe, Win 2K (with SP4), left GateKeeper open, had an assumed user by machine name, and then disabled this user. I then opened a testing app we have, on this client that had the assumed user associated with it, that made 10 requests every 2 seconds for the next 17 hours, all of which of course had auth failures and were logged, both to file and GK. And still WinGate is going. GateKeeper's memory is quite high around 50 megs, as you wuold expect with so many syslogs, but other clients can still connect out through it, and the OS is holding up.

As you mention you cuold try turning off logging of these auth failures (either turning off logging to file, screen or both) and see if that helps. You don't have debug logging enabled do you?

Regards

Neil

[andrewclark]

>Unfortunately i still can't repro this. Again, last night i set up WinGate as you describe, Win 2K (with SP4), left GateKeeper open, had an assumed user by machine name, and then disabled this user. I then opened a testing app we have, on this client that had the assumed user associated with it, that made 10 requests every 2 seconds for the next 17 hours, all of which of course had auth failures and were logged, both to file and GK. And still WinGate is going. GateKeeper's memory is quite high around 50 megs, as you wuold expect with so many syslogs, but other clients can still connect out through it, and the OS is holding up.

AC>Hmmm - you certainly seem to have given it a flogging!

>As you mention you cuold try turning off logging of these auth failures (either turning off logging to file, screen or both)
AC>How does one select that - there seems to be only one check box on the "Logging" Tab to uncheck Authorisation failures?

and see if that helps.

AC> OK, I'll try that and run it for a few days, and report back to you.
I have also upgraded to the latest release 5.2.2 since the last post, in case that would make adifference, but I haven't had the opportunity to test it with this issue, as when it fails it makes a real mess of my mission-critical Wingate Server!

AC>You don't have debug logging enabled do you?
No, that us unchecked.

Thanks for your efforts so far!

[andrewclark]

Neil - update marked AC2>>

>As you mention you cuold try turning off logging of these auth failures (either turning off logging to file, screen or both)
AC>How does one select that - there seems to be only one check box on the "Logging" Tab to uncheck Authorisation failures?

AC2>> Logging now set as unchecked. Gatekeeper closed after setting user account as disabled, but user machine turned off. Server ran fine for 24 hours until User machine was turned on, then within minutes it crashed the Wingate server. Completely. No response at all, not even pulling up Task Manager on Ctrl-Alt-Del!

I'm at a loss!

Regards
Andrew