Core FTP

We download a file daily that usually works without an issue. Some days we have to try several times before the file will download. There are no issues with connecting and browsing to the directory where the file is located. When the file downloads correctly, it begins right away. when we have problems, it will not download, but hang a transferring file. after about a minute, there will be a timeout error. Working with the FTP Servers tech team, I was able to get a response from the FTP Server Team.

Here is the response that I get

BEGIN RESPONSE*************

Each time you connect with us to retrieve the file, immediately after we receive the path and the command to CWD (Change Working Directory), we then get a command to “closefileâ€￾
04/17/2014 12:36:34 PM|[SFTP:667396:M00005:***.***.***.***] WROTE: *250 "/M00005/M00005_EReports/EReports/" CWD command successful.*
04/17/2014 12:36:34 PM|[SFTP:667396:M00005:***.***.***.***] READ: *closeFile
After the “closefileâ€￾ is received, the connection just hangs.
Notice we wrote the command CWD successful and then READ the closefile message

We have logged in with Core FTP and downloaded the file successfully with no issues.

END RESPONSE ******



My question would be, is the *closefile coming from core ftp ?

using CoreFTP 2.2 build 1778.

I will also state that we are also trying to download using winscp with the same results. I am just trying to determine if the issue is on our side or the FTP server's side

I have an ssh/sftp site setup in CoreFTP lite 2.2 1765 and I can upload files just fine manually through the GUI. However, when try to upload via the command line, files do not get uploaded and the log indicated permission denied. Watching the process, I can see the file move to the right side for a...