Unable to access DSM via OpenVPN tunnel

Currently reading
Unable to access DSM via OpenVPN tunnel

3
0
NAS
DS1019+
Operating system
  1. Windows
Mobile operating system
  1. iOS
Hi - am running OpenVPN on my Untangle firewall... (not hosted on my Synology).

Have recently added a Synology Diskstation 1019+ to my LAN at 192.168.0.129. My Untangle NGFW 15.1 box is 192.168.0.1. I've setup OpenVPN on NGFW and the address space is: 172.16.28.0/24. When I'm connected to the LAN, I can access 192.168.0.129 on port 5001 without issue to access Synology's DSM management web interface.

However when I connect to OpenVPN, I'm able to access all machines on the LAN 192.168.0.x 255.255.255.0 except for the Synology on 192.168.0.129 HTTPS 5001.

Not sure whether it helps but on the local LAN accessing https://192.168.0.129 (the Synology admin address) redirects to HTTPS port 5001 as not secure due to self signed Synology certificate. This is normal behavior on the LAN. However once connected to OpenVPN, accessing https://192.168.0.129 is unable to redirect to port 5001. Also if I attempt to connect directly on https://192.168.0.129:5001 via Untangle OpenVPN, it doesn’t connect either. Using all Synology default settings which include firewall disabled. Also using default Untangle NGFW 15.1 OpenVPN setup. Have tried both full tunnel and split tunnel client connection, both behave the same.
 
After you tunnel in can you telnet 5000 or 5001 ports and connect to them via command line?

Thanks @Rusty for your response. This isn't something I've tried before. No, my attempt to telnet to either port returns: could not open connection to the host, on port xxxx: connect failed.
 
Ping is irrelevant here when it comes to testing out traffic and connectivity. Telent works you say? Using what port?

If you are getting could not open connection to the host it means that the port is not upon the destination side (probably not true considering those are main DSM ports) or you have traffic block at some level when accessing your NAS via the tunnel.

If you can't telnet those ports when you are inside the tunnel then you need to focus on that 1st.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Snapshot consumption can only be determined through the package itself... AFAIK, snapshots can only be...
Replies
10
Views
1,770
That would be a problem with browsing or email, but is it really an issue with bittorrent? Wouldn't it...
Replies
7
Views
2,272
  • Locked
CLOSING THREAD, as this was resolved here: Oh, No... DSM 7.1 *REMOVED* critical SSD/NVME Cache...
Replies
1
Views
3,629
Click the "start" button, then Package Center, then find Storage Analyzer, click on it, select the little...
Replies
15
Views
6,920
Hmm, another feature victim of DSM7, I never looked when I was running DSM6, but as the OP has stated, no...
Replies
12
Views
4,094
Yes, I'm on DSM 7, I'm willing to bet that takes up the extra 30%. Though I could check that with my 414j...
Replies
16
Views
6,156
  • Question
Ok, changing the ports didn't help. I refreshed the Synology / LE certificate too but that didn't seem to...
Replies
4
Views
2,513

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top