I am trying to connect to FTP on a new virtual machine in Azure.
I created a new default virtual machine (Windows Server 2012 Datacenter) and RDPed into a new virtual machine. Then I enabled the web server (IIS) role, including the FTP server and configured IIS, using the recommended setting from the web platform installer. Then I used the IIS Manager "Add FTP Site ..." IIS Manager to add an FTP site with root %systemdrive%\inetpub\ftproot and set up anonymous authentication for the ftp site, allow anonymous users read access, provide a range of channel ports 7000-7014 data and specify the external IP address of the firewall as a public virtual IP address (VIP) from the virtual machine control panel on the Azure management portal.
A firewall is also configured to allow an FTP server.
At this point, the FTP service is running. I know, because if I open a command prompt in a virtual machine in an RDP session, I get the following
C:\Users\slife>ftp 127.0.0.1 Connected to 127.0.0.1. 220 Microsoft FTP Service User (127.0.0.1:(none)): ftp 331 Anonymous access allowed, send identity (e-mail name) as password. Password: 230 User logged in. ftp>
However, I cannot connect from other sources.
C:\Users\timregan>ftp 111.111.111.33 Connected to 111.111.111.33. Connection closed by remote host.
What from the command line in FileZilla do I get
Status: Connecting to 111.111.111.33:21... Status: Connection established, waiting for welcome message... Error: Could not connect to server
I followed the Ronald door Walkthrough: FTP hosting in IIS 7.5 on Windows Azure VM and added two endpoints to allow access to ports 21 (FTP port) and 20 (FTP data port), and I used its Azure Powershell offer to add passive port endpoints for example
Get-AzureVM -ServiceName 'blah' -Name 'blah' | Add-AzureEndpoint -Name 'FTPPassive00' -Protocol 'TCP' -LocalPort 7000 -PublicPort 7000 | Update-AzureVM
which I can then see in the list of Azure management endpoints for the virtual machine.
Why don't my connections reach the FTP server in IIS from the outside? How can I diagnose a failure?
=========== EDIT 1 ===========
I wondered if the solution that worked for haxor could solve the problems. This refers to Azure Server 2012 VM's answer - Passive FTP will not work on the Windows Azure Virtual Machines forum, which notes that if the probe is configured by the Azure Portal on passive endpoints, then they may not work. Although the answer notes that this has been fixed in the latest version of the portal, it is suggested that you use the Azure Powershell Add-AzureEndpoint cmdlet to ensure that the probe is not running. I checked with the Azure Powershell cmdlet Get-AzureEndpoint, and none of my ftp endpoints have probes, so this is not my problem.
=========== EDIT 2 ===========
I noticed a step in Passive FTP and dynamic ports in IIS8 and Windows Azure Virtual Machines not mentioned in the original walkthrough : open the data channel port range (7000-7014) in the Windows firewall. For this, I added an inbound rule. I still cannot connect.