e2e: Direct Access single server setup with mixed IPv4 and IPv6 environment

Notice

This article is one in a series of articles on end-to-end configuring and troubleshooting of DirectAccess. For a complete list of the series, see End-to-end configuring and troubleshooting DirectAccess .

Summary

This guide provides step-by-step instructions for configuring DirectAccess in a single server deployment with mixed IPv4 and IPv6 resources in a test lab to demonstrate functionality of the deployment experience. You will set up and deploy DirectAccess based on the Windows Server 2012 Base Configuration by using five server computers and two client computers. The resulting test lab simulates an intranet, the Internet, and a home network, and demonstrates DirectAccess in different Internet connection scenarios.

Important The following instructions are for configuring a Remote Access test lab that uses the minimum number of computers. Individual computers are needed to separate the services that are provided on the network and to clearly show the desired functionality. This configuration is neither designed to reflect best practices nor does it reflect a desired or recommended configuration for a production network. The configuration, including IP addresses and all other configuration parameters, is designed only to work on a separate test lab network.Attempting to adapt this Remote Access test lab configuration to a pilot or production deployment can result in configuration or functionality issues.

Deployment information

Overview
Hardware and software requirements
Known issues
Steps for Configuring the Remote Access Test Lab

Deployment methods

This guide provides steps for configuring the computers of the Windows Server 2012 Base Configuration test lab, configuring Remote Access in Windows Server 2012, and demonstrating remote client connectivity. The following sections provide details about how to perform these tasks.
Step 1: Set up the Base Configuration Test Lab
Step 2: Configure DC1
Step 3: Create a security group for DirectAccess client computers
Step 4: Create a network location server DNS record
Step 5: Create ICMPv4 and ICMPv6 echo request firewall rules in domain Group Policy
Step 6: Configure APP1
Step 7: Install and Configure APP2
Step 8: Configure EDGE1
Step 9: Connect Client1 to Corpnet Subnet and Update Group Policy
Step 10: Connect CLIENT1 to the Internet subnet and test remote access
Step 11: Connect CLIENT1 to the Homenet subnet and test remote access
Step 12: Monitor the client connection on the EDGE1 DirectAccess server
Optional: Snapshot the Configuration
Властивості

Ідентифікатор статті: 3022362 – останній перегляд: 9 лист. 2015 р. – виправлення: 1

Зворотний зв’язок