Can't connect to Windows 10 ftp server

Question

Forgive if this isn't the right forum to post in. Please direct me if so.

I'm a total newb trying to set up a file server in Windows 10. I've set up IIS services (FTP service, FTP extensibility, and IIS management console). I created a test site with a physical path to a local folder. I set up a port forward (21) with xFinity (they say my server doesn't need a static IP address).

I want the server to be accessible from the internet and since apparently the major browsers have disabled ftp support, I've tried connecting with Cute FTP and Filezilla by using the server's public IP address, user name and password. Both just time out. I need to know where to start troubleshooting this.

Thank you for any help,

Ripper

Answer 1

Hi

If your port forward is done in the router, make sure it's for both port 20 and 21. You need both ports.

Make sure on the Windows 10 the firewall is set to allow such traffics, from external IP.

Is it working from a computer inside you LAN ? I ask as some ISP might block such port for residential's client.

Let us know if you see some error in cuteftp or not.

Thanks

Answer 2

Typically to access a server from the internet the first step is configure the modem / router to map a port to an internal server.

The second step is to determine the modem / routers public ipaddress.

If you have a static, you typically buy a domain name and register with a dns provider. Your isp may supply this service.

If dynamic, you can use a dynamic dns proxy service. You typically install an application on the server that polls the dns service to update its current public ipaddress

Finally you can just use a site like what’s my ipaddress, and just use the ipaddress.

Answer 3

Thank you for the response.

My xFinity router's setup page forces me to their website to set up port forwarding, which I did for ports 20, as you suggested, and 21 . The firewalls on the server and the desktop machine I'm using to connect are turned off for testing purposes. I can ping the server from my desktop and it's accessible over LAN. Cute FTP error says this:

STATUS:> [2/12/2022 8:35:13 AM] Getting listing ""...
STATUS:> [2/12/2022 8:35:13 AM] Connecting to FTP server... xx.xx.xxx.xxx:21 (ip = xx.xx.xxx.xxx)...
ERROR:> [2/12/2022 8:35:34 AM] The connection failed due to an error or timeout.

1. Verify that the destination IP address is correct.
2. Increase the connection timeout threshold under Global Settings | Connection.
3. Switch to the opposite data connection type (PASV or PORT) under Site Settings | Type tab.
4. Verify that the problem is not local by trying to connect to an alternate server.
5. If a server name was used, verify it resolves to the correct address.
6. If using a local server table for server name resolution, check to see that it doesn't resolve to an obsolete address.
7. Try pinging the address.
8. If you are using a router, verify the router is up and running (check by pinging it and then ping an address outside of the router).
9. Do a traceroute to the destination to verify all routers along the connection path are operational.
10. Verify that your subnet mask is setup properly.
11. Verify that your local software or hardware firewall is not blocking outbound connections originating from CuteFTP.
12. Verify that your anti-virus software is not at fault (try disabling it).

I've discovered that I can connect to the server from a different machine (a Win 10 laptop) easily using Explorer and WinSCP, so the problem obviously lies with the desktop, but I don't know what to look for. Any suggestions are appreciated.

Rip

Answer 4

Can anyone help with this?

Tnaks

Answer 5

The way traditional FTP works is not like many others applications.
Usually port 21 is used for initial connected after that a lot of other ports are used to transfer files.
Since you behind a router with NAT, you have to use it in Passive Mode, search for FTP Active/Passive mode.
Here a link that might help you ftp_modes