• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dummy FTP question...I am stumped

leeland

Diamond Member
To connect to my home NAS which runs a UNIX OS and has built in FTP functionality.

I can obviously connect fine within my home network...however when I go outside (i.e. work) I cannot connect...

I have seen thousands of posts just like this, I have read config guides on the net...they make sense...

The part that is puzzling me is WTF I am doing wrong. The settings shouldn't be that difficult but they are.

Senario #1 IT WORKS!
I have a dyndns account for the dynamic IP
forward port 21 on my router to my NAS
config filezilla via the dyndns account and port 21 and I can connect just fine from outside my network.

Senario #2 IT FAILS 🙁
make the change in the ftp server to listen on 22222
make the change on the router to forward port 22222 to my NAS IP (same port)
try to login with that simple change I get an error saying cannot authenticate...

Status: Connection established, waiting for welcome message...
Trace: CFtpControlSocket:😱nReceive()
Response: Error: Must authenticate before using this service.
Trace: CFtpControlSocket::ResetOperation(66)
Trace: CControlSocket::ResetOperation(66)
Error: Could not connect to server



Is the issue on the config of Filezilla, my router, or on the PC I am using to connect? or a combo of all three?

I do NOT want to leave it on port 21...the log is littered with assbags from China and Mexico trying every username / password combo on the earth...

I also tried to get FTP with SSL/TLS (Explicit) running but again ran into the same errors and I haven't seen a good way of configuring this...I don't know what ports I would need to open if any...

I am sure it is something super silly and I just don't get it.


Any help is appreciated.

 
An odd idea - you might try routing external port 22222 to NAS port 21. (Anything incoming externally on port 21 should be ignored.)
 
I did try that as well...I made sure I could connect correctly with port 21. It worked...went into the Router and changed the public port to 22222, went into the FTP program and change it to 22222

same error...

I was reading a little bit on a site that says if you use a standard port (21) that NAT on a firewall will kick in basically and open the command port (20)...but when non standard ports are used that doesn't work...

I think that is the majority of my issue...but figuring out how to correct it is what has me stumped
 
Back
Top