Enable and Configure Direct Access on Windows Server 2012 Essentials for Windows 8 Clients

Video is ready, Click Here to View ×

Enable and Configure Direct Access on Windows Server 2012 Essentials for Windows 8 Clients.

If you like the Video please Subscribe, like and Share

Like me on

Follow me on

Restart-Service RaMgmtSvc

Get-ChildItem -Path…


  1. The last 4 commands dont work on my client.. It comes up with the error 'Get-DnsClientNrptPolicy is not recognised as the name of a cmdlet, function, script file, or operable program'. please help!

  2. This works great except I have a red x on my "network location server". It says "Network location server: not working properly" the operations status is "url availability". Any idea how to figure out where the cause of the problem is or how to fix it? I have been pulling my hair out for a week on this! Thanks for the great tutorial.

  3. can you make a video how to enable nat on windows server 2012.
    your direct access guide do not work for me, I have two net work adapters one for lan and one for internet. It gives an error messasges that an adapter without domain profile could not be found.

  4. Only the following operating systems can be used as DirectAccess clients: Windows Server 2012, Windows Server 2008 R2, Windows 8 Enterprise, Windows 7 Enterprise, and Windows 7 Ultimate.

  5. I see your client is running windows 8 enterprise evaluation version, will this work if the client is running windows 8 pro retail version, can't get the network connectivity assistant to start so I have no DA Connection Status, any way to workaround this issue or the only way to solve it is to get windows 8 enterprise version

  6. if you are starting from scratch. you have to delete all the old certificates from MMC Certificates > Personal and if your public ip is dynamic be sure update you domain dns record of remote xyz com with public ip otherwise vpn test will not pass.

  7. ok, Can you check how many IPv4 & IPv6 DNS records of directaccess-WebProbeHost.yourdomain.local in DNS Server. if you don't find IPv6 AAA record of directaccess-WebProbeHost.yourdomain.local create IPv6 AAA record pointing to WSE server IPv6 Address after restart the server, connect the client locally run gpupdate /force ipconfig /registerdns then connect client remotely and run Get-DAConnectionStatus hope this will solved the problem. do let me know.

  8. connect the client remotely and run those two commands on power shell
    netsh interface h t t p s tunnel show interfaces (remove the spaces in between h t t p s) and send me the output.

  9. First Step-on WSE server please check port 443 is responding on your public IP to test this go to t1shopper com/tools/port-scan/ enter port # 443 and click scan you should get reply with red color saying responding if yes go to step second if not please check your router configuration. Second Step – on the client while connected locally give Get-DAConnectionStatus command on power shell you should get Status-Connected Locally. if not recheck DnsClientNrptPolicy has applied properly. let me know

  10. Thankyou so much! I followed the technet article but it didn't seem to cover all of the points you have demonstrated. I bashed my head against the wall for a full day before I found your video, an hour later direct access is working. Thanks again

Leave a Reply

Your email address will not be published.