12,549
edits
FireBrick Road Warrior Windows 10: Difference between revisions
m
→Windows not setting the VPN as the gatweway?
|
On our Windows 10 machine, the VPN connected, but traffic was still going out via our normal network connection and not over the IPsec VPN. eg, a tracert shows traffic going via our local router and not over the VPN.
We were also unable to open the TCP/IP properties of the VPN connection. Others seem to have the problem, eg [[http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/pptp-vpn-cant-open-tcpip-propities/130425bc-7997-4b50-b535-6c590805df9d|here]] and [[https://social.technet.microsoft.com/Forums/en-US/af1cce20-ae21-4e89-bebc-11dc17becea5/no-access-to-internet-protocol-v4-or-v6-in-10049|here]], but those post are about preview releases and our Windows 10 is the final release. The button isn't grayed out on our case, it just does nothing when clicked!
The problem with the routing, is that the VPN connection is set up by default for 'SplitTunneling', which is not supported by the FireBrick. The way to disable SplitTunneling is via the command-line tool 'PowerShell' which is included with Windows 10, here is how:
Load PowerShell via:▼
Start/Windows button -> type: PowerShell -> Click on 'Windows PowerShell Desktop app'▼
▲#Load PowerShell via:
Get-VpnConnection▼
Set-VpnConnection -Name "vpnname" -SplitTunneling $False▼
#Type the following command to list the VPN connections:
#You will notice the Name of the connection as well as the 'SplitTunneling' setting being set to True.
#Disable SplitTunneling with the following command:
▲
(If needed you can re-enable SplitTunneling by changing False to True)
<gallery heights=200 mode="packed" caption="Powershell screenshot">
| |||