Print

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

[Yaguar]

Hi All,

As the title suggests, I'm struggling to get anyone outside of my network to connect.

FTP server is started.
I have forwarded this port on my router, with the IP on the router pointing to the IP of the NAS.
I have also enabled Dynamic DNS on my router pointing to the same address as above.

All help is appreciated

[albert]

Use this site to check if the port is indeed open.

http://canyouseeme.org/

[Pabs]

Hi Yaguar,

Dude check out the post: issues with new firmware.

I put a post on there that may help.

Pabs

[albert]

Hi Yaguar,

Dude check out the post: issues with new firmware.

I put a post on there that may help.

Pabs

Your post is not related to TS problem.

[Gaz]

I'm having a similar issue. If I set my FTP client host value to be the internal IP, it all works perfectly. When I attempt to connect from outside, I get as far as authenticating, the FTP client reports server settings (number of allowed users, timeout, etc) but then issues command MLSD and times out reporting that file listing could not be retrieved.

Any ideas?

[Pabs]

Your post is not related to TS problem.

It is related because it has configuration information that may be of use.

[albert]

It is related because it has configuration information that may be of use.

How is your post on firmware upgrade relevant to TS problem?

[Yaguar]

Hi Guys,

Thanks for the responses. I have tried a new router (rather that the one supplied with my ISP) and I seem to have gotten a lot further. Just one question remains (I hope).

The FTP is set for Anonymous permission as "none". Setting to this value I had hoped I could enter my FTP address into a browser/windows explorer and be prompted to enter logon credentials. This is not working and just kicks straight back out as it is seeing me as "Anonymous". Is there a setting I need to change?

[Yaguar]

Fixed -

New router with proper file server forwarding options (rather than just a standard "firewall" port forwarding option). This allowed me to see the FTP server correctly.

Setting the port back to 21 from my manual set of 1025, allowed for the login box to appear and to be able to log in anonymously.

[Yaguar]

I'm having a similar issue. If I set my FTP client host value to be the internal IP, it all works perfectly. When I attempt to connect from outside, I get as far as authenticating, the FTP client reports server settings (number of allowed users, timeout, etc) but then issues command MLSD and times out reporting that file listing could not be retrieved.

Any ideas?

Gaz,

I was getting this error whilst using Filezilla. Have you chosen a different port than 21? My issue was that I was using 1025 rather than the default. Changing it back to the default value of 21 resolved this for me.

[Gaz]

Yaguar - I am also using 1025. I'll change it back to 21 and see what happens. The odd thing is that the port forwarding is clearly working, it just won't list the files.

[Yaguar]

Gaz,

Did you manage to resolve your issue by changing the port back to 21?

[Gaz]

Yaguar - no, I get exactly the same issue. It works up until the FTP client issues the "MLSD" command and then it just times out.

[albert]

Yaguar - no, I get exactly the same issue. It works up until the FTP client issues the "MLSD" command and then it just times out.

Try opening up port 20 as well.

[billy_kidd]

The problem with the 320 is that you can't seem to use any port other than 21.  I have 4 FTP servers.  The ones on 21, 2122 and 2124 work fine. The 21XX ones are DNS-321's.  The one on 21 is not a DLINK.  So, if I assign the DNS-320 to port 21, then it works fine.  Assigning it to anything else and it fails.

And yes, I am properly port forwarding in the Router and making the appropriate adjustments for ports in the DNS-320 as well as the FTP client.  It just doesn't work on ANYTHING but port 21.