Your Guide is perfect. In fact I'd like to look at forwarding ports for Android applications, but you make it clear that it isn't necessary for Synology apps, just only forward 5000 and 5001 and using Alias for other is enough. Now my video station is faster than Plex. Other apps are also smooth. Thanks for the great Guide.
Is it only ports 5000 and 5001 that need to be port forwarded? I have those and 6690 and 443 forwarded but still cannot access Synology Drive via my mobile app.
Yes, for the Synology Drive mobile app you only need ports 5000 and 5001 to be port forwarded. If you are still having problems I would check your Synology NAS firewall. Maybe you have it enabled and needs to configure allow rules there as well? Hope you find a solution.
Thanks for replying. No, my firewall is disabled. I can access my NAS using my DDNS hostname in my web browser, but not outside the local network. Would you know if internal port and external ports are the same thing when it comes to port forwarding. My router is a Linksys and it wants me to specify internal and external ports for each rule.
@@DaystromDataConcepts You're welcome!! If your Synology NAS firewall is disabled then I suspect the issue is with your port forwarding. It is fine to have both the external and internal ports be the same port. Maybe double check that the port forwarding rule points to the internal IP address of your Synology NAS. Also, maybe the Linksys has firewall rules that need to be set? Hope these clues help. Good luck!!
Thanks again for the reply, and sorry to pester you but finding answers is tough. Yes, my port forwarding rules all point to my NAS's static IP address, which is correct. The ports forwarded are 5000, 5001, 6690 (all TCP). My router's firewall is on and the only thing that might cause an issue is that NAT redirection filtering is enabled. however, a quick read of an article about this suggests I ought to have this set and that port forwarding rules will permit external access. @@digital_aloha
Thank you for this tutorial, I was able to successfully set up the DDNS and forwarded my DSM port. When logged in to my drive client from another computer I keep getting the failed to connect message. Do I need to forward more ports in my server's router to be able to connect and sync? Thank you
@SL_REFORM You're welcome!! Regarding your issue, confirm that you setup port forwarding for port 6690, which is the port your drive client will use to access the drive server. Also make sure that your router support hairpin nat especially if you are setting up your client on the same lan as your Synology NAS. You may also want to use the local IP address of your NAS to test connectivity between your client and your NAS. Hope this help? And best of luck in your setup!!
@@digital_aloha Thank you for your response!! I guess I m not so savvy to actually come through with this. Apart from Synology DDNS setup I think I m messing it up on my router setup. I have a UDM and although I am adding a Port Forward rule when trying the port it gets me to the login of my router. I think I need to read more about port forwarding on this machine.....
@@SL_REFORM Sorry to reply two time, but I've found the solution. You should add a firewall rule in you UDM which allows a connection to xx IP adress to be forwarded to the NAS IP adress and port.
Hi man! Will it work with public Wi-Fi? Cause I usually use quickconnect, but the 6690 port is always blocked on public Wi-Fi like coffee shops or airport and so the SynologyDrive Client app on the Mac is unable to reach the Nas and sync the files. It’s so frustrating
Yeah, if port 6690 is blocked then this wouldn't work either. I'd suggest setting up a VPN or use a service like Tailscale if you need access from public Wi-Fi often. I have a few videos covering both on my channel. Good luck to you!!
@@digital_aloha thanks for your quick reply. I don’t know a lot about vpn and tailscale, but I will study them and choose the best for me. 1. I already saw your video about tailscale and I didn’t understand if with it is like to have a vpn and so I will be able to use the SynologyDrive Client App. 2. Don’t you think that using a vpn is more safe then using tailscale?
I studied the problem and VPN server with Open VPN is not a solution cause Synology use 1194 port for it and also that port is closed on public wifi. The only solution I can use I think is Tailscale@@digital_aloha
Absolutely fantastic. DDNS is the way to go.
Awesome!! Happy to hear that the video was helpful and you like how DDNS works!!
Your Guide is perfect. In fact I'd like to look at forwarding ports for Android applications, but you make it clear that it isn't necessary for Synology apps, just only forward 5000 and 5001 and using Alias for other is enough. Now my video station is faster than Plex. Other apps are also smooth. Thanks for the great Guide.
Thanks. What is the "test" fails?
Thank you for this video.
Hi Pete, You're welcome!! 🙂
Excellent explanation. Thanks!
You're welcome!! Glad you liked the video!!
Is it only ports 5000 and 5001 that need to be port forwarded? I have those and 6690 and 443 forwarded but still cannot access Synology Drive via my mobile app.
Yes, for the Synology Drive mobile app you only need ports 5000 and 5001 to be port forwarded. If you are still having problems I would check your Synology NAS firewall. Maybe you have it enabled and needs to configure allow rules there as well? Hope you find a solution.
Thanks for replying. No, my firewall is disabled. I can access my NAS using my DDNS hostname in my web browser, but not outside the local network. Would you know if internal port and external ports are the same thing when it comes to port forwarding. My router is a Linksys and it wants me to specify internal and external ports for each rule.
@@DaystromDataConcepts You're welcome!! If your Synology NAS firewall is disabled then I suspect the issue is with your port forwarding. It is fine to have both the external and internal ports be the same port. Maybe double check that the port forwarding rule points to the internal IP address of your Synology NAS. Also, maybe the Linksys has firewall rules that need to be set? Hope these clues help. Good luck!!
Thanks again for the reply, and sorry to pester you but finding answers is tough. Yes, my port forwarding rules all point to my NAS's static IP address, which is correct. The ports forwarded are 5000, 5001, 6690 (all TCP). My router's firewall is on and the only thing that might cause an issue is that NAT redirection filtering is enabled. however, a quick read of an article about this suggests I ought to have this set and that port forwarding rules will permit external access. @@digital_aloha
Absolute lifesaver. Thanks!
Thank you for this tutorial, I was able to successfully set up the DDNS and forwarded my DSM port. When logged in to my drive client from another computer I keep getting the failed to connect message. Do I need to forward more ports in my server's router to be able to connect and sync? Thank you
@SL_REFORM You're welcome!! Regarding your issue, confirm that you setup port forwarding for port 6690, which is the port your drive client will use to access the drive server. Also make sure that your router support hairpin nat especially if you are setting up your client on the same lan as your Synology NAS. You may also want to use the local IP address of your NAS to test connectivity between your client and your NAS. Hope this help? And best of luck in your setup!!
@@digital_aloha Thank you for your response!! I guess I m not so savvy to actually come through with this. Apart from Synology DDNS setup I think I m messing it up on my router setup. I have a UDM and although I am adding a Port Forward rule when trying the port it gets me to the login of my router. I think I need to read more about port forwarding on this machine.....
@@SL_REFORM You're welcome! Hopefully you get your UDM router setup resolved. It does seem like you are close though... Good luck!!
@@SL_REFORM I have the same issue and can't seem to resolve it. Please let me know if you've found the fix
@@SL_REFORM Sorry to reply two time, but I've found the solution. You should add a firewall rule in you UDM which allows a connection to xx IP adress to be forwarded to the NAS IP adress and port.
Hi man!
Will it work with public Wi-Fi? Cause I usually use quickconnect, but the 6690 port is always blocked on public Wi-Fi like coffee shops or airport and so the SynologyDrive Client app on the Mac is unable to reach the Nas and sync the files. It’s so frustrating
Yeah, if port 6690 is blocked then this wouldn't work either. I'd suggest setting up a VPN or use a service like Tailscale if you need access from public Wi-Fi often. I have a few videos covering both on my channel. Good luck to you!!
@@digital_aloha thanks for your quick reply. I don’t know a lot about vpn and tailscale, but I will study them and choose the best for me.
1. I already saw your video about tailscale and I didn’t understand if with it is like to have a vpn and so I will be able to use the SynologyDrive Client App.
2. Don’t you think that using a vpn is more safe then using tailscale?
I studied the problem and VPN server with Open VPN is not a solution cause Synology use 1194 port for it and also that port is closed on public wifi. The only solution I can use I think is Tailscale@@digital_aloha
Is this for WAN or LAN only?
@hedgefundsrus This should work for both WAN and LAN access if your router supports hairpin NAT.
@@digital_aloha Cheers.
@@hedgefundsrus Good luck with your setup!!
Thanks
@fcheang8321 You're welcome!!
I see so many not so bright people opening ports on their firewalls....... Be warned! Lol Shodan will find you very easily..
@crazyclown2207 This is true!! Port forwarding should be coupled with proper security measures as well!!
Thanks you for this video.
@renatokedsondesousaamaral2724 You're welcome!!