VPN connection OK, but no remote access to folders

[petervbreemen]

A few weeks ago I set up a PPTP VPN connection using the VPN service on my QNAP-TS110 fw 3.6.0.
I then could remotely see and get access to the folders and files of my NAS on my Ipad, using the app FileBrowser. (Router firewall configuration seemed to be OK).
On May 4th I upgraded my NAS to fw 3.6.1
Two days ago I tried to get access to the NAS with FileBrowser on my Ipad from a remote network again. Didn't work! Got an error message in the app that it could not connect. Of course I first made a VPN connection in the Ipad Settings.
There is a VPN connection: The Ipad says "connected" and the VPN service on my NAS says " connected" as well. But it is not possible to connect to my NAS's files and folders anymore.
I spent hours and hours to solve the problem, but no results.
Even downgraded the NAS fw to 3.6.0. (and, in the end, upgraded it again to 3.6.1)
Also tested this with a windows 7 laptop in a remote network. This also got a VPN connection, but didn't show my NAS as a network device.

Any suggestions to fix this????

[petervbreemen]

I resolved the problem myself by looking around in the forum.

When using a VPN-connection with the NAS VPN service, I have to use 10.0.0.1 as the "local" IP address of the NAS to get connected to the NAS's folders, instead of the local IP address (in my case: 192.168.2.5) of the NAS in my home network.

I think this is a bad design of the VPN service in the QNAP software. To my logic it should bridge to the NAS's local IP address, provided by (in my case) the home network DHCP server (router). I am going to report this to QNAP as a request for improvement

[schumaku]

I resolved the problem myself by looking around in the forum.

Your original post left the impression, this VPN was operational for you on 3.6.0 before...

When using a VPN-connection with the NAS VPN service, I have to use 10.0.0.1 as the "local" IP address of the NAS to get connected to the NAS's folders, instead of the local IP address (in my case: 192.168.2.5) of the NAS in my home network.

Yes - this is because there is no NAT loopback in place, because of...

I think this is a bad design of the VPN service in the QNAP software. To my logic it should bridge to the NAS's local IP address, provided by (in my case) the home network DHCP server (router).

...which can not work.

1. Make the VPN subnetworks complete routed networks. This would be the perfect approach - but it will create routing challenges most home/SOHO/SMB users cant handle, ie. configuring routes on the internet router for each VPN subnet, pointing the NAS LAN IP.
2. Map (name it bridge if you want) the VPN client IP addresses in a pool reserved on the users home network (LAN). Like that, every VPN client appears to be a part of the home network, able to browse, and so on. For unexperienced users, this might be the best solution - but requires the reservation of an address block on the LAN for VPN purposes. Still to much administration for most users.
3. Hide the VPN subnetwork, and NAT all traffic form the VPN to the LAN. this is the most simple approach QNAP has implemented - with the constraint mentioned above.

[petervbreemen]

Yes, I tested a VPN connection from my neighbour's network and could connect to the NAS's shared folders using the NAS's local IP (192.168.2.5).

I had to enter the WPA2 password to get connection to my neighbour's wifi-network, which proved to me I was in a remote network.

This worked before I updated the firmware from 3.6.0. to 3.6.1

[young]

you had to change all ip client and router (from 192.168.2.X to 10.0.0.x) of your lan? I have the problem too and I cannot change subnet of my lan

[schumaku]

you had to change all ip client and router (from 192.168.2.X to 10.0.0.x) of your lan? ü/quote] Nope forget - do _not_ use the same TCP/IP subnetwork for the VPNs and for the LAN.

I have the problem too and I cannot change subnet of my lan

YOu don't have to . To connect ot the NAS from the VPN, jut use 10.0.0.1 (resp 10.8.0.1) instead of the LAN IP...

[young]

Thank you. I must to connect in lan with 192.168.0.x and from vpn with 10.0.0.2. It is not handy but now I can use my folders from vpn.

[schumaku]

I must to connect in lan with 192.168.0.x and from vpn with 10.0.0.2.

10.0.0.1 (for PPTP VPN) resp. 10.8.0.1 (for OpenVPN) I'd say... when using the default VPN pool config.

It is not handy but now I can use my folders from vpn.

True - but that's the way it is for now.