FTP timeout after 240 seconds

[epbrussels]

Hello,

I have a problem with long ftp download/upload. If the transer take longer than 4 mintues, the operation fails.
ftp> mget test2.tar
200 PORT command successful.
150 Opening BINARY mode data connection for test2.tar(1111726080 bytes).
421 Service not available, remote server has closed connection
684864340 bytes received in 242 seconds (2832440 bytes/s)

ftp> mget test2*
200 PORT command successful.
150 Opening BINARY mode data connection for test2.tar(1111726080 bytes).
421 Service not available, remote server has closed connection
804770644 bytes received in 241 seconds (3345585 bytes/s)

I tried the same thing on our second wingate server (same hardware, same os windows 2003, same wingate version 6.5.2) and the problem does not occur.

Any idea what stop the transfer after 4 minutes?

[Nev]

Not likely, however in the FTP proxy what is the timeout value?

[epbrussels]

The session timeout is 600 seconds of inactivity. And is the same on both wingate servers.

[adrien]

Hi

Is this going through the FTP proxy or via NAT?

If via the proxy, we link the control channel to the data channel by telling the driver the ports and IPs of both connections. If ALG.exe is running or Windows firewall however, this gets messed up, since it changes the port numbers between when we open the socket, and when the packets go through the driver.

This also breaks gateway selection.

So if you're going through the FTP proxy (either directly, or intercepted), you'll need to disable the windows firewall / alg.

Regards

Adrien

[epbrussels]

Hi,

We use the FTP proxy. The Windows firewall is disabled and ALG.exe is not running.

I compared the running windows services between our two servers and nothing is different.
I aslo compared the Wingate configs from registry export and I don't find any difference that could cause the timeout problem.

Vincent

[Nev]

Vincent, these servers share the same ISP, or a different Internet service // ISP for each Wingate?