FTP gotcha - how do you ignore a socket error?

[Dave Cragg]

On 21 Sep 2005, at 20:44, Jim Ault wrote:

> I am working on two trusted computers, getting a successful file  
> transfer,
> but then the following error on the Windows client (Mac OSX Jaguar  
> ftp host)
> about 8 seconds later
> -------------------
> 226 Transfer complete.
> QUIT
> 221-
> Data traffic for this session was 1700 bytes in 1 file.socket error
> 24.234.190.204:21|6930
> Error 10053 on socket
>     Total traffic for this session was 2342 bytes in 1 transfer.221
> Thank you for using the FTP service on localhost.
> CLOSED 24.234.190.204:21|6930
> CLOSED 24.234.190.204:21|6930
> -----------------------------
>
> Client > Win XP Pro, McAffee, Rev 2.5.1  (plus compiled versions)
>
> Firewall FTP 21-22 was tried as [ON + OFF = same error] [McAffee]
> compiled app was registered as trusted source [McAffee]
> host static IP registered as trusted IP [McAffee]
>
> The transfer is good, and I would like to just ignore the error and  
> let a
> loop continue about once every 60 seconds.

I think you can probably ignore it. (The 226 line signals the end of  
the transaction.) But things like that make me nervous. :-)

"Error 10053 on socket" is a Windows error, and means something on  
the local computer caused the connection to close.

Something you might want to check. The ftp QUIT command is issued by  
libUrl if, after a transaction completes, there is no activity on the  
socket for 15 seconds. In case there is something on your machine  
that doesn't like the socket remaining unused for so long, you can  
change the delay to less than 15 seconds by using libUrlSetFTPStopTime.

    libUrlSetFTPStopTime 2 ## put somewhere before your ftp call

This will reduce the delay to 2 seconds.

You might want to see if it makes a difference.

Cheers
Dave