I have a Windows Server 2016 machine with FTP Server role installed, an FTP site added, and FTP Server rules added in Windows Firewall. I can connect via FTP locally like via command line like this:

ftp localhost  
Connected to *redacted*.  
220 Microsoft FTP Service  
200 OPTS UTF8 command successful - UTF8 encoding now ON.  
User (*redacted*:(none)): Administrator  
331 Password required  
230 User logged in.

However, when I try to connect to the server's IP address via Filezilla on my own computer using both FTP or SFTP it tries to connect for a while then the connection times out. Anything I might be missing? Thanks.

  • 1
    Have you opened the port(s) on the firewall? – Zac67 Oct 20 '17 at 18:57
  • 1
    Well SFTP is not supported in IIS normally it would be FTPS as for remotely hitting FTP I would make sure you don't have a network firewall between your client and server. – SpiderIce Oct 20 '17 at 19:08
  • 1
    You might have a local firewall at your pc or router preventing ftp connection. Or the issue might be with the remote's server topology. You should provide more details about your local network's and server's networking in order to receive more thatn a general help. – Marco Oct 20 '17 at 19:11
  • Would help, if you show us verbose FileZilla log file. – Martin Prikryl Oct 20 '17 at 19:14
  • 1
    port 21 is closed on your IP, traceroute your IP from your client to make sure you know whats between your client and server. to rule out your windows firewall you might want to disable it for a quick test. – SpiderIce Oct 20 '17 at 19:41

(disclaimer: the links go to my guide on Installing a Secure FTP Server on Windows using IIS)

  • All 3 server rules are enabled, I restarted the FTP service and also rebooted the machine, and I added its external IP address in the indicated position. Unfortunately, I still can not connect to the server via FTP. – Aaron T Oct 20 '17 at 19:27
  • 1
    Your last point was it. I assumed that my provider would have the port open by default, but I verified that the firewall policies on the hosting account itself did not have port 21 open. I created a rule to open it, and now I can connect via FTP (albeit I get another error which I'm looking into). Thanks. – Aaron T Oct 21 '17 at 5:43

Once Port 21 is open for FTP, the user mentions another issue. I suspect the issue is with File Transfers. This is likely due to Port 20 not being open. Port 20 is used for data transfer.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.