Configure DDNS and forward the service ports on NAT router

FTP Server, File Server, DDNS, SAMBA, AFP, NFS
mrgarfin
Starting out
Posts: 12
Joined: Wed Sep 12, 2007 2:42 am

Configure DDNS and forward the service ports on NAT router

Post by mrgarfin » Mon Oct 15, 2007 7:51 am

Hi,

I have tried to enable the DDNS service on my NAS (TS-109, firmware version 1.1.2), but have had no success. In particular, I have followed all the steps in the sticky provided by QNAP

http://forum.qnap.com/phpbb2/viewtopic.php?t=730

but in the last step the NAS server will not accept my changes made for DDNS service.

Enabling this service on the NAS appears necessary, for when I use my internet browser to go to the webpage "myhostname.dyndns.org", I get the administration page for my router. [Yes, I have port forwarding on my router to 80.]

Any help would be greatly appreciated.

Michelle

User avatar
QNAPIvan
Experience counts
Posts: 1021
Joined: Mon Jul 02, 2007 4:03 pm

Post by QNAPIvan » Mon Oct 15, 2007 8:04 am

Dear Michelle:
In your description:
but in the last step the NAS server will not accept my changes made for DDNS service.

If you input the DDNS settings on TS-109 and apply it, no obvious message will feedback. As long as your settings are correct, the NAS will just reported the information to the service provider (DynDNS) periodically.

Please use these steps to check:

Check your current WAN address:
http://www.ip-lookup.net/
In most of the cases, it is useful for you to know your public IP address when you are behind a NAT router.

Check if DDNS feedback the same IP address with your WAN IP
Use ping command to check your registered address of dynamic DNS:
Start menu --> Run --> cmd
ping xxx.dyndns.org

If both IP addresses are the same, you then need to forward the related ports on your NAT router to the LAN IP of TS-109.
ex: 8080 for management, 21 for FTP, ...


Cheers,
________________________________________
Product Marketing Director
USA Online Support: http://www.qnap.com/i/useng/before_buy/con_show.php?op=showone&cid=2
Support email: q_supportus@qnap.com
USA Technical Support: +1 909 595 2782

mrgarfin
Starting out
Posts: 12
Joined: Wed Sep 12, 2007 2:42 am

Post by mrgarfin » Mon Oct 15, 2007 9:16 am

QNAPIvan,

Many thanks for your prompt reply. When I look at the Events Log on the NAS server, I see the error that the "DDNS failed to update"

Yes, I have forwarded the port for the web server (changed to 8000 on the NAS web server page).

I might add that I can reach the web site's home page when I try to access: http://<NASservername>:8000.

Also, the external address is correct and identical to the one when I use the ping command (I think, because it flashes up so quickly and then disappears).

I don't understand why the NAS server will not allow me to enable the DDNS server. Is this necessary if I have a DNSDYN client updater on my pc?

That is, I might have two distinct problems here. (i) I did not forward the port correctly; and (ii) enabling the DDNS server on the NAS is necessary, though not working.

Thanks again for your assistance.

Michelle

User avatar
QNAPIvan
Experience counts
Posts: 1021
Joined: Mon Jul 02, 2007 4:03 pm

Post by QNAPIvan » Mon Oct 15, 2007 5:58 pm

Dear mrgarfin:
When I look at the Events Log on the NAS server, I see the error that the "DDNS failed to update"


the DDNS client on QNAP NAS will periodically report the current WAN IP address to DDNS service provider (ex: DynDNS.org) every 24 hour. (Because some broadband ISPs will reset the DSL connection every 24 hour. If the WAN IP address is dynamically assigned, the WAN IP address will be changed after the connection is reinitiated. In this kind of cases, the NAS behind NAT router won't know the connection has been reset, the IP address recorded in DDNS service provider will be different from the actual WAN address. So the DDNS client on NAS need to periodically send update to DynDNS.org)

Take DynDNS.org as an example, the free service cause huge loading on their server. Therefore DynDNS doesn't allow frequently update be sent to their server. There is certain mechanism to reject the frequent connections from DDNS clients.
If you click the DDNS function on QNAP NAS many times, you may have error in event log. It does not mean you input the wrong settings, but too frequently update caused this error.

The way to verify DDNS works or not is just like what we discussed. Use IP-Lookup to check the current WAN IP, and compare the IP address feedback from ping command (ping xxxx.dyndns.org). If you have set up the correct settings, the DDNS service provider will feedback you the correct IP address.

How to access the NAS server from Internet?
If your NAS and PC are located behind the same NAT gateway, you have to forward the ports on NAT router to the LAN IP address of the QNAP NAS.

One frequently encountered issue. In many cases, users configure the NAS behind the NAT router, but failed to connect to the NAS by http://NASname.dyndns.org:8080 (example). But no problem for friends to connect to the NAS from Internet.
In this case, please make sure your NAT router support "nat loopback", otherwise the router will not forward the traffic correctly.

How to verify? You may paste the URL to your friends via Skype or MSN. If they can connect to your NAS interface from WAN but you cannot do it from the LAN, then you should check if this is the cause.

Cheers,
________________________________________
Product Marketing Director
USA Online Support: http://www.qnap.com/i/useng/before_buy/con_show.php?op=showone&cid=2
Support email: q_supportus@qnap.com
USA Technical Support: +1 909 595 2782

mrgarfin
Starting out
Posts: 12
Joined: Wed Sep 12, 2007 2:42 am

Post by mrgarfin » Tue Oct 16, 2007 3:11 am

Ivan,

Many thanks for your very comprehensive response.

I cannot access my web page on the NAS server when I am doing so outside the local network.

The ping command gives the correct IP address whether I am executing it from outside the local network or within, but when I do the command from outside the local network, I get the following error: response timed out.

I guess this means that there is a problem with my forwarding of the port. Is that a correct interpretation?

Thanks again.
Michelle

User avatar
QNAPIvan
Experience counts
Posts: 1021
Joined: Mon Jul 02, 2007 4:03 pm

Post by QNAPIvan » Wed Oct 17, 2007 7:07 pm

Dear Michelle:
Yes. I guess some settings might be incorrect on your port-forwarding of NAT router.

Please kindly refer to the system port table:

20 FTP
21 FTP
22 SSH
25 SMTP
80 Web Server
137 Netbios
138 Netbios
139 Netbios
443 SSL
445 SAMBA
873 Rsync
3306 MySQL
6000 System Management (TS-100, TS-101, TS-201)
8080 System Management (Default port of TS-109 & TS-209 series)
9000 TwonkyMedia
13131 Telnet
6881~6999 BitTorrent
55536~56559 Passive FTP
________________________________________
Product Marketing Director
USA Online Support: http://www.qnap.com/i/useng/before_buy/con_show.php?op=showone&cid=2
Support email: q_supportus@qnap.com
USA Technical Support: +1 909 595 2782

mrgarfin
Starting out
Posts: 12
Joined: Wed Sep 12, 2007 2:42 am

Post by mrgarfin » Thu Oct 18, 2007 12:11 pm

Ivan,

Thank you. I have fixed the problem. It was not that I had made a mistake in forwarding the port, but that I had not filled in the fields for the primary and secondary DNS servers (in the TCP/IP configuration page of the NAS setup), and my laptop at home was turned off, when I was trying to access the web server.

Thanks again for your help.

Michelle

User avatar
QNAPIvan
Experience counts
Posts: 1021
Joined: Mon Jul 02, 2007 4:03 pm

Post by QNAPIvan » Thu Oct 18, 2007 4:08 pm

Dear mrgarfin
Thank you for the feedback.
I will modify the title of this thread and set it as sticky post.

Cheers,
________________________________________
Product Marketing Director
USA Online Support: http://www.qnap.com/i/useng/before_buy/con_show.php?op=showone&cid=2
Support email: q_supportus@qnap.com
USA Technical Support: +1 909 595 2782

jcdede
New here
Posts: 8
Joined: Fri Nov 30, 2007 4:26 pm

Post by jcdede » Fri Dec 28, 2007 7:40 pm

Hi,
I'm confused and the more I read about it the more I am, sounds like a promessing start no? :-)

So far I have done:
1) create a dyndns host - all ok
2) when I ping dyndns i get my external IP = the one of my router
3) I'm not sure about the QNAP settings to be done (one example: "I had not filled in the fields for the primary and secondary DNS servers (in the TCP/IP configuration page of the NAS setup")
4) When I port forwared my router to 8080 I get a message (from QNAP)
The requested URL '/menu.cgi' was not found on this server and the browser is on http://jcdnas.dyndns.org:8080/menu.cgi
5) logging to http://jcdnas.dyndns.org:8080/Qfilemanager/ from another pc behind my router works ok
6) trying 5 from an external pc doesn't work

Thanks for any help.

anyuser
Starting out
Posts: 23
Joined: Wed Nov 28, 2007 2:49 am
Location: UK

Post by anyuser » Fri Dec 28, 2007 9:33 pm

When I ping jcdnas.dyndns.org I get 192.168.254.4 as your IP address which is your internal LAN address not your external IP address. Your setup is sending the wrong IP address to dyndns, I think you need to check your settings.

jcdede
New here
Posts: 8
Joined: Fri Nov 30, 2007 4:26 pm

Post by jcdede » Fri Dec 28, 2007 10:06 pm

Thanks for checking. It should be back to my external IP (i activated the DDNs in the QNAP, that restated my IP address... I suppose).
And... ping Ip address is external but request timed out and when I try to access my router now get: unknown (195.166.116.237) is managing this device
Last edited by jcdede on Fri Dec 28, 2007 10:29 pm, edited 1 time in total.

anyuser
Starting out
Posts: 23
Joined: Wed Nov 28, 2007 2:49 am
Location: UK

Post by anyuser » Fri Dec 28, 2007 10:22 pm

Check your PM!

jcdede
New here
Posts: 8
Joined: Fri Nov 30, 2007 4:26 pm

Post by jcdede » Fri Dec 28, 2007 10:31 pm

Sorry, but what is PM?

anyuser
Starting out
Posts: 23
Joined: Wed Nov 28, 2007 2:49 am
Location: UK

Post by anyuser » Fri Dec 28, 2007 10:33 pm

Private Messages (up at the top of the page).

jcdede
New here
Posts: 8
Joined: Fri Nov 30, 2007 4:26 pm

Post by jcdede » Sat Dec 29, 2007 1:24 am

Thanks for the warnings.
I tried several ports none of them worked. So here I am:

1) I have a DDNS that ping's to my IP external address (jcdnas.dyndns.org)
but get Request timed out
2) In my router I port forward to 8080 - TCP/UDP
3) When I go to http://jcdnas.dynds.org:8080 from another pc behind my router I get to my router page. (I think that happens also for public pc's)

What am I missing?

SOLVED. It appears that the problem is with my router (old model?) I tried with another and all ok now.

Post Reply

Return to “File Sharing”