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

Cannot contact some servers


Occasionally, I work with folks who have DirectAccess running, but down the road they realize that there may be a server or two that are not contactable from the DirectAccess clients for some reason. I'm not talking about the same thing as above, where the client application itself isn't working, but this would be something like a ping or RDP access to a particular server just isn't getting to its destination inside the network. There are a number of different things that could cause such behavior.

Routing

You may notice that you cannot contact a whole set of servers, and then realize that all of these servers are within the same subnet inside your network. This is the first thing I always check when working on a selective server access issue; make sure that the routes exist on the DirectAccess server. Because the internal NIC on the DA server does not have a default gateway, that means we have to build the routing table ourselves from the command prompt. If you...