Wingate 5.0.7 stops working every 2-3 days

[grtoro]

Wingate server 5.0.7 (on an NT4 machine) quits working every two or three days. There is no smoke or blue screens, just no connectivity and inability to run Gatekeeper. After this happens, we can't ping machines in the inside or the outside. The log files do not show any unusual behavior at these times.

We have a fairly simple configuration, with SMTP proxy services, WWW server, SOCKS, and a few other proxy services and mappings (no ENS, NAT, etc.).

We disabled history logging, but this did not seem to help. I would appreciate any suggestions. By the way, is 5.0.10 more or less stable than 5.0.7?

One of the things I thought of is to stop and restart the server automatically (using the Windows or Wingate schedures) every night (I know it's not elegant). Has anyone tried this? Any suggestions? I read in this forum about command-line options that might help do this, but I can't find anything in the documentation.

Thanks,

Gabriel

[DeanP]

I trust 5.0.10 about as much as ticking letter bomb. I loaded and tried to work with support for about 3 weeks this ver has multi-problems from DNS to gatekeeper on remote computers to not being able to run vpn at all. I have given up all hope on ver 5.0.10. This ver is at leased 1 month old they need a new (Bug Free) release fast. or they are going to lose a lot of long term customers like myself and my company. I have been using wingate for about 3 1/2 years. ver 2.1. Wingate staff we need some answers. I guess the short answer is stay at 5.0.7.

[Tricker]

Wingate is going the Norton's way - attract new ones with exciting features, forget about the rest!

[adrien]

we are preparing a new release... we just want to make sure we nail the problems before we put it out...

[wingater]

Hello Gabriel,

i tried to restart Wingate PC every night. It works - i wrote a small program to make the restart. There is only a Windows shutdown function declared wich initiates the restart.

The program itself is started by scheduler of W2000.

Martin

[grtoro]

Thanks to those who responded to my question.

Adrien, I look forward to a new (more stable) release. We had a very good experience with Wingate 4.2 and earlier. It used to run for months at a time on this same NT4 machine (until the HD of the Wingate server crashed and we found out this PC was not being backed up).

Martin, can you give me a few more details about your program for the restart (commands used, etc.)?

Thanks,

Gabriel

[chr]

My opinion is that 5.0.10 isa more stable than 5.0.8 if you are using ENS, with 5.0.8 I received ENS errors about 40, 60 times a day. I am now running 5.0.10 with a restart & delete every night. Works fine for me. For those of you that isnt restarting, do it and zip your log-files. It saves space and performance. Go ahead and write some batchfiles, start the scheduler service and type "at ******".

If there still is someone out there who can do something without a mouse. ;-)