Problem with ENS plugin

[jsperez]

Hi everyone.

We've installed Wingate in a server which also performs batch tasks late at night. We've detected that ENS introduces a 4 minutes TCP timeout which affects every comunication from the server, not also http requests through wingate. I don't know how to disable that timeout. Disabling ENS isn't enough to solve the problem.

Wingate 6.2.2 doesn't have this bug. With Wingate 6.5.1 we bypassed that anoying bug uninstalling ENS but, with Wingate 6.5.2 it's impossible to uninstall ENS once it's installed.

The steps that we followed are:

1) Opening GateKeeper as Domain Administrator.
2) Menu Options->Plugins->Extended networking
3) Uncheck "Enable Extended Networking"
4) Click on "..." button and select the option "Do not load ENS when system starts". Status changes to "Inactive, Will be uninstalled"
5) Restart the server
6) When the server comes up againg ENS driver is loaded once again.

Entering in Start Menu -> Programs -> Wingate -> Advanced options. I've checked that all timeouts under "Timeouts" options are set to 0.

It seems that the 4 minutes timeout is hardcoded somewhere on the ENS driver sources.

PLEASE! Don't force me to cry and beg for a solution. We've lots of batch tasks wich takes more than four minutes to finish and ENS is killing them and, at the same time, killing us.

We need a patch or workarround for this bug!

[adrien]

Hi

I had discussions this morning on this exact topic, so we will be changing this behaviour. We added timeouts for local connections with 6.5, but I think that was in hind-sight a bad idea. We just need to make sure there were no other reasons it was introduced (potentially an FTP issue).

We've got a fix for the dialup issues as well (turned out to be a quirk of our build server compared to our dev machines) so we'll be releasing a 6.5.3 very soon.

In the meantime, if the connection is being made inbound to the WinGate server on a port, you can set timeout overrides in Extended Networking port security. If it's an outbound connection initiated by the WinGate machine, there's no way to alter the timeout.

Regards

Adrien