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

What happened to Teredo?


Now that a lot of folks are moving to Server 2012 DirectAccess, I find environments all the time where all of the client computers are using IP-HTTPS for their transition tunneling technology. If Teredo is the most commonly used protocol out there in the wild, why does this happen? It is usually because a "shortcut" method was taken to implementing DirectAccess in the first place. If you have installed your DirectAccess server with only a single public IP address, or no public IP addresses at all and stuck it behind a NAT, then there is your answer. In either of these deployment scenarios, your only transition technology available to use is IP-HTTPS. Also, if you have checked the Force Tunnel checkbox during the wizards to push all traffic through the DA tunnels, this mode also locks you down to only IP-HTTPS. But, I also find many DA servers out there that do have the two consecutive public IP addresses, which should cause Teredo to work, but all of the clients...