Windows FTP and PERL Script uploading problems...

Hello,

I have a perl script that monitors a directory and
whenever a new file is put in there, it will connect to a
FTP site and upload that file.

Unfortunately, sometimes the FTP server tells me that the
File received OK but does not display XXXX bytes sent in
X.XX seconds. When this happens, the file does NOT get
sent correctly.

Here are my logs for

SUCCESSFUL:
ftp> ftp> lcd r:\
Connected to X.com.

open X.com
220 This system is restricted to authorized users.
Individuals attempting unauthorized access will be
prosecuted. If unauthorized, terminate access now.
User:
331 Please specify the password.

230 Login successful. Have fun.
ftp> ftp>
put file.ext
200 PORT command successful. Consider using PASV.
150 Go ahead make my day^W^W^Wsend me the data.
226 File receive OK.
ftp: 4402 bytes sent in 0.19Seconds 23.41Kbytes/sec.

ftp> ftp>
bye
221 Goodbye.

--------

UNSUCCESSFUL:
ftp> ftp> lcd r:\
Connected to fdde1ftp01.fand.com.

open ftpmain.fand.com
220 This system is restricted to authorized users.
Individuals attempting unauthorized access will be
prosecuted. If unauthorized, terminate access now. FAND
User (fdde1ftp01.fand.comnone)):
331 Please specify the password.

230 Login successful. Have fun.
ftp> ftp>
put d:\fand\7028518.LDR
200 PORT command successful. Consider using PASV.
150 Go ahead make my day^W^W^Wsend me the data.
226 File receive OK.
ftp: 4629 bytes sent in 0.20Seconds 22.80Kbytes/sec.

ftp> ftp>
bye
221 Goodbye.
ftp> ftp> lcd r:\
Connected to X.com.

open X.com
220 This system is restricted to authorized users.
Individuals attempting unauthorized access will be
prosecuted. If unauthorized, terminate access now.
User:
331 Please specify the password.

230 Login successful. Have fun.
ftp> ftp>
put file.ext
200 PORT command successful. Consider using PASV.
150 Go ahead make my day^W^W^Wsend me the data.
226 File receive OK.
ftp> ftp>
bye
221 Goodbye.

---------

As you can see, the "ftp: 4629 bytes sent in 0.20Seconds
22.80Kbytes/sec." is missing.

This only began happening after I upgraded to 2003 Server.

Anybody have a solution to this? This problem happens
probably 1/6 times per FTP connection...