Hello, <p>Has anyone figured this out? I am having the same problem. My network guy insists that we should not have to open a port on the fire wall since it is a client ftp. <BR>
If we do have to open a port which one? 20? <p> This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

Port 21 is the command port. In order to actually send data, though, you need a second port. AFAIK, passive mode means that the FTP server will tell you which port to listen to. Otherwise, you need use port 20. <p>I know I'm screwing up this explanation, but stay away from passive mode and give port 20 a shot. Let me know how it goes, and if it doesn't work I'll try to give you a more complete explanation. <p>Joe

Hi all, <p>I am trying a access a secure FTP server (Unix box) from AS/400 (*SSL). <p>After logging on successfully, I am NOT able to perform: DIR/LS/PUT commands. After executing the command, the screen hangs and after 3 - 5 minutes, gives an error of 425 - cannot open data connection. I've tried turning off Passive mode and still getting same error. <p>I found a very similar post on the forum where it turned out to be a firewall issue see following paragraph: <BR>
&nbsp;&nbsp;***Finally i solved the problem.Its related with Firewall.I checked the firewall filters for FTP permissions. But we have to change the process specifically for FTP if the data passes thru the Firewall*** <BR>
I was hoping someone can be more specific and provide more details of what I need to check. Is it something I need to do on my side (AS/400) or Client's side (Unix). I have other FTP jobs running and never had this problem before. <BR>
Thank you for your help !!

I have been doing FTP’s for years bust this SSL stuff is making me look like a newbie -- how do a specify a port to send/receive the data on? I thought that SSL negotiated the port that the data would be sent on.