Configuration Scenario

New_Network
Week3-ConfiurationScenario.docx

Running head: VPN, DIRECTACCESS, AND WINDOWS ROUTING

VPN, DIRECTACCESS, AND WINDOWS ROUTING 2

Ray’s Food: VPN, Direct Access, and Windows Routing

Michael Boddie

Administering Windows Server

NTC/326

Sokly Vann

March 12, 2018

Introduction

In this week, I will detail some of the actions that are required to configure VPN, direct access services and routing in windows server 2012 R2 so as to give Ray’s customers a remote access to some of the organization services

Why VPN, Direct Access, and windows routing

Virtual Private Network (VPN) is a computer technology which allows the extension of local network on a public network just like the internet. By using VPN, a user computer which is connected to the internet can send or receive data from other computers inside the network as if the computer was connected directly. To configure VPN is very easy especially on Windows 2012 R2. Direct Access is a feature both in Windows 2008 R2 and windows 2012 R2. It allows remote connectivity to the corporate network resources without the requirement of VPN. Windows routing provides traditional VPN connectivity for legacy clients.

Requirements for configuration

When doing so, Ray’s need to configure the two network interfaces which are external and internal. This configuration usually allows for better security. Only the external network interface is configured with the organization default gateway so as to allow remote internal subnets (Hicks, 2016).

Configuring VPN, Direct Access, and windows routing

To configure VPN and Direct Access the first step is to install the Remote Access Role. In here one obtains two consecutive IPv4 addresses which must be unique. Second, one creates a new DNS record for the server FQDN. The third step is obtaining a server certificate for IP-HTTPS connections. Forth, is creating a client security group policy. After this Remote Access Role feature will have been installed. The network administrator then opens up the Remote Access Management Console. After this one clicks on the Deploy Direct Access and VPN and then clicks finish.

To configure windows routing, one does the same as configuring VPN and Direct access by first installing remote access role then opening the server manager and clicking on manage and then selecting add roles and features. On reaching the step of roles services, routing option is selected then finishing the configuration process (Bartolo, 2014).

References

Bartolo, A. (2014). Step-By-Step: Enabling DirectAccess in Windows Server 2012 R2. Retrieved March 8th, 2018, from Microsoft TechNet: https://blogs.technet.microsoft.com/canitpro/2014/01/05/step-by-step-enabling-directaccess-in-windows-server-2012-r2/

Hicks, R. (2016). Configure VPN in Windows Server 2012 R2. Retrieved March 8th, 2018, from Technix: http://techgenix.com/configure-vpn-windows-server-2012-r2/