Book Image

Microsoft DirectAccess Best Practices and Troubleshooting

By : Jordan Krause
Book Image

Microsoft DirectAccess Best Practices and Troubleshooting

By: Jordan Krause

Overview of this book

DirectAccess is an amazing Microsoft technology that is truly the evolution of VPN; any Microsoft-centric shop needs this technology. DirectAccess is an automatic remote access solution that takes care of everything from planning to deployment. Microsoft DirectAccess Best Practices and Troubleshooting will provide you with the precise steps you need to take for the very best possible implementation of DirectAccess in your network. You will find answers to some of the most frequently asked questions from administrators and explore unique troubleshooting scenarios that you will want to understand in case they happen to you. Microsoft DirectAccess Best Practices and Troubleshooting outlines best practices for configuring DirectAccess in any network. You will learn how to configure Manage Out capabilities to plan, administer, and deploy DirectAccess client computers from inside the corporate network. You will also learn about a couple of the lesser-known capabilities within a DirectAccess environment and the log information that is available on the client machines. This book also focuses on some specific cases that portray unique or interesting troubleshooting scenarios that DirectAccess administrators may encounter. By describing the problem, the symptoms, and the fixes to these problems, the reader will be able to gain a deeper understanding of the way DirectAccess works and why these external influences are important to the overall solution.
Table of Contents (13 chapters)
Microsoft DirectAccess Best Practices and Troubleshooting
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Setting up the Network Location Server (NLS)


The Network Location Server is a very simple requirement in the DirectAccess environment, but a very critical one. NLS is just a website; it doesn't even have to be a dedicated server, that runs only inside the corporate network. It is not publicly accessible. Every time that the DirectAccess client computers get a network connection, they query this website. If they see it, they will know that they are inside the network, and that they do not need to turn on DirectAccess. Specifically, what this does is disables the Name Resolution Policy Table (NRPT), so that the name resolution requests do not attempt to be pushed over the DirectAccess tunnels, which wouldn't exist if you were inside the office. On the flip side, if your client computer cannot validate NLS, it assumes you are out in the wild and ready to fire up that DA connection in the background, and so that process is initiated automatically.

With Server 2012 DirectAccess, there is an option...