It 's not very stable

[wingateuser_cn]

I installed Wingate on windows 2003 server and used it as a proxy, there are around 100 to 200 clients connecting through the proxy to the Internet.

The problem is this:

It works fine for only one or two days, sometimes a few hours, or may be when the network load is light. After that or otherwise, the Web browsing from the clients side become very very slow. the only solution is to restart the server that installed Wingate to get things back to normal.

I am wondering if there are any configurations to solve the problem? thanks.

[engineerzg]

i'm agree with you. I have the same problem :(

[logan]

Make sure you aren't leaving the GateKeeper open when the server is unattended. A lot of communication occurs between the GateKeeper and the WinGate engine so if you leave the GateKeeper open and connected, your system resources will be slowly used up in time often leading to instability. The best method to avoid this is to place a timeout on the Remote Control Service. If a GateKeeper is left idly connected to the WinGate engine, it will be disconnected automatically.

• GateKeeper -> System tab -> Remote Control Services -> Sessions
• Enable "Sessions time out after X seconds of inactivity"
• Set X to a suitable value value (the default value is 180)
• Click OK

[wingateuser_cn]

Make sure you aren't leaving the GateKeeper open when the server is unattended. A lot of communication occurs between the GateKeeper and the WinGate engine so if you leave the GateKeeper open and connected, your system resources will be slowly used up in time often leading to instability. The best method to avoid this is to place a timeout on the Remote Control Service. If a GateKeeper is left idly connected to the WinGate engine, it will be disconnected automatically.

• GateKeeper -> System tab -> Remote Control Services -> Sessions
• Enable "Sessions time out after X seconds of inactivity"
• Set X to a suitable value value (the default value is 180)
• Click OK

thanks, but I 've already done that,
when the web browsing from clients side become slow, the remote login of the Gatekeeper becomes slow too, it takes up to 10 seconds to login. I 've also checked the server running Wingate also, the server is normal, the CPU utilization, the memory and the bandwidth utilization etc.
So, it is very strange, any idea about it?

[Nev]

Have you disabled logging for all services?

Disabled caching and Transparent Redirection?

[wingateuser_cn]

Have you disabled logging for all services?

Disabled caching and Transparent Redirection?

only log www proxy,
caching and transparent redirection have already been disabled

[logan]

Can you try making the following change in your WinGate configuration please.

- GateKeeper -> Services tab -> WWW Proxy Server -> Sessions
- Disable the session timeout so that WinGate will not close idle sessions

[wingateuser_cn]

Can you try making the following change in your WinGate configuration please.

- GateKeeper -> Services tab -> WWW Proxy Server -> Sessions
- Disable the session timeout so that WinGate will not close idle sessions

I've tried this also, and disabled the logging event for www proxy server, the problem is still there.

Will there be any chances that my server has some virues running, which caused the problem? but it looks fine.
because I am always getting the message from windows event logging like this:

The Winhttp web proxy auto discovery service has been idle for 15 minutes. It will be shut down.

[adrien]

we found a stability issue in the WWW proxy relating to chunking.

There is a release candidate of WinGate 6.5 available that we've resolved this problem in. it's available at

http://www.wingate.com/downloads/WinGat ... 96-USE.EXE

We hope to finalise testing on this for a release early next week, but in the meantime, if you are having urgent stability issues, we recommend this one.