FXPing from Site to Site hangs intermittently

JCDinPGH · 06-14-2002, 07:05 AM

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 · 06-14-2002, 05:42 PM

http://www.flashfxp.ws/forum/showthr...=&threadid=879

dinje · 11-30-2002, 10:01 PM

i have the same problem...

the link above doesn't work?

MxxCon · 11-30-2002, 10:23 PM

Quote:

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 · 12-11-2002, 11:03 AM

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 · 12-11-2002, 04:40 PM

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

gozu · 12-16-2002, 02:49 PM

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 · 12-16-2002, 03:37 PM

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 · 12-16-2002, 03:44 PM

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 · 12-16-2002, 03:56 PM

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

darkone · 12-22-2002, 11:18 AM

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 · 01-02-2003, 03:27 PM

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 · 01-02-2003, 04:15 PM

Quote:

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 indefenatly

Quote:

Of 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 · 01-02-2003, 07:29 PM

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 · 01-03-2003, 04:03 AM

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.