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

No ISATAP with multisite DirectAccess


If you remember back a few pages, we talked about Windows preferring IPv6 over IPv4 whenever v6 is available. That, combined with the fact that an internal computer's ISATAP connection essentially default-routes all IPv6 traffic to its ISATAP router (the DirectAccess server) all the time, means that ISATAP and multisite DirectAccess don't really work together. If you had multiple DirectAccess entry points, each one of them running as an ISATAP router, your internal servers or PCs that you intend to join to the ISATAP network can only point one place. So they are going to hit either Site A or Site B, not both. This means that their responses to the client machines are always going to go out whichever site they are connected to for ISATAP. If a DirectAccess client is coming in through Site A and the Helpdesk computer is ISATAP connected to Site A, that will work fine. If a DirectAccess client is coming in through Site B, however, the packets from the Helpdesk...