![\"image\"](\"https:\/\/www.sqlskills.com\/blogs\/jonathan\/wp-content\/uploads\/2015\/05\/image18.png\" "\\"image\\"")
<\/a>![\"image\"](\"https:\/\/www.sqlskills.com\/blogs\/jonathan\/wp-content\/uploads\/2015\/05\/image21.png\" "\\"image\\"")
<\/a><\/p>\nThe final hardware configuration for the VM should then look like this:<\/p>\n
Now we can install Windows Server 2012 R2 and setup our basic server configuration.\u00a0 In this case I\u2019ve changed the name of the server to be DC, and set static IP\u2019s to each of the network adapters, 192.168.52.1 for VMNet2, and 192.168.53.1 to VMNet3.<\/p>\n To properly identify each adapter, you can edit the VM settings and disconnect them one at a time so it shows Network cable unplugged for the network connection.\u00a0 I usually set the NAT adapter to disconnected unless there is a need to have the VM connected to the internet through the host internet connection for some reason.\u00a0 Once this has been done we can proceed to setup the server as our Active Directory Domain Controller, DNS server, DHCP host for the networks, and as a Router between the two subnets.<\/p>\n To setup Active Directory Domain Services, open the Add Roles and Features Wizard, and then check Active Directory Domain Services as a role for the server.\u00a0 It will open a popup window shown below to add additional features required by Active Directory Domain Services.\u00a0 Click the Add Features button then click Next twice followed by the Install button.<\/p>\n When the installation finishes, don\u2019t click the Close button.\u00a0 Instead click on the link that says Promote this server to a domain controller<\/strong> to launch the Active Directory Domain Services Configuration Wizard.<\/p>\n Click Close<\/p>\n Click the Add a new forest radio button, then add the Domain Name and click Next<\/p>\n Set the domain functional level and then specify the recovery password and click next<\/p>\n Click Next<\/p>\n Click Next<\/p>\n Click Next and wait for the prerequisites checks to complete<\/p>\n Click Install and it will finalize the configuration of the Active Directory Domain Services on the server making it a new Domain Controller in the environment.\u00a0 When it finishes Windows will prompt to sign you out as shown below, and then the VM will reboot.<\/p>\n Configuring DHCP is not required, but it simplifies creating all the remaining VMs by automatically configuring their network settings based on the VMNet that they have been assigned on the virtual network adapters. Open the Add Roles and Features Wizard and add the DHCP Server role to the machine.<\/p>\n A popup will open with the additional features required and you can click Add Features.<\/p>\n Then click Next, followed by Install and when the installation finishes you can click the Complete DHCP Configuration.\u00a0 If you mistakenly click Close, you can still complete the configuration by opening Server Manager and then clicking on Manageability under the DHCP box.<\/p>\n This will open up the Manageability Detail View shown below.<\/p>\n Click Go To DHCP.<\/p>\n Click the More link at the top in the yellow bar to the far right<\/p>\n Click the Complete DHCP configuration link.<\/p>\n Click Next<\/p>\n Click Commit<\/p>\n This authorizes the server to be a DHCP host, so now we need to customize the configuration of DHCP. Click the Start button then type in DHCP and open the DHCP console.<\/p>\n Right click on the IPv4 and choose New Scope then click Next.<\/p>\n I name the scopes by the Subnet they apply to so in this case 192.168.52.x and once we complete this scope a second will have to be made for the 192.168.53.x subnet by simply repeating these same steps and using that subnet for the gateway and DNS server addresses.<\/p>\n Set the starting and ending IP address range for the scope and click Next. Then click Next on the Add Exclusions and Delay and Lease Duration windows.<\/p>\n On the Configure DHCP Options page, make sure it says Yes, I want to configure these options now and click Next.<\/p>\n Add the local IP address for this server as the Router address, in this case 192.168.52.1 and click Add, then click Next. (For the second scope you will use the other IP address, in this case the 192.168.53.1 address)<\/p>\n If the IP Address for the DNS Server is not the local address for the subnet, remove any existing IP addresses, and add the local IP address for the subnet, in this case 192.168.52.1 as the DNS server and then click Next. (Again, for the second scope you will use the other IP address, in this case the 192.168.53.1 address)<\/p>\n Remove any WINS server IP Addresses and click Next.<\/p>\n Then click Next to activate the scope.\u00a0 Now repeat these same steps for the 192.168.53.x subnet specifying the 192.168.53.1 address for the router and DNS server and activate that scope.<\/p>\n To setup routing between the subnets, open the Add Roles and Features Wizard, and then check Remote Access as a role for the server.<\/p>\n Click Next three times and then check the Routing box.\u00a0 It will open a popup window shown below to add additional features required for Routing.\u00a0 Click the Add Features button.<\/p>\n This will also cause the DirectAccess and VPN (RAS) option to become checked as shown below.<\/p>\n Click Next twice and it will have the addition IIS role services window shown below with the required features checked.\u00a0 Nothing needs to be changed here, just click Next again, followed by Install to install the Remote Access Role to the server.<\/p>\n When the installation completes, click Close.\u00a0 Now click on Start and type in Routing and Remote Access and open the Routing and Remote Access management console.<\/p>\n Right click on the server and select the Configure and Enable Routing and Remote Access<\/strong> option.<\/p>\n Click Next on the first window then select the Custom Configuration option and click Next.<\/p>\n Check the box for LAN routing and click Next.\u00a0 Then click Finish.<\/p>\n Now click the Start service button to start the Routing and Remote Access services.<\/p>\n <\/p>\n EDIT: After initially publishing this blog post, Thomas Stringer (Blog <\/a>| Twitter<\/a>) pointed out that static routes don’t have to be configured and RIP can be used to simplify the configuration of routing. \u00a0So I am updating this post with the RIP configuration as an additional section. Either option will work but I have to admit that RIP is easier to configure. You only need to configure RIP or the Static Routes, don’t configure both options.\u00a0<\/strong><\/p>\n Expand the IPv4 folder and right click on Static Routes and choose the New Static Route option.<\/p>\n Select the 192.168.52.1 interface and then add a Destination of 192.168.53.0, subnet mask of 255.255.255.0 and gateway of 192.168.53.1 to create a static route between the subnets.<\/p>\n Now create a New Static route again.<\/p>\n This time, change to the 192.168.53.1 interface and set the Destination to 192.168.52.0, network mask to 255.255.255.0, and the Gateway to 192.168.52.1 and click OK to add the static route between the subnets.<\/p>\n Restart the Routing and Remote Access Services and you\u2019re all set.<\/p>\n To test the configuration, I created two new VMs named SQL1 and SQL2 with a single network adapter each.\u00a0 SQL1 was configured on VMNet2 and SQL2 was configured on VMNet3, then joined both of the servers to the SQLskillsDomain.com domain.\u00a0 The Windows Firewall<\/strong> needs to be configured to allow ICMP echo packets in the Inbound Rules<\/strong> on each of the servers by enabling the File and Printer Sharing (Echo Request \u2013ICMPv4-In) <\/strong>rule that already exists in the Inbound Rules of the firewall. Once this is enabled on each of the servers, we can test with ping between the VMs as shown below:<\/p>\n<\/a><\/p>\n<\/a><\/a><\/p>\nConfiguring Active Directory Domain Services<\/h1>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nConfiguring DHCP<\/h1>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nConfiguring Routing Between Subnets<\/h1>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nRouting with Routing Information Protocol (RIP)<\/h3>\n
\n
Routing with Static Routes<\/h3>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nTesting<\/h1>\n
SQL1 to SQL2<\/h4>\n