Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mas110]

Hopefully, you can find an answer to your problem and please let us know as well.  I am having similar issues.

[gunrunnerjohn]

There must be something silly I'm missing, just don't know what it is.

[DocD]

Hi gunrunnerjohn,

Your NAS box settings look like a duplicate of mine.  Out of curiosity, what FTP client are you using?  With FileZilla, I can consistently connect with TLS enabled.

Two settings are critical, however...
1)  FTPS must be defined as "explicit" - shown below:

2)  In the passive FTP settings options (in the client), the external IP option must be selected (shown below)


Everything else was pretty much the default settings for a passive FTP setup.

Hangeth in there... 
-DocD

[mas110]

Hi
It is possible that the external IP address in DynDNS is the issue, if you use it.  I installed the new bin (ver 1.08) and could finally make it work with net2ftp.com in passive mode with SLS.  I have not yet tried it with standalone FTP client (such as filezilla), I can try it tomorrow morning in the office.  I loged in to my DynDNS server (which is dlinkddns.com) and the IP was not correct. IT showed the internal IP of the DNS-323 as external IP. Apparently, the DNS-323 was not updating the real external IP to the server and was sending internal IP to the server.  I disabled the feature in the DNS-323 and put it back in the router. It is working fine now.

The question is, does anybody else have this problem (DNS feature not providing correct external IP address to the DynDNS server). if the answer is yes, then the solution is to put the feature in the router to update the DynDNS server correctly.  

If the above is confirmed and we end up disabling the DNS in the DNS-323, how the "external IP" line in the FTP section of Web UI would update itself.

[gunrunnerjohn]

I'm using FileZilla and I have the above settings.  I'm beginning to think there may be some issue with my router passing the proper data.  Since it's a Verizon FiOS router, and it also controls my TV guide and On-Demand, I can't really lose the router.

I'm going to have to fire up WireShark and see what is actually going on and see if I can find out where this is going bad.

[mas110]

Hi gunrunnerjohn
What about the Dyn DNS server.  Does your DNS-323 update/provide correct external IP address to the DynDNS server or like mine, it was a wrong address.  HAve you logged in to youe accound in the DynDNS to verify it?

[gunrunnerjohn]

The DynDNS is working properly, and the address they have is really my address here.

[mas110]

I am surprised why the DDNS feature is not working properly in my DNS-323 (sending wrong IP address to DynDNS).  I had to disable it in DNS-323 and put it in my Linksys router.

Just to let you know.  I tried my home FTP (DNS-323) from the office today.  I tested four different client as below:

1 - www.net2ftp.com: it worked fine under SLS as last night from home

2 - WinSCP for U3:  I did not worked at all

3 - FireFTP (an add-on to Mozilla FireFox in U3):  It worked only under "Auth TLS".  It worked fine.  The two other methods "Auth SLS" and "Implicit SLS" did not work.

4 - FileZille for U3: It worked fine only under "FTP over TLS".  The other two method of "FTP over SLS" did not work.  However, the setting menu is different that what DocD is shown above.  Maybe, mine is different as it is for U3.  The pictures shown by DocD might be for standard FileZilla, not the U3.

[gunrunnerjohn]

I'm getting the idea that maybe I'm not destined to have secure FTP working here.

I'm thinking of looking for a 3rd party add-on for SFTP, which seems to be more common than FTP over SSL, which seems to be what the DNS-323 is offering.  It also bothers me that even when I run locally, it switches over to clear mode for the file transfer, I'd like all of the transaction to be encrypted.

[mas110]

Hi gunrunnerjohn

I am wondering if you could solve your problem.  As I noted before, it was working for me after removing the Dyn DNS update feature from DNS-323 and put it back in my router.  Since then, the secure FTP was working for me with the FileZilla and the setting recommended by DocD above.

However, I moved to a new office and the FTP is not working with FileZilla any more.  I get the folliwng message.

Status:   Connection attempt failed with "ECONNREFUSED - Connection refused by server".


Nothing has changed, same setting in DNS-323 and same setting in FileZilla, I just fo not understand.  It might have something to do with being in a new office.  Any idea?

[gunrunnerjohn]

Probably something in the network topology at the new location.  I still haven't gotten secure FTP to work here through my Verizon FiOS connection, don't know why.  I get logged in, but FileZilla can't get a directory listing.

I've dropped back to standard FTP, and I only enable the server when I need it.  Not an ideal solution, and I'm still looking for a better way to do this.

[mas110]

Have you tried checking the Dynamic DNS.  In my case, when I enabled the Dyn DNS in the DNS-323, it cuased the problem.  During the initital connection it was Ok, however, it could not get the directiry list.  I went to the Dyn DNS web site (in my case Dlink.ddns.com) and noticed that my IP address is wrong.  Appreantly, when the FTP server is called, it screws up the IP address and send the local IP address of the DNS-323 to the website.  I suggest, try to connect to the FTP sever by using FileZilla, however, this time enter you IP address directy (e.g., 209.34.......), insted of the Dyn DSS link.  Try it if you have not done that before.

[gunrunnerjohn]

Well, my IP address at DynDNS is correct, and if you look at the log in my first message, it has the correct public IP address.  It certainly appears that this is OK.

[Buhric]

I get as far as trying to get a directory listing, and then it fails.  I've forwarded ports 21, 22, 990, and the default passive range of 55536-55663.

I dont know much about Secured FTP, but I noticed something...
Could you issue be port related ? I see that it times out after setting he passive ports
and the ports set are NOT in your PASV port range...

I dont think you issue is IP related since it "connects" to the server fine and authenticates you.
The connection times out after trying to get the file list...

Try "forcing" the passive port range to 55536-55663 instead of using "default"

[gunrunnerjohn]

What would be the difference between using the default and forcing it.  I wondered about that, since they specify the same port ranges!  

FWIW, standard FTP works fine remotely.