Missing 226 for ul/dl/fxp behind router

Daeluin · 08-28-2002, 04:03 AM

Using 2.0 b865 RC2
with winXP

I've seen this problem posted here before a few times, but never a solution.

When downloading/uploading/fxping a file, it seems if the transfer takes longer than ~30 minutes no '226 Transfer Complete' (or any other) message is returned. So then the client gets timed out, reconnects, sees the file is there and executes the 'when file exists' settings.

This all started happening when I had to set up behind a linksys router. Using latest firmware and can't find any mention of the problem on the linksys site.

It happens with every site I use, so I doubt it's a server side matter.

Small files, or files that take less than 20 - 25 minutes seem to work just fine, always receiving the 226 Transfer Complete.

Using passive mode, external IP is set just in case.
Tried every combination of settings I could think of, but the problem persists.

I hope someone can solve this, but my hopes aren't high.
Goodluck.

MxxCon · 08-28-2002, 01:30 PM

this is problem with session time out setting.
try checking "send noop during transfer", but keep in mind that it will cause problems with servers that don't support this.

Daeluin · 08-29-2002, 02:13 AM

Keep alives aren't sent during a tranfer (unless I'm mistaken) and it doesn't know it's idle until the server boots it out. After the file completes, no 226 message is received, so the client thinks it's still sending until the time-out.
So setting it to send NOOP doesn't do anything for this situation... (it times out before it knows it's idle.)

The time out happens with fxping and uploading; downloading is slightly different, but as it doesn't time out of the server I'm not as worried about it.

Is there anything that could be blocking the 226 message from the client?

Thanks for the suggestion though. ^^ Any other ideas?

MxxCon · 08-29-2002, 03:42 AM

most likely what happens is during long transfers there is no activity on control connection, so after a while, in your case "less than 20 - 25 minutes", your router closes that connection, transfer complets normaly, but you don't get 226 becuase control connection is closed, not becuase server booted you out(server knows that there is a transfer, but your router doesn't) and after that flashfxp waits 30sec at which point you actualy see timeout message.

"send noop during transfer" will keep control connection alive..by sending 'noop' during transfer

. like i stated above, this option may cuase problems with some servers.

alternatively you might want to look into your router config and set connection timeout to even larger value.

Daeluin · 08-29-2002, 04:42 AM

ahh, I appologize, I misread your first reply.

yeah, that sounds like what the problem must be.

I'll try that, thanks for the help (=

Delerium69 · 09-15-2002, 11:35 AM

I have the same problem (again Linksys router). I've tried using all versions including RC3 to try and see if I can resolve the issue it just doesn't like fxping for me.

File transfers, as stated before, with smaller files but with larger ones that take 20mins+, it cuts out when the file is done. And when relogging onto the server (flashfxp doesn't do this auto) it then gives me the transfer complete message for the file that I fxped.

The send NO-OP doesn't seem to work for me.

But here is an interesting quirk - of all of the transfers I have tried, I CAN fxp without a problem to one ftp which has just blown all my theories out of the water.

I'd really like to use flashfxp but I can't justify paying for a full registration until I know it can work for me.

Is there anyone out there that can help me solve this issue?

Thanks

Del

Daeluin · 09-15-2002, 12:25 PM

sending NOOPs works for me.

all I can say is make sure you're sending noops during the transfer (preferences/firewall settings) and not the keep alive noops.

I couldn't find a way to adjust the timeout in the linksys firmware... =/

good luck

Delerium69 · 09-15-2002, 01:27 PM

Thanks - yes that works a treat - although i'm not happy about the fact the help file says this can break many ftps. Is there an option where we can choose the frequency of when it sends the no-ops - cant seem to see that anywhere.

Del

Daeluin · 09-15-2002, 02:28 PM

I think most servers allow noops by default now; at least I haven't had any problems.

Yeah, an option to change the delay between transfer noops would be great, although I doubt it effects anything.

MxxCon · 09-15-2002, 03:21 PM

Quote:

Originally posted by Daeluin
I think most servers allow noops by default now; at least I haven't had any problems.

problem might arise not with "noop" itself, but with the fact that you are sending a command during transfer.
according to RFCs ftpd should allow sending commands during transfer so...

bigstar · 09-15-2002, 03:22 PM

The interval can be adjusted by editing the FlashFXP.ini

Please see the following post for more details
http://forum.flashfxp.com/showthread...&threadid=1218