rauan Posted January 15, 2018 Share #1 Posted January 15, 2018 Hi everyone!I apologize in advance if this was discussed already. If it was I would appreciate a link to the topic.I successfully updated from 5.2 on 3611xs to 6.1 on 3615xs, but my new SN is kicked out from quickconnect service. I want to say that I am not trying to get SN working with Synology account before I got banned here. The thing is that my Telekom Speedport w724v router doesn’t provide upnp option. I am not 100% sure if that’s the reason but I can’t connect to my nas from internet with my servername.ddns.net address.I am not advanced person in this matter therefore I was hoping if I can get help here. Does anyone have a step by step instructions how to solve my case? Unless it is a small thing. Thank you in advance! Sent from my iPhone using Tapatalk Quote Link to comment Share on other sites More sharing options...
sbv3000 Posted January 15, 2018 Share #2 Posted January 15, 2018 Have a look to see if your router supports ddns and setup on there, with port forward or vpn to the NAS Quote Link to comment Share on other sites More sharing options...
rauan Posted January 16, 2018 Author Share #3 Posted January 16, 2018 I enabled ports 5000 and 5001 on my Telekom router. No changes. Quote Link to comment Share on other sites More sharing options...
Dfds Posted January 16, 2018 Share #4 Posted January 16, 2018 3 hours ago, rauan said: I enabled ports 5000 and 5001 on my Telekom router. No changes. Have you checked to see that they are open using something like https://portchecker.co/ Quote Link to comment Share on other sites More sharing options...
painkiller895 Posted January 16, 2018 Share #5 Posted January 16, 2018 (edited) make sure that you point the proper ip number to that port on the router. Also on the DSM you have to add your account info from your-dsm-host.ddns.net go to external access , ddns add your info and hit update now. If it turns green your good, if it's red it means its not working or configured correctly. if your using ddns.net make sure you point to the proper port on that server to your box.... Edited January 16, 2018 by painkiller895 Quote Link to comment Share on other sites More sharing options...
rauan Posted January 16, 2018 Author Share #6 Posted January 16, 2018 Have a look to see if your router supports ddns and setup on there, with port forward or vpn to the NASI don’t know how I missed it on my router, it was right there on the same page where I could setup ddns access. Thank you for the tip! I can finally access it from outside. However learned that I cannot access my nas inside of network with the same ddns address. I can either use 192.168.2.xxx ip in the network or xxxx.ddns.net from internet. Any ideas?Sent from my iPhone using Tapatalk Quote Link to comment Share on other sites More sharing options...
sbv3000 Posted January 17, 2018 Share #7 Posted January 17, 2018 17 hours ago, rauan said: I don’t know how I missed it on my router, it was right there on the same page where I could setup ddns access. Thank you for the tip! I can finally access it from outside. However learned that I cannot access my nas inside of network with the same ddns address. I can either use 192.168.2.xxx ip in the network or xxxx.ddns.net from internet. Any ideas? Sent from my iPhone using Tapatalk Check your router for options like 'bypass dns for local addresses', 'dns forwarding or routing' . It might be that the router is 'talking to itself' trying to use external ddns and routing back. more relevant is why use ddns internally anyway? The NAS should be found by upnp/samba name etc not some long external ddns, much simpler Quote Link to comment Share on other sites More sharing options...
rauan Posted January 18, 2018 Author Share #8 Posted January 18, 2018 18 hours ago, sbv3000 said: more relevant is why use ddns internally anyway? The NAS should be found by upnp/samba name etc not some long external ddns, much simpler I wanted to use it for DS Photo and DS Video stations. It is easier when I have only one name instead of changing IP to DDNS all the time. Quote Link to comment Share on other sites More sharing options...
Meniak Posted February 16, 2018 Share #9 Posted February 16, 2018 Your problem is probably related to NAT loopback rather than a DNS problem. See if your router supports NAT loopback and if so, enable it and see if that works. If your router doesn't support UPnP I doubt it would support NAT Loopback though. We used to alter host files in a windows environment to have the IP of the system correspond with the DDNS. I don't know if that's possible with xpenology. Quote Link to comment Share on other sites More sharing options...
apejovic Posted July 7, 2018 Share #10 Posted July 7, 2018 The router from Telekom does not support it. A friend of mine got the same problem. Buy a router from AVM. They work like a charm. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.