|
|
Post by kostasgr on Jul 19, 2008 3:15:06 GMT 7
anybody could help me with my ddns which dont work from remote admin.I own a thecus nas n1200
My ip is dynamic
My router is sagem fast 1500wg..Please someone help me..I try to set up ddns about 3 months but nothing...
Sorry for my english...I am greek ;D
I have tried also with no-ip...not only with dyndns.org
|
|
|
|
Post by spiken on Jul 19, 2008 21:35:22 GMT 7
Dracos :
I didn't see your router wan administration access in your picture but however both of your device are associated to dyndns.
Only one device must be connected to it (your router is the better choice).
Secondly, you ve put your nas into your router dmz port, if you do this you don't have to forward anything : all the wan traffic going to your router will be redirected to your nas automatically (so it can be vulnerable to hack). Port forwarding is only used when you want to redirect some ports to it (our case).
Finally, you have not blocked the ping access to your router, so you can test it to the dyndns working:
ping myDynDnsUrl.com
|
|
|
|
Post by dracos on Jul 19, 2008 22:54:58 GMT 7
Since I posted that I tried various combinations of those configurations to no success..
how about this, can I get some examples of the settings for the router and the n3200 that work for other people?
|
|
|
|
Post by spiken on Jul 20, 2008 17:32:49 GMT 7
According to me, the problem is in your router configuration.
You don't have to configure anything in your nas to make it available from the wan.
|
|
|
|
Post by dracos on Jul 20, 2008 19:18:03 GMT 7
Ok, so the only thing I should do is:
Set dydns in router and port forwarding (ports 443,80,21) to the NAS
what about dhcp for he nas? Making sure it keeps the same ip?
|
|
|
|
Post by spiken on Jul 20, 2008 21:42:49 GMT 7
IT rules are : fixed IP for servers and printers, dhcp IP for client pc.
Ports forwarding if you don't use dmz option (strongly recommended).
You should be able to ping your dyndns url with success from the wan to check your dyndns settings.
|
|
|
|
Post by dracos on Jul 22, 2008 22:26:19 GMT 7
arghhh..
I think I give up at this point, after days of screwing with it it still won't work for me....
every time I ping, no matter what configuration it Times Out
so much for having access to my files while I'm away...
|
|
|
|
Post by dracos on Jul 22, 2008 22:32:27 GMT 7
SO.. I thought I might pop over to the DLink website and see what they had about this kind of thing... I just read that some ISPs block port 80, and that includes mine Verizon..
could that be my problem?!?!?
|
|
|
|
Post by spiken on Jul 22, 2008 22:52:45 GMT 7
Nop, according to your router configuration, you should be able to ping your router from the web (no matter port 80 blocking).
While your ping times out (so you can't reach your router) you can't access the following step : configure your router to have access your nas.
|
|
|
|
Post by dracos on Jul 22, 2008 22:58:21 GMT 7
I was talking about pinging my dydns address actually... but I just tried to ping myself (ip address) from network-tools.com and it timed out, it comes up with the information-area/isp but under that it just lists Timed Out with average time over 10 pings: 0ms
so now what do i do that my router isn't visible?
|
|
|
|
Post by edgar on Jul 23, 2008 20:16:06 GMT 7
Hi Dracos,
It doesn't matter if you cannot ping your dyndns address (disable this option on network-tools form)...
Set the ports (http/https/ftp) forwarding on your router and connect directly to the service you want.
Once connected, you have all the time required to check how to enable the wan ping as well.
If you nas is using http, I suggest you start setting that service on your router.
Reminder : http= port 80, https = port 443, ftp = ports 20 (!) AND port 21. If you are not using default port for ftp, consider forwarding port 20 AND the port you selected.
If you cannot connect to your nas using http, you should double check your router manual.
Ed
|
|
