The 425 error means that the data channel is blocked or closed between you and the server you are trying to connect to.
For Active connections open ports 20 and 21
For Passive connections open ports 21 and 1024+ (and higher)
Also, turn off command filtering on the firewall.
If you still cannot get a successful connection, check all devices that are between the client and server to ensure that the proper ports are open (e.g. routers).
"I am getting 425 connection errors when trying to connect to my WS_FTP Server. What is going on?"
Answer/Solution: This error means there is no connection being made between the server and your ftp client.
The best way to troubleshoot this is to work your way from the server to the "outside world" one step at a time. In order to do this, please do the following:
Try to connect to the server locally by going to a DOS prompt on the ftp server and entering "ftp localhost". If you cannot connect locally, make sure that you don't have another ftp server running on the machine. If you don't, you have a network problem that is preventing you from connecting to port 20 and you need to contact your network administrator about it.
If you can connect locally, shut off any firewall that may be blocking the connection and try to connect from another internal machine. If you can't shut off the firewall, make sure that ports 20 and 21 are open in the firewall. They both need to be open in order to connect to the server.
Once you can successfully connect both locally and from another internal machine, you can test whether or not you can connect from an external machine. Problems connecting from an external machine usually result from a DNS configuration problem or from a firewall or router problem.
You can use the DOS traceroute command to determine the problem. The traceroute command (syntax: tracert IPaddress) will show you where problems are occurring in the path between the ftp client and the ftp server.
Question/Problem: My firewall does command filtering. How can I get SSL for an ftp connection to work correctly through the firewall?
Answer/Solution: You will need to turn off command filtering on your firewall in order for SSL to work. Once SSL is enabled all communication between the server and client will be encrypted. The firewall has no way of decrypting the information being sent. For this reason, the firewall will reject the encrypted information even if the AUTH SSL command is allowed through the firewall.
Hope this might help you in tracing your problem..
