FTPES server stops at LIST command in Filezilla

[foges]

Im running an FTPES server at home and i tried to connect to it from a remote client (ie. computer not on my home network) and i get the following:

--------------
Status: Connecting to xx.xx.xx.xx:21...
Status: Connection established, waiting for welcome message...
Response: 220 Welcome to Server
Command: AUTH TLS
Response: 234 Using authentication type TLS
Status: Initializing TLS...
Command: USER admin
Status: Verifying certificate...
Status: TLS/SSL connection established.
Response: 331 Password required for admin
Command: PASS **********
Response: 230 Logged on
Command: PBSZ 0
Response: 200 PBSZ=0
Command: PROT P
Response: 200 Protection level set to P
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,9,16,78)
Command: LIST
Response: 425 Can't open data connection.
Error: Failed to retrieve directory listing
Error: Disconnected from server
--------------

Clearly it is getting through my cable modem to my computer, but why wont the LIST command work? It does work on my home network if i connect to 192.168.1.9 (my server's ip address)

 

[spidey07]

Google "ftp nat data channel"

It's a common problem. You'll just have to setup your port forwarding and server correctly.

 

[Goosemaster]

Not familiar with what ftpes is, but as far as ftps (ftp w/ ssl or tls) you will need to have two ports open/translated, one for data and one for control. As spidey said, it is a common oversight and should be easily fixed.

 

[foges]

FTPES is FTP over explicit ssl/tsl, well according to filezilla at least.

Thanks for the replies, i guess i should have read up more on the protocol before setting it up. I fixed it by setting the port range for passive mode and then adding that range to my port forwarding range in my router

 

[Goosemaster]

Originally posted by: foges
FTPES is FTP over explicit ssl/tsl, well according to filezilla at least.

Thanks for the replies, i guess i should have read up more on the protocol before setting it up. I fixed it by setting the port range for passive mode and then adding that range to my port forwarding range in my router