When I connect using the Softether VPN client to my VPN server, I cannot get any access to the shared folders. I am using the Virtual DHCP function which gives my client the address 192.168.30.10. I have tried with both the secureNAT function on and off, indeed through trial and error I have tried all sorts of things but with no success.
I have all firewalls disabled and can ping the VPN server 192.168.30.1 fine, but when I do \\192.168.30.1, my client fails to connect at all. Neither client nor server are on a domain. I disabled the encryption on the connection too for the moment.
I really don't know where to go from here.
Please, I really need some help with this.
Windows Shared Folders on VPN Server
-
- Posts: 329
- Joined: Wed Sep 18, 2013 1:49 pm
Re: Windows Shared Folders on VPN Server
192.168.30.1 is not the VPN server address. 192.168.30.1 is the SecureNAT (Virtual Router/ Gateway) address. SecureNAT feature when enabled creates a "Basic Virtual NAT ROUTER" that sits "behind" the Local Physical Network router. Your VPN server Host address is the one that was given by the Local Physical (Home/Office Router) DHCP server. Example: Your local network (Home/Office Router) is say 192.168.1.X. Your SE- VPN server software is installed on a Host( PC, Laptop, other) at 192.168.1.10. Your VPN clients would find the VPN server Shares at \\192.168.1.10
-
- Posts: 6
- Joined: Tue Oct 13, 2020 2:49 pm
Re: Windows Shared Folders on VPN Server
That is a real shame. I don't want VPN clients to be able to access shares thought the 192.168.1.X subnet, I wanted to force VPN clients to use the 192.168.30.X subnet so that their connections would be encrypted. Is there no way to do that?
-
- Posts: 30
- Joined: Thu Dec 03, 2020 6:15 pm
Re: Windows Shared Folders on VPN Server
Hi KaledDavros,
When you establish the VPN connection from your local client device to the SEVPN, the connection is already encrypted (default is AES-128). The SEVPN allows users to access network resources (such as map drives) behind the VPN. It is not a shame where you cannot access \\192.168.30.1\, because it is by design. Your connection is already secure.
When you establish the VPN connection from your local client device to the SEVPN, the connection is already encrypted (default is AES-128). The SEVPN allows users to access network resources (such as map drives) behind the VPN. It is not a shame where you cannot access \\192.168.30.1\, because it is by design. Your connection is already secure.