FXPing from Site to Site hangs intermittently

[JCDinPGH]

I've tried this with several different versions and builds of Flashfxp so it's possible the problem is not in the program itself. When I queue several files to transfer from one site to another (FXP), the first file transfers completely but it never registers in flashfxp as being completed so even though the file was done transferring after 5 minutes (just an example), Flashfxp still thinks it's going and will hang like that forever until I cancel it. I've had this problem with many different ftp sites and it seems to be hit and miss. I really don't know if it's a problem with glftpd or flashfxp or a combination of both. Anyone seen this? Have a workaround? It's driving me crazy!
J.

[MxxCon]

http://www.flashfxp.ws/forum/showthread.php?s=&threadid=879

[dinje]

i have the same problem...

the link above doesn't work?

[MxxCon]

Originally posted by dinje
i have the same problem...

the link above doesn't work? without proving more info no way we can help you.
read me sig below

[gozu]

the same thing happens to me. The only common factor i could identify was a slow transmission speed (15-30 k/s). But this had never happened to me before while dealing with these same speeds so I don't know what to make of it.

flashfxp build: 2.0 901
O.S: winXP+SP1 professional

[MxxCon]

build 901 is an obsolete unsupported beta.
upgrade to latest public release, at this time it's 906.

[gozu]

this problem is not specific to build 901. I tried build 906 on a clean windows XP install and the problem remains. this problem only occurs for me when the speed is low (15-30 k/s) and the files are quite large (15-50 Mb).

the link maxxcon provided before does not work.

i do not know if this is relevant, but i'm using a linksys router (well configured)

[bigstar]

Are you behind a router or firewall? The problem you described sure sounds like it.

The connection is being closed and the client isn't being notified. The slow/longer a fxp transfer the greater the chances of the connection timing out.

[JCDinPGH]

The problem seems to be in the linksys router as I only have this problem when I am FXPing from home, which is behind a linksys router. I've tried adding the workstation into the DMZ in the router and also played with port forwarding settings but nothing seems to help. I imagine others with linksys routers also have the same or similar problems.
Thanks.

[MxxCon]

if your router support this, consider changing idle connection timeout value to a bigger number.

[darkone]

Or enable 'noop'ing during transfers.. it should keep the main connection alive (Some servers don't support nooping, so you'll get some few hundred noop responses after transfer is complete - but who cares as long as it doesn't hung :I)

[bigbras36]

I get the same problem.

OS: Windows XP
Version: 2.0 build 905
Config: Sat behind a linksys BLFS801 router.

Intermitantly, fxp transfers are not seen as completed, and flashfxp just sits there for hours on end (if you dont spot it), waiting for it to complete.

The transfer has compelted without error as confirmed by people looking at the file sizes on the other end.

My router contains no idle timout settings and has the latest firmware. I only see this problem with *some* sites, not all.

The discussion about the primary tcp connection timing out would seem logical, but if this is case why doesnt flashfxp report anything? Its a pretty serious thing if the fxp connection is dropped during a FXP. Maybe we can have a setting such as 'if fxp takes x10 longer than expected then skip to next file'. At least that would let thing continue without wasting any more time.

Of course if any of you brainy buys know the solution to this problem, then please let me know because its really annoying me!


bigbras36

[MxxCon]

Originally posted by bigbras36
The discussion about the primary tcp connection timing out would seem logical, but if this is case why doesnt flashfxp report anything? Its a pretty serious thing if the fxp connection is dropped during a FXP.

becuase during normal fxp transfer or for that matter normal upload or download, nothing is going on control connection. with upload/download flashfxp knows when data stop being transfered and if no reply is recieved during 90sec timeout period flashfxp will reconnect to the site, with fxp this is not the case, so flashfxp wait indefenatlyOf course if any of you brainy buys know the solution to this problem, then please let me know because its really annoying me!as a workaround you can try checking "send noops during transfers" from proxy tab.

[bigbras36]

My point is that during the FXP transfer flashfxp KNOWS if the connection is dropped. If it is, then it can surely work out that it will *NEVER* receive confirmation. So hanging indefinitely can be avoided surely!?


bigbras36


*edit*

im gonna try the noop thing in the mean-time. but lets not forget that some sites BAN on NOOPs.

*edit*

[bigstar]

That's just it though, FlashFXP doesn't know the connection is lost. If it knew then this problem wouldnt exist.

When doing FTP transfers FlashFXP can offer stall protection to determine if data has stopped sending and abort and restart.

[bigbras36]

Well, things are never as easy as I envisage them. This only leaves a 'if xfer takes X% longer than expected, then restart' option.

Thanks for your prompt replies.


bigbras36

[maclaeden]

But why does flashfxp not know the connection is dropped? I look at my firewall log and see connection attempts from the ftp's listening port to the local port flashfxp was using. If I open enough ports, flashfxp doesn't time out, so it must be accepting those connections once they are lost.

[bigstar]

In order for FlashFXP to know the connection was dropped the windows socket layer (winsock) must inform FlashFXP. This isn't happening.

[gozu]

A few facts I compiled since my original reply:

- This problem is not exclusive to flashfxp. Other fxp clients have the same problem (I tried smartftp with the same results).

- The noop method suggested earlier doesn't seem to work either.

- It is DEFINITELY caused by my router (a linksys). when i don't use it, that problem never occurs (or maybe its incidence is reduced so much i just never caught it)

It is thus my guess that the only solution to this is a workaround implemented in FlashFXP.

Flashfxp already estimates the time of the current transfer using the results of the last successfully sent file. so what bigbras suggested if xfer takes X% longer than expected, then restart' option. seems to me like an excellent idea. Make this option available for each individual site and let the user define X. i would personally go with something around 20-25% to allow for normal site slowdowns due to increased traffic.

Now, of course. this isn't a bug inherent fo flashfxp but to routers , network conditions or whatnot so I can understand why BigStar would be reluctant to try to solve a problem he didn't cause. Unfortunately, more and more people have Lans everyday and i just cannot spare my router. And it's a fact linksis is the leading brand. This problem will probably not go away in the near future but increase in proportions. If it's not too hard to code, I think it's worth a shot.

Thx bigstar

[BlaBlaBla123]

I have the same problem.. after receiving a file it just hangs at 'Transfer Complete'

I have tried everything written in this forum etc.. I tried it with no firewalls running and it still happends. I am also not behind a router. This did not happen to me in previous betas or final versions but it has on 2.0 Build 906 ..the only that works is the NOOP command. It still NOOPS after 'Transfer Complete' about 10 times then it finally disconnects and comes back online starting back in the queue. Which is still a time waster.

I'm almost positive its an issue in 906 as it didnt do this in previous versions until I upgraded now. :(

[MxxCon]

well, you could try to downgrade and see if problem still exist. but i highly doubt that's the case. it's possible that one of the servers is behind a router that drop idle connection..

[hpolimar]

i've no router and i have the same problem. and it occurs if the fxp is slow. TRANSFER COMPLETED and flashfxp hangs.

[bighead_1]

after upgradeing to latest public version (from main download link)
i'm still seeing this problem..

noop isn't working.. anyone else got any suggestions when using a linksys router

[visitor]

Hey, all

running:
XP Pro
500mHz Compaq
Linksys router on cable connection
FlashFXP 2.1b924

To alieviate hangs after transfers of individual files in qeue we set connection time-out lower - to lessen hang time before FlashFXP tries to reconnect.

& send noops during transfer under Proxy/Firewall/Ident worked to keep it from disconnecting at all, though we prefer not to run this option as default.

Is there a way to control the # of noops sent? We're getting:
[15:29:56] Transferred: xxxa.rar 14.31 MB in 24:32 (9.95 KBps)
[15:29:57] PASV
[15:29:57] 227 Entering Passive Mode (xx,xxx,xx,xxx,xxx,xxx)
[15:29:57] STOR xxxb.rar
[15:29:57] 150 Opening BINARY mode data connection for xxxb.rar.
[15:59:04] 226- [Ul: xMB] [Dl: xMB] [Speed: 8.39K/s] [Free: xMB]
[15:59:04] 226 [Section: DEFAULT] [Credits: xMB] [Ratio: Unlimited]
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] 200 NOOP command successful.
[15:59:04] Transferred: xxxb.rar 14.31 MB in 29:06 (8.39 KBps)
[15:59:04] PASV
[15:59:05] 227 Entering Passive Mode (xx,xxx,xx,xxx,xxx,xxx)
[15:59:05] STOR xxxc.rar
[15:59:05] 150 Opening BINARY mode data connection for xxxc.rar.

tried editing the INI to:
[Proxy]
SKA=600
...in hopes it wouldn't send as often, but that didn't seem to work the way we planned.

thaNX