I'm trying to setup softether on Windows Server 2008 R2 X64 to access my Internal LAN. My setup is:
1 server with 2 NIC's
NIC1 -->192.168.0.1 (connected to internet) NIC2 --> 10.167.7.0 (connected to my LAN)
I have created two hubs:
HUB LAN --> It is locally bridged to the NIC 2, called "Intranet" on my windows server. This configuration was made on "Local Bridge Settings"
HUB VPN -->
1. Created 1 user called test.
2. Secure NAT is Enable. In secure nat Configuration Virtual host interface hast the IP 10.167.9.2 also DHCP is enable with the range from 10.167.9.10 to 10.167.9.200
In Edit static routing table to push i have 10.167.7.0/255.255.248.0/10.167.9.1, 10.167.9.0/255.255.255.0/10.167.9.1
After that i HAVE created a Virtual Layer 3 Switch called "Router" with the following configuration:
1. Virtual interface 10.167.7.6 mask 255.255.248.0 attached to Virtual Hub "LAN"
2. Virtual interface 10.167.9.1 mask 255.255.255.0 attached to Virtual HUB "VPN"
3. In routing Table default route 0.0.0.0/0.0.0.0/10.167.7.1 metric 1
But... the problem is that i can connect to the vpn and get an ip address from the pool 10.167.9.0 but i can't access my local lan. There is no ping to any other IP address on network 10.167.7.X or 10.167.9.0 and can't ping Layer 3 switch virtual interface 10.167.9.1
From my local network i can ping the virtual interface 10.167.7.6 on my Virtual Layer 3 switch
Some can help me to make it work? Any ideas?
I didn't find information about this kind of setup
PD: Excuse my bad english please!
Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
2 posts • Page 1 of 1
Hello there! Technically speaking, this statement: "10.167.7.0/255.255.248.0" is a wrong statement. Most likely that network devices accept it but with a little change, which is modifying it as follows: "10.167.7.0/255.255.248.0" >> "10.167.0.0/255.255.248.0". So when you try to access your LAN from the remote side, your packets, actually, are destined toward your local router on the remote side because you don't have a routing entry for your LAN subnet, which is 10.167.7.0. Let me know if you can change your mask then I would further help you solving your issue.