Print

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

[bosstone75]

Hello all!

I need some real basic help to learn how to FTP to my DNS-321 NAS Drive.

Here's what I've done so far...

In the web interface, on the FTP Server tab of the 321...
I have the following settings saved...
Max. User = 10    
Idle Time = 2 minutes
Port  = 1025   
Flow Control = Unlimited
Client Language = Western European

I created a user on the User/Groups tab
Username = bosstone75
Password = ********** (I actually set a password)

Back to the FTP Server tab
I selected the user bosstone75
I Browsed until I found the folder Volume_1
I gave permission for read and write

The status says that the FTP Server is Started.

THEN ON MY ROUTER

My Router is Buffalo Airstation WHR-G54S

I edited the NAT table
For the WAN side IP address I selected (Use AirStatation WAN IP Address)
For the Protocol, I selected TCP - Port Number 1025
For the LAN IP address, I entered 192.168.11.18 (the address that is assigned to my NAS Drive)

That pretty much covers everything I've done so far...

I would be using Filezilla (on my PC) and Cyberduck (on my Mac) as the FTP Clients

Can anyone help with what I need to do next?  When I try to log on using (let's say Cyberduck), what would my Server be?  My username (would I use the router username or the NAS username I created?)  My password?

Thanks!

[bosstone75]

OK... got a little further in my quest.  I discovered I had to create an account at dlinkddns.com.

I put in my hostname I want and it came up with my browser IP address automatically, but it's asking me for a New IP address... would that be the address of my NAS (i.e. 192.168.11.18)?

[Another Joe]

I believe the new IP address refers to your external IP.

[kaiserbachfeld]

yes you need to use your external or WAN IP address given to you by your ISP which is probably a Dynamic address so you will need to install a client that will update your ddns to what your new IP address is when it is changed others your link will break.  I haven't figure out what the best update client is yet.  I think my router is doing it for me since it is connected to dyndns.com where I have my dns from but I haven't verified that yet.  The clients suggested at dyndns are for linux and I am setting this NAS up for someone who doesn't have linux (and my linux server isn't currently up and running).

[emanoyhl]

actually the dns-321 in tools/ddns has the fields to input your dyndns account info - most routers also have that setup somewhere in config as well.... ideally, you should set it up with your router (if internally supported) - not sure why the dns-321 has this feature anyway since it sits behind a router anyway - unless you plug your internet line right into the dns-321...

anywho - good luck!


(also, ftp port is usually 21, not sure some clients would support 1025)

[gunrunnerjohn]

actually the dns-321 in tools/ddns has the fields to input your dyndns account info - most routers also have that setup somewhere in config as well.... ideally, you should set it up with your router (if internally supported) - not sure why the dns-321 has this feature anyway since it sits behind a router anyway - unless you plug your internet line right into the dns-321...

The reason you can't understand why the DNS-321 has this feature is you simply don't understand at all how DynDNS works.  Maybe you should do that research before posting nonsensical answers. 

[wayd]

I had issues with my FTP working and I trouble shot it for HOURS. I was forwarding to a random port number, and had both the DNS-321 and the Router and the DDNS set up... Never worked. I changed my port back to 21 and also forwarded 20. It worked. I have read several places, that its best to get it working on 21 and 20 first, then try to move ports.

[emanoyhl]

The reason you can't understand why the DNS-321 has this feature is you simply don't understand at all how DynDNS works.  Maybe you should do that research before posting nonsensical answers. 

i quite understand, you don't have to be rude

i'm stating that why would you plug the dns-321 directly to the internet, as most casual users will have it behind a router/firewall - hence making that feature of the dns-321 null

imo it's best to configure it behind your router/firewall by utilizing the router's ddns features and disabling the dns-321 ddns - but if you are willing to place your dns-321 exposed to the internet, with no router/firewall, by all means go ahead

[jamieburchell]

Your DNS-321 doesn't need to be "exposed to the Internet" nor "directly connected to the Internet".
If your router doesn't have DynDNS facilities, you can configure the DNS-321 to update the record instead. It can still sit behind your router/firewall.

[emanoyhl]

Your DNS-321 doesn't need to be "exposed to the Internet" nor "directly connected to the Internet".
If your router doesn't have DynDNS facilities, you can configure the DNS-321 to update the record instead. It can still sit behind your router/firewall.

it doesn't work that way - if your dns-321 sits behind your router - the dns-321 has an internal ip address - so its ddns function will only ping out its internal ip address, not the actual wan ip - unless you yourself manually update your dyndns ip number through their website - the only way the dns-321 can ping dyndns services is by acquiring the actual wan ip of your line and then pinging that out - if the dns-321 is statically assigned an internal address (192.168.x.xxx - such as you would when behind a router) it won't update the actual wan (isp address)

hence my previous posts - irregardless, the problem the original poster had was the port number

[jamieburchell]

it doesn't work that way

It does.

if your dns-321 sits behind your router - the dns-321 has an internal ip address - so its ddns function will only ping out its internal ip address, not the actual wan ip - unless you yourself manually update your dyndns ip number through their website

Try it.

Think about it. What would be the point of a DynDNS function that updates the account with your NAS's internal IP address? It works out what your EXTERNAL IP address is, even though it's sitting behind your router/firewall (hint: DNS-321 gateway address).

You really should have a better understanding of these things before stating ill informed information.

[emanoyhl]

It does.

Try it.

Think about it. What would be the point of a DynDNS function that updates the account with your NAS's internal IP address? It works out what your EXTERNAL IP address is, even though it's sitting behind your router/firewall (hint: DNS-323 gateway address).

You really should have a better understanding of these things before stating ill informed information.

yes - technically it is *supposed* to work wherever the ddns resides - however, on the 321 it does not work
it's some type of bug on the firmware

try it yourself - as i have tried

plus, this is the 321 forum, not the 323

thanks


*edit

to clarify, when i set it up - the ddns on the dns-321 worked - for logging in and connecting with dyndns.com - however, once the wan ip changed, the dns-321 did not update like a ddns should - anyone else experienced this? or am i the only isolated event? (irregardless, i disable it on my dns-321 and enable on my router)