Why can't I connect to my server?

[hotelmariofan]

I recently set up a FileZilla server on one of my PCs, and I cannot connect to it on any other PC than the PC hosting the server itself. I have forwarded a few ports, 990, 3850, and 21. I have made sure that the server software is allowed through the windows firewall. I have turned off both the windows firewall and my routers firewall and I still can't connect. Now I'm not completely sure but if I have it right, I need to connect to the PC that is running the servers internal IP, which in my case would be 10.0.0.2. I've tried that, and 127.0.0.1 and the external IP just to see what happens. When I try to connect to 10.0.0.2 I get a message saying,
"Status: Connecting to 10.0.0.2:21...
Error: Connection timed out
Error: Could not connect to server"

If I try to connect to 127.0.0.1 I get this
"Command: USER hotelmariofan
Response: 331 Password required for hotelmariofan
Command: PASS
Response: 530 Login or password incorrect!
Error: Critical error
Error: Could not connect to server"

Also, yes I went through and set up an account with the correct settings and everything. Just to be sure, I tested it on on the server PC itself and I can connect to the server when on the server PC, but that's kind of obvious so didn't help much. I'm not sure what to do from here and I'd really appreciate some help, thanks in advanced.

[botg]

127.0.0.1 is the loopback address, every computer has this address. It always refers to the machine it is entered on.

Using the LAN IP address instead, if connecting on the same machine as the server is running works, but not from another computer, then there's still some firewall interfering.

[hotelmariofan]

127.0.0.1 is the loopback address, every computer has this address. It always refers to the machine it is entered on.

Using the LAN IP address instead, if connecting on the same machine as the server is running works, but not from another computer, then there's still some firewall interfering.

Alright, but I'm not sure exactly what else there is for me to do. Is there something I could be missing?

[boco]

I have forwarded a few ports, 990, 3850, and 21.

If you intend to make the server public eventually, you need to forward multiple ports for Passive data connections. For low-traffic FTP servers 100 ports should suffice, higher traffic ones need thousands.

If the server works from the same PC, the server works. The rest is all about firewall/router exceptions and the like.

If I try to connect to 127.0.0.1 I get this

Whatever PC you tried this IPv4 on must run an FTP server, too. That address always means ''Connect to yourself''.

[hotelmariofan]

So what should I change in my routers settings? If it helps, my router also doubles as my modem. It's the Comcast dori.

[boco]

You must do what's written in the Network Configuration guide about setting up the server for Passive mode.
1. Tell it the external IPv4.
2. Define Passive port range.
3. Open all involved ports in every firewall you own and forward them in the router (statically, not triggering).
4. Use https://ftptest.net/ to test the server.

Btw. Comcast isn't the best choice if you want to run FTP servers.

[hotelmariofan]

You must do what's written in the Network Configuration guide about setting up the server for Passive mode.
1. Tell it the external IPv4.
2. Define Passive port range.
3. Open all involved ports in every firewall you own and forward them in the router (statically, not triggering).
4. Use https://ftptest.net/ to test the server.

Btw. Comcast isn't the best choice if you want to run FTP servers.

Wow, sorry for wasting your time. I had set the server interface as an exception in windows firewall instead of the server.exe, it's now working. I appreciate your patience.