Overview of the Test Lab Scenario

 

Applies To: Windows Server 2012 R2, Windows Server 2012, Windows 8

In this test lab scenario, DirectAccess is deployed with:

  • DC1—A server computer that is configured as a domain controller, Domain Name System (DNS) server, and Dynamic Host Configuration Protocol (DHCP) server.

  • EDGE1—A server on the internal network that is configured as the Remote Access server. This server has two network adapters; one connected to the internal network, and the other connected to the external network.

  • RSA—A server on the internal network that is configured as the RSA Authentication Manager server.

  • APP1—A server on the internal network that is configured as a web and file server, and an enterprise root certification authority (CA).

  • APP2—A server on the internal network that is configured as an IPv4 only web and file server. This server is used to highlight the NAT64/DNS64 capabilities. This guide uses Windows Server 2003 SP2; however, you can use any computer that is configured as an IPv4 only computer.

  • INET1—A server that is configured as an Internet DNS and DHCP server.

  • NAT1—A client computer that is configured as a network address translator (NAT) device using Internet Connection Sharing.

  • CLIENT1—A client computer that is configured as a DirectAccess client, and will be used to test DirectAccess connectivity when moving between the internal network, the simulated Internet, and a home network.

The test lab consists of three subnets that simulate the following:

  • A home network named Homenet (192.168.137.0/24) connected to the Internet by a NAT.

  • The external network represented by the Internet subnet (131.107.0.0/24).

  • An internal network named Corpnet (10.0.0.0/24; 2001:db8:1::/64) separated from the Internet by the Remote Access server.

Computers on each subnet connect using either a physical or virtual hub or switch, as shown in the following figure.