D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-320 => Topic started by: ATARI on April 04, 2011, 12:18:16 AM
-
OK here is my Setup
Wall - Modem - Dlink WLAN Router - DNS 320
(PC connect to the Router)
I have an account at dyndns.com. now what iv done before but didn't work:
In the Dynamic DNS section of my NAS I entered the Info's provided by dyndns.com (IMO correctly because the NAS can connect to the provided IP)
I enabled the FTP server and its Port to 21
plus I have the Itunes server running
In my Dlink router I Port forwarded Port 21 to my NAS
plus I made an entry for the Itunes server running on Port 3698 allsow on my NAS
what am i doing wrong?
do I have to connect the NAS to the Modem instead of the Router? or
Does the DynDNS entry have to be set on the Router instead of the NAS... the router has the possibility..
thanks in advance...
i know these things should be left to experts but just have to get this running^^
-
no one?
or am I just in Bad time zone to expect other people awake^^
-
Configure DDNS on router or NAS not both, the former is prefer.
As for FTP issue, what specific error did you encountered?
Use this site - www.canyouseeme.org to verify that the require port(s) are not block.
-
Configure DDNS on router or NAS not both, the former is prefer.
As for FTP issue, what specific error did you encountered?
Use this site - www.canyouseeme.org to verify that the require port(s) are not block.
Thanks for answering!
(and sorry for my bad english)
Ok i have done the check on that site and i get:
Error: I could not see your service on 80.219.XXX.25 on port (21)
Reason: Connection timed out
When I ping that IP (or the domain given by dyndns.com) with the cmd it works.. no loss of pakeges..
could it be that I have to not only do a portforward rule but allsow a virtual server rule in the advanced section of my router
or do I need a rule with this ip further up? right now the router only has the local IP enterd in the rules.. the normal 192.and so on.
thanks again!
ps. I now made the settings on the router like you sugested and dsabled it on the NAS
-
It pointless to ping within your LAN as the problem is not related to name resolution. If you get a negative response from canyouseeme site that meant your port forwarding is not done correctly or being blocked by your ISP.
-
Hey Atari,
I setup my DDNS account today. Here's how my config looks.
Router setup
Port forwarding is turned on. Port 20 to 21 points to: my internal NAS IP.
DMZ address also is turned on and again points to: my internal NAS IP.
NAS setup
DDNS is configured to use my DynDNS account (dyndns.com) the details are intern replicated into the NAS's DDNS settings. So host name, username password etc from your dyndns account are added in here.
I am also on Firmware V2.
Hope that helps.
Pabs
-
LOL, what's the point of doing port-forwarding when the NAS is already on DMZ?
-
OK Thanks for all the help! really great of you guys to take the time!
Still cant get it to wortk... would it be of use if I post screen shots of my port forwarding rules?
or does someone have like a step by step method of testing the setting to see where it fails..
an other thing is my Router is a DLink DIR-855.. and it has more configuration options than the my DNS320 so im guessing its pretty sophisticated^^ Searching the User Manual with the Keyword "FTP" broght me to two pages... The Page for DDNS settings (witch I think I enterd correctly) and the Page for Virtual Servers. The possible Settings in the Virtual Servers menu are allmost the same as in the Portvorwarding menu. Could it be that I need the entry there and not in the Portvorwarding?
and its not that my ISP is blocking port 21... I set FTP to 2012, went to canyouseeme.com, and still conection timmed out..
-
Use the Virtual Server option to configure portforwarding.
Do ensure your NAS FTP server is enabled before checking out at canyouseeme.
-
cool thanks Im in the office right now but ill change it to virtual server as soon as im home!
In an other forum of DynDNS.com I read somewhere that a guy had to change the dyndns service from HOST to WEBHOB redirect.. but im sure thats not what im looking for.. just wanted to throw it in there.