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

Windows Firewall with Advanced Security


Another place on both the DirectAccess server and the clients that I frequent is Windows Firewall with Advanced Security (WFAS). From a command prompt, type wf.msc, and you will be presented with the WFAS console. Inside this console, the first screen we see is an "overhead view" of which firewall profiles are currently active. For the server, in our most common and recommended "edge" deployment, where you have an Internal and an External NIC, you should see both the Domain profile active (on the Internal NIC), and the Public profile active (on the External NIC). If you see any other behavior, you may have networking configuration issues or firewalls that are blocking your server's ability to contact the network resources that it needs. And then on the client side, it is important to know that the DirectAccess IPsec rules will only activate themselves when the NIC has been assigned either the Public or Private profiles, those rules will not be active...