Leaderboard

I believe the 3rd character in the 10th line of your code is wrong. On a more serious note without any details what the server expects and how you tried to connect we can not help.

The profilers for 64 bit applications developed with Delphi XE2 up to Delphi 12 and for 32 bit applications developed with Delphi 5 up to Delphi 12 are released. ProDelphi mesures 32 bit applications, ProDelphi64 measures 64 bit applications. Prodelphi6432 measures both. All ProDelphi versions measure how many CPU-cycles a method (procedure or function) uses during execution. Measurement is independent from CPU mode at execution time (normal, boost or power save mode). Even a mode change during execution does not matter! After measurement the cycles are converted into time units by the viewer considering the CPU speed. UI languages selectable: English, German, Dutch, French, Italian Downloads of the limited Freeware Version measuring 20 methods are available at https://www.prodelphi.de. The professional version can measure up to 65500 methods.

What are the EXACT error messages? What EXACTLY did you try? What are your EXACT property settings? Umm, you are comparing a higher-level APPLICATION to a lower-level LIBRARY. Of course, a LIBRARY is going to be more flexible and thus require more configuration for meet your particular situation. Seems simple enough. Please show the EXACT code you are trying to use to accomplish that. Then you don't have TIdFTP setup correctly to match your server's requirements. Those are not the only settings involved. What ELSE do you have configured EXACTLY? Well, then you should have no trouble grabbing logs from CoreFTP and TIdFTP and compare them for differences. At what stage EXACTLY in the communication is the failure actually occurring? There are several different possibilities, which is why more DETAIL is needed. Probably, but without any DETAIL about your setup or your server's requirements, there is simply no way for anyone here to know for sure what is actually wrong/missing. Provided the server is actually reachable and responsive, most often a timeout error on a connect is due to a mismatch between the Port and UseTLS properties, causing Indy to wait for a server greeting that is never sent because the server is waiting for a TLS handshake from the client first. Again, what is the EXACT error message? Is it an FTP-level error or a TLS-level error? You can't set the UseTLS property to Explicit (or Implicit) without having an SSLIOHandler assigned first.