In this demo was your home PC on the same local subnet as the domain controller? If so how do you route traffic via the VPN instead of directly? And when connecting via public IP does this configuration automatically supply a static route to the server's local subnet?
Thanks' very useful, point 11:37 is not clear "what mydomain are you talking about" ?
That refers to your local doman, usually mydomain.local or mydomain.int..... these are local domains that are not visible online. Thanks
In this demo was your home PC on the same local subnet as the domain controller? If so how do you route traffic via the VPN instead of directly? And when connecting via public IP does this configuration automatically supply a static route to the server's local subnet?
The answer is yes. As long as you know the destination public IP, you will always be able to connect to the local subnet.
Hi!
Does this tutorial work in a Windows Server 2012? (not R2)
I have not tested in Windows 2012, but I think it will work the same way. Thanks
I closed out of "post deployment configuration" too early and now I can't get back into that menu. Help.
I'm getting the feeling this is NOT the solution to bypass my IPS's blocking on port 80 and 443 on my home web server by way of a VPN?!?!?
No, I don't think so. This is VPN using port 1723.
Does the home PC need to join the domain? I've se this up for an actual office but it connects then disconnects after 60 sec
No, the phone PC does not need to be joined to the domain. Check the connection and see if it has a time-out configured.
Great tutorial, worked on the first try. Thanks!
Glad it helped!