DescentBB

Okay, this is totally jacked up..

I have a batch of files I need to FTP up to my server. However, when at home using DSL, it only uploads maybe 10 files before it stopps and just sits there, and will time out.

I have High Speed internet with my cell phone, and I can FTP all day with it, but it seems like its changing the files slightly (adding breaks when there shouldn't be) and when they files get to the server, they are not 100% correct and the script won't run.

My question is, if anyone out there wants to take a crack at this for me, I will provide them with FTP access to my server if they would be so kind as to upload the files.

Thanks!

I beleive at home your issue is with the setup of your FTP client. I use Filezilla. Very easy to use and free.

As for the phone, I bet you it has to do with how it transfers the files, wether in binary or ANSI text. Or somethign like that. They can change a file slighty but enough for it not to work.

I second that.

thats the thing, I have the same exact setup as it has always been. It just started not working recently, and I too am using FileZilla.

Seems to work better if I connect in \"Active\" mode instead of normal or passive. But it will connect, and upload about 10 files then stop, and time out.

And sometimes the LIST command causes it to time out as well.

Check with your provider. Some of the providers out there are placing new controls and limits to bandwidth. Mine just knocked me back from unlimited to 5GB a month and placed caps on file transfer rates. I use Sprint.

I'd check with provider as to what protocols the FTP Server requires. Using Passive when the server requires Active will time out.

When using Passive, it times out at the initial LIST command, so I can't even see the files on the server.

Active lets me get in, but craps out after 10 or so uploads.

The only thing I can think of is it has to be my ISP.
If anyone wants to give it a shot, just let me know and you can see for yourself!

...Or it will work for whoever, and then I will know its my ISP. Unless you also use BellSouth.

1) Don't let anyone use your FTP. Giving away login information is not smart.
2) Just try using a different computer with different software.

1.) Yeah, thats obvious! I would create a FTP account with access ONLY to the directory in which I need the files uploaded to. once the upload is complete, I would delete the account.

2.) Been there, done that. Different Machine, Different ISP, seems to work fine.

As of right now though I need these files uploaded, and am looking for a volunteer.

How would you get the files to whoever would upload them for you? Plus how big are these files?

And how fast is your current upload speed?

I'm at work and locked down tight. For good reason.

The files I needed uploaded were those for an Ad Server (OpenX.org). Downloadable free. I think un-compressed, its like 25mb.

UPDATE: I got them to upload from home finally. I rebooted my router from its web-interface, and power cycled my DSL Modem (I have the 6MB/768K package, or whatever bellsouth's fastest offer is).

I had to reboot both of those, and force the FTP software into Active Mode, and instead of uploading them all at once in one big queue, I grabbed a bunch - uploaded them, then grabbed more, and uploaded them. Until finally, its done!

Still not sure what the problem is, still can't connect from home in normal/passive mode, I must be in active mode for it to work.

Passive FTP doesn't work if the FTP server is not configured for it properly.

The type of disconnect you had could be your router screwing it up, check for firmware updates. Otherwise you might need a new router, since I recently uploaded almost 60 GB of data to a FTP server without a single issue. The only other likely cause could be your internet connection messing up, next time it happens just powercycle either the router or the DSL but not both and see if it improves, that way you will know which device is causing it.

Actually, now that you mention it, i have not had this problem in the past until I did a Firmware Update on the router.

It wasn't an ElCheapO router, got it off TigerDirect for about $250 a year ago... Linksys WRVS4400N

Could have been something screwry with the firmware...

Linksys does not have a good reputation for firmware support.

Interesting. I've had issues trying to set up a working passive FTP server from my Ubuntu box, and I'm working through a LinkSys router as well (an old cheap one, BEFW11S4v4).

In passive mode, I keep getting a \"425: Bad IP Connecting\" error when the client tries to get a directory listing. Made sense because it was passing my local 192.168.1.* IP back to the client, but now it even fails with the \"PASV_ADDRESS = x.x.x.x\" setting in place.

I may try changing firmware, and I'll post if I have any success.

In order for Passive FTP to properly work, the server has to know what its EXTERNAL IP address is (meaning the IP internet servers see you as). So for instance if my server was running internally on 192.168.12.34 and its internet IP was 12.34.56.78 the server would have to have its passive IP set to 12.34.56.78. But that isn't all, by default passive FTP uses a random port greater than or equal to 1024, most servers let you configure a smaller range than that (which is generally a better idea than opening all of 1024-65536).

So if you just give your server a passive IP but don't also forward a port range to it, passive will not work. On my own server in the past I have used the range 28000 to 28100 and had no problems.

Hm, that may be the issue for me. I am returning my correct external IP (I even had a friend check it), but my port range may not be forwarded correctly. Thanks, Krom.

Interesting, thanks for the info Krom. Still not sure why it worked fine before the firmware update.

Mabye because the router was passing my public IP before, but after the update, its changed to an internal one.

Who knows - as long as it works (under \"active\") then im fine!

Thanks again!