Windows 10: Windows 10 IKEv2 VPN connects but does not have internal network access

I test this in 2 different computers with windows 10 1809 with latest updates.

When I configure a IKEv2 VPN connection using the windows 10 configuration interface:





I can connect to the VPN and access internet connections but I cannot access the internal VPN network, after troubleshooting the problem I realized the issue is the lack of a setting for a gateway, you can find it in: adapter options, properties of the VPN adapter, Networking, IPV4 Properties, Advanced:




If I enable that option I can sucessfully connect to the servers in internal VPN network.


Then, I made a test creating the VPN using Network and Sharing Center interface, Setup a new connection or network, Connect to a workplace, use my internet connection (VPN) and after creation of the VPN adapter I changed in the security tab, the type from Automatic to IKEv2.




Finally I checked the gateway option and it was active by default, i havent had to activate it myself:




So I realize that the problem is that when you setup a new vpn IKEv2 connection using the windows 10 settings interface it does not enable the "Use default gateway on remote network" option, but that option gets enabled if you set up the IKEv2 VPN using the Network and Sharing Center interface.


I tried setting up a PPTP type VPN and it got the "Use default gateway on remote network" enabled on both, Windows 10 settings and Network and Sharing center interface. So this problem only happens with IKEv2 type VPN.

:)

 

A problem of Windows 10 VPN (Ikev2) connection

I tried to use ikev2 VPN on my windows 10 laptop, and connected successfully (at least it showed "connected"). However, when I checked my IP on google, it suggested that it didn't connect me to the VPN server at all. And other methods also proved that my
laptop didn't get access to the Internet via ikev2 VPN.

So are there anyone who also meet the same problem? Is it a bug on windows 10, or just something I do is wrong?

 

A problem of Windows 10 VPN (Ikev2) connection

I know this thread is old, but hopefully some info here can help those us bewildered by this new behavior in Windows 10 (desktop and mobile).

I replied with details in this thread
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/why-doesnt-the-vpn-work-on-windows-10-mobile/607d23f9-eff0-44f6-9308-bbd250569966, but here are the basics:

• This is a feature called Split Tunneling, and will send traffic through a VPN only when it is inaccessible to the underlying connection (wired, WiFi, LTE, etc).
• The way to get around it is to avoid selecting any specific protocol for your VPN connection. Instead, choose Automatic.
• Along with that, you must choose Automatic when the connection is first setup. Changing and saving it to any other option will re-enable split tunneling and the only option to return force all traffic through the VPN is to create a new VPN connection with
  Automatic.
• With Automatic, the protocols are tried in this order until a connection is made: IKEv2, SSTP, L2TP, and PPTP. Been this was since Windows 7 as those are most to least secure protocols.

Again, more details are in my reply in the link above. Hope this helps.

 

How to get on internal network to VPN to a client


I am looking for ways besides RDP to have employees connect to my work's internal network at another location so that they can VPN to one of their client's. The VPN connection only works from the internal network as their Sonicwall configuration is setup to allow it through IP's on my work's network.
Any third-party apps, Windows settings, or other suggestions are welcomed.
One suggestion by a friend was to use Cendio, an open source Linux remote desktop server.

I have a Windows Server 2016 Standard machine and several Windows 10 Pro machines