Wingate service stops accidentally!!

[NickyDJ]

I'm running Wingate 5.1 on a Windows Server 2003 standard edition machine.
I posted another topic 2 days ago about NO ALL the NICs are shown in the service windows...
But now i found out a new problem: wingate stops itself accidentally after a random period of time!!! So i must re-start the service manually each time to resolve the problem!!!
Could you resolve that quickly?
Regards
Nicola

[neil]

WinGate should be perfectly fine on a 2003 machine. Is there anything specifc happening on the WinGate machine at the time the engine stops? If you have WinGate running, for example, with no gatekeeper open, and no traffic going through it, will it still stop itself? What is the memory like while WinGate is running? And CPU? Can you restart the WinGate engine straight away, or do you have to reboot the machine? Is there anything written to any of your logs that may be of interest?

Regards
Neil

[NickyDJ]

Dear Neil, now i answer this topic.
My server is at its first configuration, so it's clean with no other apllications running on... So the only apllication running on it is Wingate.
(my RAM memory is 1GB)....
Wingate seems to stop with no reason and without anything else that could cause its stopping... My CPU is a Xeon 2.4 Mhz... Anyway after stopping i can restart Wingate restarting the engine only, no reboot is needed. The server Logs only say that Wingate service has stopped accidentally...

Many thank and waiting for a reply...
Nicola

[NickyDJ]

Perhaps I found a correlation between an application used from a client and Wingate crashing...
It seems that Wingate stops accidentally (after a short period of time)when a Client connects the Wingate WWW proxy service through Opera 7.21 browser.... while if Internet Explorer only is used, Wingate doesn't stop...
Could it be helpful?
Regards
Nicola

[johnza]

I think the reason is not important.At first you can install windows 2000 to test the compatibility of your computer.

[srcloutier]

I have a batch procedure I've been using which works around the problem. The procedure tests the proxy, and if the proxy does not respond correctly (or at all), the procedure will stop and restart it for you.

The procedure includes a utility which tests the proxy's ability to respond to an HTTP GET message. If this succeeds, the proxy is deemed to be OK. It does not test the proxy's ability to retrieve an HTTP page from an outside location. When the proxy hangs, it will not respond to any messages at all, and this is what my procedure looks at.

Check: ftp://ftp.piesky.com/pub/wg.zip

This works very well for me.

Regards,

Steve

[davida62]

I have had problems in the past with network card drivers; they can cause NT to crash with the dreaded BSOD. If you have a different NIC card, preferably one that has drivers that Win2003 is happy with, perhaps you could try that out.

David