I have a remote Synology drive at my parent’s house that I use in part as a VPN (They are in the US, I’m in Europe), at least I used to as the DDNS appears to have stopped working correctly.
Since it is pretty easy to set up a DDNS, I deleted the old configuration and redid it according to the instructions on the video provided by SpaceRex. The status shows as normal and the connection test worked.
What are some common faults that I should check to resolve this problem?
Thanks!
Dan
I assume that you mean that remote access via DDNS is no longer working. A common cause is that port forwarding is not working. Potential causes are that the router lost the rule to forward, or that the rule does not forward to the correct IP address. The latter may be the case if the NAS does not have a fixed or reserved IP address.
Thanks. I will have to look into these two possibilities. How do I find the correct port number for DDNS?
DDNS takes the problem of a dynamic external IP address out of your hands. The port number is determined by the service you plan to access on your NAS.
For example, the DSM login page has by default the ports 5000 (http) and 5001 (https). You can find and change the default in DSM > Control Panel > Login Portal. At the Applications tab in the Login Portal, you can define other applications and their port numbers.
Next, you have to forward these ports to the IP address of your NAS in your router.
Contact Synology, as others have seen on/off behavior with Synology DDNS recently.
I recommend you find an alternate DDNS provider, and use Synology DDNS only for a backup.
Has the NAS firewall been changed to include things like country blocking? Aside from Port Forwarding, changes in the firewall rules can break a connection too.
Please elaborate on what worked and what didn’t work. I’m guessing that what didn’t was a VPN connection though, that’s just a guess. Also, based on what worked, are there other things that you have tried to test the connectivity?