![filezilla cannot retrieve directory listing filezilla cannot retrieve directory listing](https://i.stack.imgur.com/rfN2j.jpg)
So adding that configuration statement should resolve the problem with FileZilla not getting the LIST output. If you are having problems with setting up FileZilla Server to run behind Windows Firewall (specifically, it fails on 'List' and the client receives a 'Failed to receive directory listing' error), you must add the FileZilla Server application to Windows Firewalls Exceptions list. I have a passive port range set in ISS and the range is. Error: The data connection could not be established: ECONNREFUSED - Connection refused by server. Response: 150 Opening BINARY mode data connection. Response: 227 Entering Passive Mode (,252,122).
![filezilla cannot retrieve directory listing filezilla cannot retrieve directory listing](https://i.stack.imgur.com/vWR5x.png)
Apparently the GnuTLSĬode used by FileZilla is strictly enforcing receipt of the alert, and errors out when a FIN arrives without the alert. Response: 501 Server cannot accept argument. Specifically, configuring TLSRFCLEVEL RFC4217 will cause an SSL Close alert packet to be sent before actually closing the TCP connection (sending the FIN). Ready dlna do the same, log in then crash I used to be able to connect by FTP with previous firmware. Same with remote, whatever cifs or FTP mode, I login but it fails reading shares. I log in correctly but then failed to retrieve the shares and stop. Specification of the TLSRFCLEVEL does not affect the initial SSL handshake or encryption of traffic it changes the behavior when a session (or at least, SSL) ends. I remark that I am not able to retrieve the directory listing with FileZilla by FTP. If it defaulted to DRAFT, add a TLSRFCLEVEL RFC4217 statement to the server's FTP.DATA input to change this behavior.
![filezilla cannot retrieve directory listing filezilla cannot retrieve directory listing](https://www.greengeeks.com/blog/wp-content/uploads/2016/11/quickconnect7-1024x456.jpg)
If your TLSRFCLEVEL is configured as DRAFT, change it to TLSRFCLEVEL RFC4217. One effect of this is that the session is simply closed instead of first sending an SSL Close Alert message first. In this situation it was found that the FTP server was configured (defaulted) to the draft level of the FTP/TLS RFCs.