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

Clients with native IPv6


The past year of so has shown an increasing amount of DirectAccess client computers that are receiving a native IPv6 address for internet browsing, for one reason or another. What usually happens is that I receive a call about a particular client computer that isn't working at a customer, and I ask that they ship me some logfiles. In those logfiles, right away in the ipconfig, I can see that there is a native IPv6 address listed on one of the regular network adapters. Typically, these addresses start with 2600:, and they can show up on either a LAN adapter or wireless adapter, if this address came from a home router, for example. Otherwise they can also show up on the adapter installed from a cell phone card. I would say the cell cards are more common from what I have seen, but the core of the problem is the same in either case. If you see this IPv6 address, and you will probably also see a 2001: or 2002: address listed for either Teredo or IP-HTTPS as you normally...