VPN & SAMBA on Same Server -- Cant Access SAMBA

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
marc25v
Posts: 2
Joined: Mon Nov 04, 2019 10:15 pm

VPN & SAMBA on Same Server -- Cant Access SAMBA

Post by marc25v » Mon Nov 04, 2019 10:20 pm

Hi all,

I am attempting to figure out how to access my SAMBA shares that are on the same server as the VPN when connected as a VPN client.

Current Architecture:
- Client: iOS / Android Mobile Device -- On Mobile Data
- VPN Server: Linux Raspberry PI -- 192.168.0.2
- Samba Server : Same as the VPN Server -- 192.168.0.2

-----
What Works:
- Connected to the VPN, I can access the internet AND all LOCAL network drives and devices, EXCEPT the Raspberry PI running the Server and the Samba shares.

What Doesnt Work:
- I cannot access the 192.168.0.2 IP address when I am connected via VPN.

What I Would Hope to Work:
- When connected to the VPN, I can access Internet, and ALL local devices on the network, including the Raspberry PI 192.168.0.2.

----
Any suggestions? Thanks!

jennylove
Posts: 8
Joined: Tue Nov 05, 2019 6:08 am
Location: Dallas, TX

Re: VPN & SAMBA on Same Server -- Cant Access SAMBA

Post by jennylove » Tue Nov 05, 2019 6:54 am

Can you ping the samba server? Access its shares via \\IPADDRESS? Is the samba server on the same subnet as everything that can be seen?

marc25v
Posts: 2
Joined: Mon Nov 04, 2019 10:15 pm

Re: VPN & SAMBA on Same Server -- Cant Access SAMBA

Post by marc25v » Tue Nov 05, 2019 1:34 pm

Hi

I cannot ping the samba share or even SSH into the server when connected. I cannot connect to the share even using the IP address. Yes, it is on the same subnet.

Thanks a lot

ozone
Posts: 57
Joined: Thu Sep 19, 2019 7:18 pm

Re: VPN & SAMBA on Same Server -- Cant Access SAMBA

Post by ozone » Wed Nov 06, 2019 12:15 am

This is a known issue on (at least) linux.

Try bridging the virtualhub to a new tap-device (on vpnserver).
Give this tapdevice in Raspbian a new (fixed, unused) ip-address, eg 192.168.0.3.
From the vpn-clients, use that new ip-address to access the resources on the pi.

Success,

Oz

Post Reply