Wingate WWW Proxy unresponsive

[sduffey]

I have had repeated issues with the Wingate server becoming unresponsive to WWW Proxy requests. When this happens DNS resolution still works and NAT still works. If I go to the Wingate server and load a local browser session the page loads just fine but all clients behind the Wingate server are hosed. Any attempt to restart the Wingate engine results in the engine hanging. The only fix is to restart the entire server, everything is fine afterwards. The problem is quite annoying and has been happening on average several times a week.


I am running 6.62 build 1298.

[adrien]

Hi Shawn

Hope you got my email - is there any chance I can have a look at the system?

Regards

Adrien

[adrien]

Hi Shawn

It just happened here, so we're investigating.

one thing I note though, for us, the DNS server becomes unresponsive as well. You say for you DNS resolution for clients keeps working. Are they using WinGate as a DNS server?

Regards

Adrien

[sduffey]

Our Windows DNS server uses NAT to get to Comcast DNS servers for forwarded look ups. As a result I can still get DNS resolution even when this happens. It's almost like the proxy service is totally dead. When this occurs there is no long timeout as it tries to resolve the name, the browser instantly errors out.

[sduffey]

Adrien I sent you the files after our latest episode of the Wingate proxy hanging up.

[adrien]

Hi Shawn

Trying to email you, but all your mail servers aren't accepting connections.

Regards

Adrien

[aperia]

We have the same issue with v.8.2.1 (4711) on an almost daily basis. However, we do a taskkill on the wingate services and Wingate restarts. Wingate simply stops serving requests and eventually no one can access the internet until it is restarted. Has anyone solved this issue? We can still pull DNS and ping during this down time, just cannot get browsers to work.

[adrien]

Hi aperia

Can you tell us a bit more about your system? E.g. is it running in a VM to a SAN, or anything like that?

There are issues logging to SAN due to extra latency due to network access to disk. We added caching into our logging system because of this.

Also the current version is 8.2.5 I'd suggest updating as well.

Regards

Adrien

[sdenzler]

We are having the same problem as the original post (below). We have had this problem on Version 6 and on the latest version 8 as well.

Original Post: I have had repeated issues with the Wingate server becoming unresponsive to WWW Proxy requests. When this happens DNS resolution still works and NAT still works. If I go to the Wingate server and load a local browser session the page loads just fine but all clients behind the Wingate server are hosed. Any attempt to restart the Wingate engine results in the engine hanging. The only fix is to restart the entire server, everything is fine afterwards. The problem is quite annoying and has been happening on average several times a week.

Has a solution to this problem been identified yet?

Thanks

[adrien]

Hi

the original issue was raised with WinGate 6.2.2. There have been several bugs fixed since then which could cause issues like this.

Normally we find issues like this nowadays are related to DNS resolution.

I'd suggest you open a support ticket on our support desk and you'll get more timely responses. Just email support@wingate.com

Regards

Adrien de Croy