PutFile Timeout on Core FTP Server (General questions)

I've built some code that I use to automate file transfers to various trading partners. All are working fine until this new one. At the PutFile step I always receive this error:

-2146818228 The current connection has timeout.

The only difference I know of between this trading partner and all others is that this one is using CoreFTP Server. I can connect to his server using FileZilla and transfer files but not through wodFTP code.

Any thoughts on what to look into?

Thank you,
Cliff

Hi Cliff,

I will try to duplicate it now.

What protocol did you use to connect to Core FTP Server?

Regards,
Drazen

I'm using standard FTP: protocol set to 0. It is a Active FTP connection. Regular port of 21.

In my little app I set Blocking = True so the only error I get is at the actual error spot.

I'm about to see if I can download Core FTP Server also to see if I can reproduce it and get more information.

The trading partner tells me that his log shows that I'm trying to change to a directory that includes the filename. For example, if I set RemotePath = /Inbox/Testfile.txt he's saying I'm trying to change to the directory /Inbox/Testfile.txt . I'm not actually issuing any CWD commands. I just set LocalPath and RemotePath and call PutFile.

Thanks
Cliff

Hi Cliff,

Please set Compression Property to 0. That should fix your problem.
[code]
ftpdlx1.Compression = 0
[/code]

More help for Compression Property you can find here:
http://www.weonlydo.com/FtpDLX/Help/wodFtpDLXLib~wodFtpDLX~Compression.html

Let us know how it goes.

Regards,
Drazen

Funny, I found that setting just before you replied. And it almost solves the problem. I downloaded Core FTP Server. I found that disabling Mode Z on the server fixed PASV connections. That's when I found the Compression setting. So with Mode Z enabled on the server and Compression = 0 then PASV connects appropriately. I tried this with my trading partner and it still won't work. I'll talk with him about that.

But another item is that Active transfers still don't work. On the Core FTP activity it issues a PORT command and sits there until it times out. Active mode will work with Filezilla. Any thoughts about this idea?

Thank you,
Cliff

Addtional Info: On the trading partner when using PASV mode I get the following error on PutFile:

-2146798259 Component was busy while disconnected by the server.

Cliff

Cliff,

Did you set Blocking = True?

Drazen

Yes, Blocking is set to True.

Cliff

Cliff,

seems that Core FTP doesn't reply on PORT command with 200 response, but decides to use 250. By RFC specification from 1985

http://www.faqs.org/rfcs/rfc959.html

you will see that correct response to PORT is 200 - thus component is confused and awaits wrong response. Since 250 is also used during data file transfer, component expects 250 to close the data which doesn't happen - and it times out.

I will see how easy/hard is to make workaround for this, but you should mark this complaint to Core FTP authors to be fixed.

Hope I helped.
Kreso

Ok. Sounds good on the Active connection, well, good to know what it is. I'm also having problems with a Passive connection but it looks to be a configuration of the firewall on the trading partners end. Thank you for all of your efforts.

Cliff