Issue Getting Connected to FTP Server

[CaseCrS]

Hi there,
I had an FTP server setup and working with no problems then my router died and I needed to get a new one. Now for some reason I can't figure out why I can't get connected to the FTP server.
I've opened the custom ports on the router and windows firewall and it shows that the listening port is open using canyouseeme.org.
I can connect to it using the ftp://localhost:port# in a browser but am unable to connect when trying to connect outside my home network.
I've got it set up using a Free Dynamic DNS service.
The Online FTP Tester comes back with connection attempt timed out.

I've also disabled both the router firewall and the windows firewall with no luck.
Any other suggestions?
Thanks!

[botg]

Did you merely open the ports in the router's firewall, or did you also forward them in your router's NAT tables?

[CaseCrS]

When forwarding the ports on my router I specified the IP address for the PC that the server is on.

[boco]

What about the software firewall on the server machine? Even if it was configured before, new router means new network detected. New network means new entries required, especially if you got a new IP from the new router.

[CaseCrS]

The Firewall on the Server (Windows) machine has both inbound and outbound rules set up to open the specific ports that I have set up.

[CaseCrS]

I just disabled Windows firewall and installed Comodo firewall, and set up the server for FTP Over TLS. I'm still able to login using localhost but not from outside my home network.

I get this result in the server window when using canyouseeme.org

Code: Select all

(000002)2018-08-05 6:27:01 AM - (not logged in) (52.202.215.126)> Connected on port , sending welcome message...
(000002)2018-08-05 6:27:01 AM - (not logged in) (52.202.215.126)> 220 
(000002)2018-08-05 6:27:01 AM - (not logged in) (52.202.215.126)> disconnected.

However I get nothing when trying to connect through an ftp client or when testing with ftptest.net

[boco]

Did you modify the log? No port shown, and no Welcome Message shown.

[CaseCrS]

Yes, the port is 990

[boco]

Port 990 is used for FTP over TLS Implicit, which is encrypted from the start. The check website you used probably doesn't support Implicit FTPS or you didn't use it. For FTP servers, please use our testing facility.

Also note that the client must support the FTP encryption mode you use. Browsers generally DO NOT support any encrypted FTP. So, trying to connect with a Browser on port 990 will ALWAYS fail.

[CaseCrS]

That testing facility is the one that I used.
I was originally just using the normal unencrypted FTP on port 60059 (my original server before the router switch) and when setting it back up with the new router I started with the same config using the 60059 port which wasn't working so I tried to switch to FTP over TLS Implicit because I noticed a few entries in the log that looked like someone I didn't know was trying connect to the FTP server.

[CaseCrS]

Here's some more info (switched back to Plain FTP for now)
I've Forwarded the port range 60059-60160 On my router

FileZilla Port Range.png (18.89 KiB) Viewed 6415 times

Also in the Firewall

The attachment Listening Port.png is no longer available

The attachment FirewallPortRange-.png is no longer available

Set Up the FileZilla Server like this

The attachment FileZilla Port Range.png is no longer available

I've tried bypassing the Router and connecting the Modem directly to the PC with no luck.
I get these results in the server logs when testing to port on canyouseeme.org

Code: Select all

(000006)2018-08-07 13:48:30 PM - (not logged in) (52.202.215.126)> Connected on port 60059, sending welcome message...
(000006)2018-08-07 13:48:30 PM - (not logged in) (52.202.215.126)> 220-FileZilla Server 0.9.60 beta
(000006)2018-08-07 13:48:30 PM - (not logged in) (52.202.215.126)> 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
(000006)2018-08-07 13:48:30 PM - (not logged in) (52.202.215.126)> 220 Please visit https://filezilla-project.org/
(000006)2018-08-07 13:48:30 PM - (not logged in) (52.202.215.126)> disconnected.

and the Online FTP Tester comes back with these results

Code: Select all

Warning: Plaintext FTP is insecure. You should use explicit FTP over TLS.
Warning: Selected port (60059) is not the default port (21) of the selected protocol.
Status: Resolving address of audiobooks.ddns.net
Status: Connecting to 24.53.119.78
Error: Connection attempt timed out

[botg]

Your firewall configuration is wrong.

For incoming packets 60059 through 60160 are the destination ports. The source port can be anything and everything as it is solely client-controlled.

Only for outgoing packets, the source port is 60059 through 60160 through, this time with the destination client-controlled.


An exception are active mode transfers, here both source and destination, in both directions, are random from the server's view.

[CaseCrS]

I had both Destination and Source Ports set up for that range.
I took away the Source Port range shown in the picture with the same results as before.
The port check tool shows the port is open and the Online FTP tester comes back with attempt timed out.

[boco]

I cannot see your images, please attach them directly (also future ones).

[CaseCrS]

I cannot see your images, please attach them directly (also future ones).

Edited post and attached images directly.