When trying to connect with an IIS FTP site that I created in IIS remotely, I am not able to connect.

Question

_{Friday, August 5, 2016 1:14 PM}

I have created an FTP site on my Windows 10 PC using IIS. I have followed this tutorial to the T: https://www.youtube.com/watch?v=Cd2k9nQSdro

I am able to connect to the server within my LAN, but using the public IP address in Chrome only yields this result: 

This site can’t be reached

ERR_CONNECTION_TIMED_OUT

Any help is appreciated,
        -Owen

All replies (9)

_{Saturday, August 6, 2016 5:27 PM ✅Answered}

While looking for an answer for the problem, I stumbled across this:

http://www.iis.net/learn/publish/using-the-ftp-service/configuring-ftp-firewall-settings-in-iis-7

I had created the server using the local IP address of the computer, but I should have used "All Unassigned."

Now I am able to connect from and external network but still not within... Is there a way that I am able to connect from external networks with my laptop and then come home and still access it without changing the IP to the local one in my mac's server list?

Thanks,

-Owen

_{Friday, August 5, 2016 2:38 PM}

If you created the FTP site on your local machine you need to take several steps to make it accessible from outside. This is a security measure. Are you sure you want to open your FTP server for public access?

Best regards, George

_{Friday, August 5, 2016 10:27 PM}

Thank you for the quick reply!

I have port forwarded port 21 in my router settings and enabled FTP in the Windows Firewall. 

Is there something else that I am missing?

Thanks,

-Owen

_{Saturday, August 6, 2016 7:13 AM}

Are you trying to connect from the same internal network as the IIS to the public address? Depending on your router that might or might not work. Most often it does not.

Hence I suggest:

1. Use Chrome on another network and connect to your FTP server with the public IP
2. If that does not work:
   The FTP protocol is not only using port 21 as default. Depending on your router's software you may need to connect to FTP as 'passive'. Google it if you want to know the details about the FTP protocol.

       Set Chrome to use Passive FTP:

http://smallbusiness.chron.com/use-passive-ftp-google-chrome-49772.html

Then try to connect again.

Best regards, George

_{Saturday, August 6, 2016 1:26 PM}

As I am not taking my computer with me to another network any time that is convenient, I tried it on my phone.

First I connected using my wireless network at home to the FTP using the local address of the computer, and it worked. Next, I disabled wireless and used the cellular data connection to try the FTP server and it did the same thing as my computer.

So, I went into IIS and into the firewall section to try to configure the passive port range. Unfortunately, the passive port range box was grayed out...

Thanks for all of your help so far,

-Owen

_{Saturday, August 6, 2016 1:29 PM}

You never fiddle with the passive port range. Just follow my previous link regarding Chrome.

Best regards, George

_{Sunday, August 7, 2016 2:57 PM}

Is there a solution to this problem? 

You said above that it is a router function...

Thanks,

-Owen

_{Sunday, August 7, 2016 3:01 PM}

There is always a solution but you need to read up on IP networks and how they work. Currently you are disregarding my advice and follow your own "expert" trail. It's ok but you cannot have it both ways.

Best regards, George

_{Sunday, August 7, 2016 9:31 PM}

Alright.

I left the FTP server using "All Unassigned" and followed your link. I found that the checkbox was already checked in the Browser section and exited out of the menu.

Trying to connect to the FTP - which is still on the same network - this way only yielded the same result as before...

I do not have a windows computer that I can test this on that is not on the same network. I had to do this test on the server computer as we are all on macs.

Thanks,

-Owen