I'm running PHP/5.0.3RC1 under Apache 2.052 in WinXP, SP2.

I get the following warning messages:

Warning: ftp_get() [function.ftp-get]: Transfer complete - file {private - edited out} sent successfully in C:\Documents and Settings\Abu Hurayrah\Desktop\Web Development\TSI\ftp_test.php on line 45

DEBUG: There was an error retrieving and downloading file {private - edited out}

The filename DID have spaces in it - but it works on some, and not on others.  Go figure!  I suspect it might have something to do with timeout, because the first 114 files seem to have downloaded without error, and the files that couldn't be downloaded were the last ones.

I also realize I'm running a release candidate (forgot that I was), and I will update the shortly and see if it solves anything.

Just to confirm, I have updated to the official release on PHP 5.0.3, and I am experiencing exactly the same errors.  Once again, my loadout is the following:

Apache/2.0.52 (Win32) PHP/5.0.3 WinXP SP2

I tried it again on another machine, and this time, it did not happen - the only difference is that that machine doesn't have SP2, only SP1 (i.e., WinXP, Apache 2.052, PHP 5.0.3 ), so maybe SP2 is limiting connections, which I think is a "feature" they added.  I'll see if I can change that setting and get the problem solved.

I've discovered that the cause of this bug, at least in my case, had to do with WinXP SP2 limiting the number of simultaneous connections per port to 10 per second, as a safety feature to prevent the spread of viruses/worms that attempt connections of this sort (i.e., searching for random IPs and trying to connect and exploit a weakness).

So, perhaps it is the case that this bug is caused by the system itself limiting connections in this manner.

Please try using this CVS snapshot:

  http://snaps.php.net/php5-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5-win32-latest.zip

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".