FTP shows Connection Closed by Remote Host

May 3, 2011 at 01:01:50
Specs: Windows XP
Actually the client use AS400 FTP to our FTP server and the FTP seems has come in to our server but with zero byte. After that when customer try to FTP the second time, it can replace the zero byte file, but when our engine try to read and process it, it is failed because the first file is being held by the FTP engine and cause it hang. That is why it shows the process is being used by another process. So now, we need to manually restart the FTP server to allow the engine run.

Any idea on if the first file is being held by the FTP engine, can it automatically detect and cut off the holding process and allowed to accept for the second try without restart the FTP engine?

Does it due to line connection problem? Usually is happen to the same file.


See More: FTP shows Connection Closed by Remote Host

Report •

#1
May 3, 2011 at 07:46:34
Most likely, the first FTP session never get's closed correctly.
This could be caused by an incorrect configured firewall between the FTP server and the accessing client.
Have you already checked the FTP log files.
Don't ask me on where to find the FTP logs on AS400, that's your turn.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#2
May 3, 2011 at 20:06:02
check already, but the log shows No response from remote host, all connections closed.

But it is unstable, sometime ok sometime failed. and it is happen on the same files.

Do you have any idea on it?

Thank you.


Report •

#3
May 3, 2011 at 22:22:10
You say, that this always happens on the same files and that it is working sometimes.
So the main question is, what type of files is it and what happens to the files and maybe which application is working with the files, when FTP gets timeout on it?

Maybe one application makes changes to the files while someone is trying to download the file via FTP.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

Related Solutions

#4
May 4, 2011 at 01:01:50
Thank you for replying. The situation is like this: client use 2 public IP FTP to my server. IP: A & IP: B. Numbers of file they FTP in is 5 files. If client use IP A, all files will be come in successful. But if client use IP:B, some file come in successfully but some file may not be fully transfer. Those file not fully transfer will shows zero byte in our server. And they need to manually resend FTP fail file to us again.

Does this due to client internet problem or any other issue that cause this?

I have open port 20 & 21 to allow incoming FTP but still face this problem.

Thank you.


Report •

#5
May 4, 2011 at 01:17:48
If you are using a SOHO router with build in firewall, you normally only have to open port 21 or, if the server has a private ip and is behind this routers firewall, you have to forward port 21 to the FTP servers private ip address and port 21. Stateful packet filtering (in most SOHO routers) do automatically open the other ports, needed for ftp session temporarily.

While the user uses 2 public ip addresses, do the problem occure always at the same ip address?
If yes, let the user try to use the working ip address, to transfer the files in question.
Btw: Why does the user use 2 different public ip addresses to access your FTP?

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#6
May 10, 2011 at 01:59:33
Hi
The reason they use 2 ip is because of load balancing. They can't choose only to use the working IP because it will locate automatically. But, usualy it will happen to the same file.
We notice after the file name if it is success connect it will shows 200 follow by a set of number, if it is fail connection it will shows 499 can't open connection to client. We are wondering the figure of 200 & 499 is showing some hint? Do you have any idea on this?

Thank you.


Report •

#7
May 10, 2011 at 03:31:47
Status codes:

100-199
ftp command was successful, server is waiting for the next ftp command.

200-299
ftp commands had been running successfully

300-399
ftp command were sucessful, server is waiting for further commands, to successfully end the ftp session.

400-499
ftp command was not successful. This might be a temporary problem. Rinning the ftp command again may run successfully.

500-599
error on ftp command. A retry of the same command will end up in the same error.

Depending on the exact status code between 400 and 499 may give a better hint.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

Ask Question