Synology VPN Connects but Nothing Opens The Fix Ladder
Connected is the most misleading word in networking. The tunnel is up, the phone is happy — and your NAS might as well be switched off. Here is the ladder, in the order that fixes it.
🎥 Watch the full Synology VPN setup in the video, step by step
Do not reinstall anything. This failure has a short list of causes and every one is a setting. Start at the top of the ladder — the tick box everyone misses — and stop the moment your files open, because the ladder is ordered by how often each rung is the real answer.
Phone · VPN Connected, NAS Unreachable
VPN statusConnected
Open DSM 192.168.1.10Timeout
Shared folderNot found
Internet on phoneWorking
The tunnel is up and everything on the other side is silent. Work the ladder — do not reinstall anything.
1
Check the LAN Access Tick Box First
This single setting causes most cases. Without it, the VPN happily connects you to the NAS itself and to nothing else on your network.
In DSM, open VPN Server → OpenVPN
Tick Allow clients to access the server's LAN
Apply, disconnect the phone, and reconnect — the setting applies to new connections
2
Use the NAS Home Address, Not Its Name
Names like DISKSTATION are resolved by your home network's local discovery, which often does not cross the VPN. Numbers always work.
Open the NAS by its fixed LAN address, for example http://192.168.1.10:5000
For shared folders, connect to 192.168.1.10 directly in your file app instead of browsing for the NAS
If the address works and the name does not, your VPN is healthy and only name discovery is missing — live with the address or bookmark it
3
The Same-Subnet Clash
The sneakiest cause. If the network you are visiting (a hotel, a friend's house, many offices) also uses 192.168.1.x, your phone cannot tell "router here" apart from "NAS at home" — both claim the same addresses, and the phone keeps everything local.
Check the Wi-Fi details on your phone: if its own address is also 192.168.1.something, you have found the clash
The lasting cure is at home: change your home LAN to a less common range like 192.168.50.x or 10.0.0.x on the router, and give the NAS its fixed address in the new range
Yes, this means redoing the fixed address and the port forward. It is an hour of work that ends this failure class forever
4
Check the DSM Firewall Allows Your VPN Range
VPN clients arrive from a virtual range (default 10.8.0.x). A strict DSM firewall can let the tunnel form and still refuse everything the tunnel carries.
Open Control Panel → Security → Firewall
Make sure your allow rules for DSM services and file sharing are not limited to the LAN range only
Test by reaching DSM on its LAN address through the VPN before testing shared folders — DSM answering means the road is open
5
Last Rung — Read What the NAS Saw
In VPN Server, open the Connection List and Log pages while you reproduce the problem
If your login appears and bytes move both ways, the tunnel is fine and the problem is addressing (rungs 2 and 3)
If bytes only leave the phone and nothing returns, suspect the firewall rung or a router that drops the traffic
Change one rung at a time and retest — changing three things at once teaches you nothing
🎥 Watch the Complete Process in the Video
The video shows a clean working setup; if yours connects but stays silent, this ladder finds the difference.
VPN shows connected but the NAS page times out. What is the first check?
The 'Allow clients to access the server's LAN' tick box in VPN Server → OpenVPN. It is disabled in many setups and produces exactly this symptom: connected, but nothing opens.
Why does the VPN work at one hotel and fail at another?
Probably the subnet clash. If the hotel network and your home network both use 192.168.1.x, the phone cannot route to your home addresses. Moving your home network to a less common range like 192.168.50.x fixes it permanently.
Should I reinstall VPN Server when this happens?
No. This failure is always a setting, never a broken install. Work the ladder: LAN access tick, IP address instead of name, subnet clash, DSM firewall, then the logs.
This guide is based on the Technical Anshu Synology NAS VPN video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏