- Run VPN server from Windows 10 PC
- Access SAMBA shares located on VPN server at same IP address from VPN and LAN clients
LAN IP of VPN server: 192.168.123.4
VPN subnet: 10.8.0.0/24
VPN server IP: 10.8.0.1
I could access the shares of the VPN server from VPN clients via 10.8.0.1, but not 192.168.123.4.
Eventually, I gave up and ran the VPN server from the LAN gateway. Accessing the SAMBA shares via the same IP is critical for proper QuickBooks Multi-User support, so my hands were tied.
Now I'm taking another swing at it, but from an angle I hadn't thought of before: Access the shares via the VPN server IP (10.8.0.1) from LAN and VPN clients (192.168.123.0/24 & 10.8.0.0/24).
I'm dead in the water. Again. I can't ping the VPN server IP from a client on the LAN (not directly connected to the VPN). I have tried:
- Modifying the registry to enable IPEnableRouter and also started the Routing and Remote Access service
- Routing via LAN gateway
Code: Select all
ip route add 10.8.0.0/24 via 192.168.123.4 ....
- Routing on LAN client
Code: Select all
route add 10.8.0.0 mask 255.255.255.0 192.168.123.4