Direct Access Configuration

Implementing Microsoft DirectAccess Step by Step: Part 1

We have compiled five step implementation posts, this will help you to configure and monitor your Microsoft DIRECTACCESS using simple and complex scenario.

By completing this scenario the following goals will be accomplished:
  1.  Allow a workstation to seamlessly move between internal, public, and home networks      while retaining access to application servers.
  2. Enable IPv6 in an IPv4 network using IPv6 transition technologies.

This article is for Windows Server 2012 and Windows 7/8 technologies that will automatically enable and configure IPv6 using transitional technologies like IP-HTTPS, ISATAP, 6to4, and teredo.
 Additionally, the intended DirectAccess server must have two physical network interfaces. The first is connected directly to the Internet ( The second interface is connected to the internal network ( two NICs should be on different IP network.
For this scenario there are five servers and a client system. That we have configured and tested against during the scenario.

· DC01 (—Domain controller, DNS, and enterprise Certificate Authority server running Windows Server 2008 R2. The Active Directory domain is example.local The CA must have an Internet available certificate revocation list (CRL) or you should have public Certificates for your DA.

· DA ( &—DirectAccess server and domain member running Windows Server 2012, with two network interface cards, and one public IP addresses (108.0.x.x) assigned.

· FLSrv (—File server and domain member that the DirectAccess client is accessing.

· Webmo (—Web server and domain member that the DirectAccess client is accessing. This server also hosts the NLS Web site, using the URL http://webmo-webprobehost.example.local

· Client1 (—DirectAccess client and domain member running Windows 8. This system will travel between the internal and public networks.


0 Responses to “Direct Access Configuration”

Post a Comment

Windows Admin Jobs in Pune