FTP file transfer error

Topic

New Reply

I’m downloading 12 files via cmd line ftp and script file. Has worked for years. Now, when it gets to file #2 in download, ftp displays size of file as 140 Trillion bytes, when it’s actually 10k. Script stops on this file, sits about a minute, then disconnects. I can download this file using CuteFTP. I have deleted this file. It routinely gets deleted and resent everyday. But on this one PC, ftp is stuck on the 140 Trillion file size and will not download. Go to another PC, run same script, works perfectly.

Any suggestions?

Seems like there’s something I need to reset somewhere.

tia –

Reply | Quote

Replies

Nylla,

Just a shot-in-the-dark but you might try clearing all your internet caches. HTH :cheers:

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Just a shot-in-the-dark but you might try clearing all your internet caches.

Sounds good to me. Anyone want to give me a refresher on how to do that? Go to cmd line and run

ipconfig /?????

Also, is this one of those occasions when you would delete the Hosts file? If so, where is the Hosts file or what’s it’s official name.

thanks again

Reply | Quote

Nylla,

The easiest way is to use CCleaner and use the Cleaner button the default settings should clean things up.
34182-ccleaner_settings

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Well, I figured out my problem tonight. It’s a long story. First I don’t work in this office. I’m remote tech support. This problem has been there for over a year, but no one told me. So when I made a recent change and noticed problem while testing changes, assumed recent change had caused problem. Wrong.

Problem is the filename on GoDaddy’s ftp server was in ALL CAPS, but the ftp script was using upper/lowercase mix. We use two different ftp servers so that if one fails, we have the other. Every night all sends are sent to both. All locations have two get scripts – one for each server. The other server ignores case and this is not a problem on that server. So office personnel had just been using the one server for over a year without reporting a problem.

Tonight, I went in script and moved the “bad” file get to bottom of list. Script then ran for 4 files before failing. Moved next failure to bottom. Etc. Then used CuteFTP to figure out what bad files had in common. Which was all caps. Thanks for your efforts at helping.

later –

Reply | Quote