FXP problem with large files

Kibe · 09-25-2003, 07:50 AM

Hey guys, I hope you can give me some idea about this problem.

It only happens when I transfers large files, for instance 50 mb, through some not so fast servers, so it takes about 40 minutes to finish each file. I suspect that FlashFXP is not receiving the reply from the destination server indicating that file was received.

Is it possible that Winroute is closing this connection because it was idle for a long time? Is that possible this can be fixed in a future build?

I'm using:

- FlashFXP 2.1, build 924, Registered
- WIndows XP Pro SP1
- Running behind a NAT, WInroute Pro 4.2.5
- Network ADSL

This is a sample of what status window reports:

List (cached)
List Complete.
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (xxx,xxx,xxx,xxx,10,240)
PORT xxx,xxx,xxx,xxx,10,240
200 PORT Command successful.
STOR xxxxxxxxx.rar
150 Opening BINARY mode data connection for xxxxxxxxx.rar.
RETR xxxxxxxxx.rar
150 Opening BINARY mode data connection for xxxxxxxxx.rar (50000000 bytes).
226 Transfer complete.
421 Connection timed out - closing.
Transfer Failed!

MxxCon · 09-25-2003, 12:46 PM

preference, Proxy/Firewall/Ident tab, enable "Send NOOP during transfer".
if that doesn't help, look into settings for WinRoute to increase idle connection timeout value.

Kibe · 09-26-2003, 12:01 AM

Thanks for your reply MxxCon!

I've already tryed to enable noop during transfers, but it wouldn't help. Reading your suggestion, I realized that the answer would probably be in Winroute.

I'm gonna try this setting now and check what happens:

Settings/Advanced/Misc. Options/Advanced Options
NAT Table Default timeout for TCP protocol 90 minutes (default was 40)

I'll report as soon as I notice any change.

Kibe · 09-27-2003, 06:53 PM

Just to let you know, my problem is solved.

If someone have the same issue, just change those setting I mentioned above, ok?

NathanO · 09-27-2003, 08:38 PM

If anyone knows how to solve this problem with a D-Link DI-707P router I'd like to know

It has no option for timeout values

NathanO · 10-04-2003, 12:11 AM

Solved it by using the 'Bind sockets to this address' and setting it to my WAN IP and ticking 'Site uses IP Masq/NAT/Non-Routable IP' in SiteList for the site that was timing out.