Does windows 10 have built in VPN hosting?

[Jonathan_192]

Ok so after much frustration, and pulling of hair, I have given up on figuring this out myself.

As I understand it windows 10 has a built in VPN service, I am trying to host a VPN server on my machine and be able to access the internet through the VPN on my local system.

I tried a couple of youtube videos, but I seem to hit a stumbling block.

I have setup "incoming connections" on my network adapter settings, I have assigned user's to allow through "incoming connections" by entering usernames and passwords. I create a new VPN, and tell it to connect through my public IP address, I then choose to connect to the VPN and it propmts me for username and password, I enter the same ones that I previously authorized under "Incoming connections"

and I get this error message:

The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.

I am starting to think I have some fundamental misunderstanding of the way that this works, does windows 10, not actually have VPN hosting functionality built in, and only has convienant options for connecting to VPNs?

That would actually make alot of sense now that I think about it.

 

[bill001g]

It does but your router needs a special feature related to vpn passthrough turned on. Most routers now have this feature but many have it disabled by default.

Not sure why you are getting ipsec messages windows I though only supported PPTP but its been a long time since I did this on a windows box I always do it on my routers.

The main problem with most VPN though NAT routers is that PPTP uses GRE to carry the data. The session setup and all the key exchange is done via normal tcp/udp port numbers. It then attempt to open a GRE session to carry the actual data. Since this is not TCP/UDP it does not use things like port forwarding rules. It has exactly the same problem though with connecting to the internal machine. The VPN passthough stuff is almost a hack that allows this to function. It is fine with a single vpn you try to run multiple and you have all kinds of problems.

If you continue to have troubles load wireshark on both end devices and capture the traffic. It does a pretty good job of letting you see the actual communications and many times you can see why the session is failing.

 

[Jonathan_192]

It does but your router needs a special feature related to vpn passthrough turned on. Most routers now have this feature but many have it disabled by default.

Not sure why you are getting ipsec messages windows I though only supported PPTP but its been a long time since I did this on a windows box I always do it on my routers.

The main problem with most VPN though NAT routers is that PPTP uses GRE to carry the data. The session setup and all the key exchange is done via normal tcp/udp port numbers. It then attempt to open a GRE session to carry the actual data. Since this is not TCP/UDP it does not use things like port forwarding rules. It has exactly the same problem though with connecting to the internal machine. The VPN passthough stuff is almost a hack that allows this to function. It is fine with a single vpn you try to run multiple and you have all kinds of problems.

If you continue to have troubles load wireshark on both end devices and capture the traffic. It does a pretty good job of letting you see the actual communications and many times you can see why the session is failing.

Sorry about the couple days late response, But I looked into my router settings and it does infact, have a VPN passthrough option that is checked. Any ideas that I could try for troubleshooting?

 

[bill001g]

Run wireshark on your pc and see if you are even getting traffic to pass though the router.