Book Image

Windows Server 2012 Unified Remote Access Planning and Deployment

Book Image

Windows Server 2012 Unified Remote Access Planning and Deployment

Overview of this book

DirectAccess, introduced in Windows Server 2008 R2, has been a ground breaking VPN-like connectivity solution, adopted by thousands of organizations worldwide. Allowing organizations to deploy without manually configuring every client and providing always-on connectivity has made this technology world-famous. Now, with Windows Server 2012, this has been made even easier to deploy, with a new friendly user interface, easy-start wizard and built in support tools.With Unified Remote Access, Windows server 2012 offers a unique way to provide remote access that is seamless and easier to deploy than traditional VPN solutions. With URA, the successor to DirectAccess, your users can have full network connectivity that is always-on. If you have deployed Windows Server 2012 or are planning to, this book will help you implement Unified Remote Access from concept to completion in no time!Unified Remote Access, the successor to DirectAccess, offers a new approach to remote access, as well as several deployment scenarios to best suit your organization and needs. This book will take you through the design, planning, implementation and support for URA, from start to finish."Windows Server 2012 Unified Remote Access Planning and Deployment" starts by exploring the mechanisms and infrastructure that are the backbone of URA, and then explores the various available scenarios and options. As you go through them, you will easily understand the ideal deployment for your own organization, and be ready to deploy quickly and easily. Whether you are looking into the simplest deployment, or a complex, multi-site or cloud scenario, "Windows Server 2012 Unified Remote Access Planning and Deployment" will provide all the answers and tools you will need to complete a successful deployment.
Table of Contents (17 chapters)
Windows Server 2012 Unified Remote Access Planning and Deployment
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Client troubleshooting


As we described earlier, the first thing to check in case of connectivity problems is the client-side routing and networking. If you can see the client appears in the monitoring console, that usually means that the client-side networking is ok. The first tunnel is "easy" for the client to establish, because it's a simple interaction between the URA client and server. The second tunnel is more complicated, because it requires the client to communicate with a domain controller through the first tunnel.

Establishing the second tunnel could fail for several reasons. First, if something is blocking the traffic from going through to the domain controllers, the Kerberos authentication would not complete. Second, if there's something wrong with the credentials that the client is using, the Kerberos authentication will fail and the tunnel won't be established. The trick is finding out which is it that we're dealing with.

The first step in looking into this is trying to access...