Ошибка 501 ftp

I am running IIS 8.5 on Windows 2012 R2.

I created an FTP site to use port 8021 and when trying to connect using FileZilla (plain FTP), I get the error message «Connection timed out after 20 seconds of inactivity. Failed to retrieve directory listing». I am using Active mode in FileZilla, but in FileZilla connection window it shows that it automatically switches to Passive mode. Any idea why? Do I have to configure anything in IIS to not use Passive mode?

14:19:39    Status: Connecting to ip:8021...
14:19:40    Status: Connection established, waiting for welcome message...
14:19:41    Status: Logged in
14:19:41    Status: Retrieving directory listing...
14:20:02    Command:    PWD
14:20:02    Response:   257 "/" is current directory.
14:20:02    Command:    TYPE I
14:20:02    Response:   200 Type set to I.
14:20:02    Command:    PORT 10,0,1,16,5,64
14:20:02    Response:   501 Server cannot accept argument.
14:20:02    Command:    PASV
14:20:02    Response:   227 Entering Passive Mode (ip,250,68).
14:20:02    Command:    LIST
14:20:02    Response:   150 Opening BINARY mode data connection.
14:20:02    Error:  Connection timed out after 20 seconds of inactivity
14:20:02    Error:  Failed to retrieve directory listing

Thanks in advance.

Update: Tried Passive mode and still no luck,

09:27:20    Status: Connecting to ip:8021...
09:27:21    Status: Connection established, waiting for welcome message...
09:27:22    Status: Logged in
09:27:22    Status: Retrieving directory listing...
09:27:42    Command:    PWD
09:27:42    Response:   257 "/" is current directory.
09:27:42    Command:    TYPE I
09:27:42    Response:   200 Type set to I.
09:27:42    Command:    PASV
09:27:42    Response:   227 Entering Passive Mode (ip,193,17).
09:27:42    Command:    LIST
09:27:42    Response:   150 Opening BINARY mode data connection.
09:27:42    Error:  Connection timed out after 20 seconds of inactivity
09:27:42    Error:  Failed to retrieve directory listing

Update: Solved!
https://www.iis.net/learn/publish/using-the-ftp-service/configuring-ftp-firewall-settings-in-iis-7

Added port range to IIS FTP Firewall Support for server node and opened port range in external firewall to allow Passive Mode. Thanks Martin for pointing out

Настроил на сервере 2008R2 FTP, прописал правила в брандмауэре на порты. Внутри сети все открывается, с внешних не хочет. Набираешь адрес, выскакивает окно запроса логинапароля, вводишь и появляется ошибка:

В ходе открытия папки на FTP-сервере произошла ошибка. Убедитесь, что у вас есть разрешение открывать эту папку.
Подробности:
200 Type set to A
501 Server cannot accept argument.

Прокси никакой нету, инет на сервер идет через шлюз TP-Link ER 5110. В нем через virtual server настроен проброс на сервер. Что это может быть и что мешает коннекту?

Range Purpose 1xx Positive Preliminary reply

The requested action is being initiated; expect another reply before proceeding with a new command. (The user-process sending another command before the completion reply would be in violation of protocol; but server-FTP processes should queue any commands that arrive while a preceding command is in progress.) This type of reply can be used to indicate that the command was accepted and the user-process may now pay attention to the data connections, for implementations where simultaneous monitoring is difficult. The server-FTP process may send at most, one 1xx reply per command.

2xx Positive Completion reply

The requested action has been successfully completed. A new request may be initiated.

3xx Positive Intermediate reply

The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information. The user should send another command specifying this information. This reply is used in command sequence groups.

4xx Transient Negative Completion reply

The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. The user should return to the beginning of the command sequence, if any. It is difficult to assign a meaning to «transient», particularly when two distinct sites (Server- and User-processes) have to agree on the interpretation. Each reply in the 4xx category might have a slightly different time value, but the intent is that the user-process is encouraged to try again. A rule of thumb in determining if a reply fits into the 4xx or the 5xx (Permanent Negative) category is that replies are 4xx if the commands can be repeated without any change in command form or in properties of the User or Server (e.g., the command is spelled the same with the same arguments used; the user does not change his file access or user name; the server does not put up a new implementation.)

5xx Permanent Negative Completion reply

The command was not accepted and the requested action did not take place. The User-process is discouraged from repeating the exact request (in the same sequence). Even some «permanent» error conditions can be corrected, so the human user may want to direct his User-process to reinitiate the command sequence by direct action at some point in the future (e.g., after the spelling has been changed, or the user has altered his directory status.)

6xx Protected reply

RFC 2228 introduced the concept of protected replies to increase security over FTP communications. The 6xx replies are Base64 encoded protected messages that serves as responses to secure commands. When properly decoded, these replies fall into the above categories.

Code Explanation 100 Series The requested action is being initiated, expect another reply before proceeding with a new command. 110 Restart marker replay . In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm where yyyy is User-process data stream marker, and mmmm server’s equivalent marker (note the spaces between markers and «=»). 120 Service ready in nnn minutes. 125 Data connection already open; transfer starting. 150 File status okay; about to open data connection. 200 Series The requested action has been successfully completed. 202 Command not implemented, superfluous at this site. 211 System status, or system help reply. 212 Directory status. 213 File status. 214 Help message. Explains how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user. 215 NAME system type. Where NAME is an official system name from the registry kept by IANA. 220 Service ready for new user. 221 Service closing control connection. Logged out if appropriate. 225 Data connection open; no transfer in progress. 226 Closing data connection. Requested file action successful (for example, file transfer or file abort). 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2). 228 Entering Long Passive Mode (long address, port). 229 Entering Extended Passive Mode (|||port|). 230 User logged in, proceed. 232 User logged in, authorized by security data exchange. 234 Server accepts the security mechanism specified by the client; no security data needs to be exchanged. 235 Server accepts the security data given by the client; no further security data needs to be exchanged. 250 Requested file action okay, completed. 257 «PATHNAME» created. 300 Series The command has been accepted, but the requested action is on hold, pending receipt of further information. 331 User name okay, need password. 332 Need account for login. 334 Server accepts the security mechanism specified by the client; some security data needs to be exchanged. 335 Server accepts the security data given by the client; more security data needs to be exchanged. 336 Username okay, need password. Challenge is «….». 350 Requested file action pending further information 400 Series The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. 421 Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down. 425 Can’t open data connection. 426 Connection closed; transfer aborted. 430 Invalid username or password 431 Need some unavailable resource to process security. 434 Requested host unavailable. 450 Requested file action not taken. 451 Requested action aborted. Local error in processing. 452 Requested action not taken. Insufficient storage space in system. File unavailable (e.g., file busy). 500 Series Syntax error, command unrecognized and the requested action did not take place. This may include errors such as command line too long. 501 Syntax error in parameters or arguments. 502 Command not implemented. 503 Bad sequence of commands. 504 Command not implemented for that parameter. 530 Not logged in. 532 Need account for storing files. 533 Command protection level denied for policy reasons. 534 Request denied for policy reasons. 535 Failed security check. 536 Data protection level not supported by security mechanism. 537 Command protection level not supported by security mechanism. 550 Requested action not taken. File unavailable (e.g., file not found, no access). 551 Requested action aborted. Page type unknown. 552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset). 553 Requested action not taken. File name not allowed. 600 Series Replies regarding confidentiality and integrity 631 Integrity protected reply. 632 Confidentiality and integrity protected reply. 633 Confidentiality protected reply. 10000 Series Common Winsock Error Codes^[2] (These are not FTP return codes) 10054 Connection reset by peer. The connection was forcibly closed by the remote host. 10060 Cannot connect to remote server. 10061 Cannot connect to remote server. The connection is actively refused by the server. 10065 No route to host / DNS cannot be resolved. 10066 Directory not empty. 10068 Too many users, server is full.