INF204x Module 1 Lab 2: Configuring and Troubleshooting Networking Part 2

Transcription

1 INF204x Module 1 Lab 2: Configuring and Troubleshooting Networking Part 2 Estimated Time: 60 minutes Your organization plans to expand the use of IPv6 in its existing Windows Server 2012 R2 Active Directory environment including Windows 10 computers. In preparation for this expansion, you need to evaluate the how IPv6 will be interacting with the existing IPv4 network communication. You need to minimize potential for any issues resulting from the dual IP stack. Objectives After completing this lab, students will be able to: Configure IPv6 addresses on a Windows 10 computer Configure DNSv6 settings on a Windows 10 computer Disable individual IP6 network components Lab Environment The lab consists of three virtual machines: LON-WIN10 - Windows 10 Enterprise client (Adatum.com Active Directory domain member) with IPv4 address of LON-WIN81 - Windows 8.1 Enterprise client (Adatum.com Active Directory domain member) with IPv4 address of LON-DC1 Windows Server 2012 R2 Datacenter server (Adatum.com Active Directory domain controller) with IPv4 address of This domain controller also serves a DNS Server role. Note: It is important to point out that, in general, you would likely rely on a combination of IPv6 capable router advertisements and a DHCPv6 server to configure IPv6 on Windows 10 client computers. However, in this lab, we will use static IPv6 address assignments in order to illustrate basic principles of IPv6 configuration and demonstrate techniques that you might find helpful while troubleshooting IPv6 related issues or setting up your own IPv6 lab. Exercise 1: Configure the Windows 10 and Windows Server 2012 R2 virtual machines with static IPv6 addresses. In this exercise, you will assign static IPv6 addresses to the Windows 10 and Windows Server 2012 R2 lab virtual machines and configure both with DNS server settings. The main tasks for this exercise are as follows: 1. Configure static IPv6 address and DNS server setting on the Windows Server 2012 R2 lab virtual machine (LON-DC1) 2. Configure static IPv6 address and DNS server setting on the Windows lab virtual machines (LON-WIN10 and LON-WIN81)

2 3. Verify that the lab virtual machines successfully registered their AAAA DNS records Task 1: Configure static IPv6 address and DNS server setting on the Windows Server 2012 R2 lab virtual machine (LON-DC1) 1. Sign in to the Windows Server 2012 R2 (LON-DC1) lab virtual machine with the following credentials: USERNAME: ADATUM\Administrator PASSWORD: Pa$$w0rd 2. On the lab virtual machine, launch Windows PowerShell by clicking on its icon in the taskbar. 3. In the Administrator: Windows PowerShell window, type the following and press the Enter Get-NetIPConfiguration InterfaceAlias Ethernet -Detailed 4. Examine the output and note that the Ethernet interface has both an IPv4 and IPv6 address assigned to it. The IPv6 address starts with fe80:: and has the prefix length of 64. This is a linklocal address. Note that this address contains a suffix (following the % sign) matching the network interface index. Note: Link-local addresses are functionally equivalent to IPv4 APIPA addresses since they facilitate communication within the local subnet. To find out more about link-local addresses, refer to IPv6 for the Windows Administrator: IPv6 Fundamentals at fundamentals/ 5. At the Windows PowerShell prompt, type the following and press the Enter key ncpa.cpl 6. In the Network Connections window, right-click Ethernet and click Properties in the rightclick menu. 7. In the Ethernet Properties dialog box, double-click Internet Protocol Version 6 (TCP/IPv6). 8. In the Internet Protocol Version 6 (TCP/IPv6) Properties dialog box, select Use the following IPv6 address option button. In the IPv6 address textbox, type in fd44:ecc6:e322::dc1. Note that your choice of IPv6 address is arbitrary, as long as the 64-bit prefix matches the one designated for the DHCPv6 scope (we decided to use dc1 as the Interface ID portion of the address purely for convenience). Ensure that the Subnet prefix length is set to In the Internet Protocol Version 6 (TCP/IPv6) Properties dialog box, select Use the following DNS server addresses option button. In the Preferred DNS server textbox, type in ::1. Note: The IPv6 address ::1 represents the loopback address, which in this case, points to the local DNS server. You could have used fd44:ecc6:e322::dc1 instead, however, the loopback address provides an additional benefit. If an IPv6 address of the server changes at any point in the future, the loopback address would still allow you to reach the local DNS server.

3 10. Click OK. 11. In the Ethernet Properties dialog box, click OK. Task 2: Configure static IPv6 address and DNS server setting on the Windows lab virtual machines (LON-WIN10 and LON-WIN81) 1. Sign in to the Windows 10 (LON-WIN10) lab virtual machine with the following credentials: USERNAME: ADATUM\Administrator PASSWORD: Pa$$w0rd 2. On the LON-WIN10 lab virtual machine, click the Windows logo in the lower left corner. Click All apps in the Start menu. In the All apps menu, click the Windows PowerShell folder. In the list of programs in the PowerShell folder, right click Windows PowerShell. In the right-click menu, click Run as administrator. 3. In the Administrator: Windows PowerShell window, type the following and press the Enter Get-NetIPConfiguration InterfaceAlias Ethernet -Detailed 4. Examine the output and note that the Ethernet interface has both an IPv4 and IPv6 address assigned to it. The IPv6 address starts with fe80:: and has the prefix length of 64. This is a linklocal address. Note that this address contains a suffix (following the % sign) matching the network interface index. Note: Link-local addresses are functionally equivalent to IPv4 APIPA addresses since they facilitate communication within the local subnet. To find out more about link-local addresses, refer to IPv6 for the Windows Administrator: IPv6 Fundamentals at fundamentals/ 5. At the Windows PowerShell prompt, type the following and press the Enter key ncpa.cpl 6. In the Network Connections window, right-click Ethernet and click Properties in the rightclick menu. 7. In the Ethernet Properties dialog box, double-click Internet Protocol Version 6 (TCP/IPv6). 8. In the Internet Protocol Version 6 (TCP/IPv6) Properties dialog box, select Use the following IPv6 address option button. In the IPv6 address textbox, type in fd44:ecc6:e322::c11. Note that your choice of IPv6 address is arbitrary, as long as the 64-bit prefix matches the one designated for the DHCPv6 scope. Ensure that the Subnet prefix length is set to In the Internet Protocol Version 6 (TCP/IPv6) Properties dialog box, select Use the following DNS server addresses option button. In the Preferred DNS server textbox, type in fd44:ecc6:e322::dc1. Note: The IPv6 address fd44:ecc6:e322::dc1 is the IPv6 address of the LON-DC1, which we assigned in the previous task of this exercise.

4 10. Click OK. 11. In the Ethernet Properties dialog box, click OK. 12. Switch to LON-WIN81 Windows 8.1 lab virtual machine. On LON-WIN81 Windows 8.1 lab virtual machine, from the Start screen, type Windows PowerShell. In the search result list, rightclick Windows PowerShell. In the right-click menu, click Run as administrator. 13. In the Administrator: Windows PowerShell window, type the following and press the Enter Get-NetIPConfiguration InterfaceAlias Ethernet -Detailed 14. Examine the output and note that the Ethernet interface has both an IPv4 and IPv6 address assigned to it. The IPv6 address starts with fe80:: and has the prefix length of 64. This is a linklocal address. Note that this address contains a suffix (following the % sign) matching the network interface index. Note: Link-local addresses are functionally equivalent to IPv4 APIPA addresses since they facilitate communication within the local subnet. To find out more about link-local addresses, refer to IPv6 for the Windows Administrator: IPv6 Fundamentals at fundamentals/ 15. At the Windows PowerShell prompt, type the following and press the Enter key ncpa.cpl 16. In the Network Connections window, right-click Ethernet and click Properties in the rightclick menu. 17. In the Ethernet Properties dialog box, double-click Internet Protocol Version 6 (TCP/IPv6). 18. In the Internet Protocol Version 6 (TCP/IPv6) Properties dialog box, select Use the following IPv6 address option button. In the IPv6 address textbox, type in fd44:ecc6:e322::c12. Note that your choice of IPv6 address is arbitrary, as long as the 64-bit prefix matches the one designated for the DHCPv6 scope. Ensure that the Subnet prefix length is set to In the Internet Protocol Version 6 (TCP/IPv6) Properties dialog box, select Use the following DNS server addresses option button. In the Preferred DNS server textbox, type in fd44:ecc6:e322::dc1. Task 3: Verify that the lab virtual machines successfully registered their AAAA DNS records 1. From the Windows 10 (LON-WIN10) virtual machine, in the Administrator: Windows PowerShell window, type the following command and press the Enter key: Resolve-DnsName Type AAAA Name LON-DC1.adatum.com -DnsOnly 2. The output should list a single AAAA DNS record providing translation between the LON- DC1.adatum.com name and its IPv6 address you assigned in the first task of this exercise (fd44:ecc6:e322::dc1).

5 3. At the Windows PowerShell prompt, type the following command and press the Enter key: Resolve-DnsName Type AAAA Name LON-WIN10.adatum.com -DnsOnly 4. The output should list a single AAAA DNS record providing translation between the LON- WIN10.adatum.com name and its IPv6 address you assigned in the second task of this exercise (fd44:ecc6:e322::c11). 5. At the Windows PowerShell prompt, type the following command and press the Enter key: Resolve-DnsName Type AAAA Name LON-WIN81.adatum.com -DnsOnly 6. The output should list a single AAAA DNS record providing translation between the LON- WIN81.adatum.com name and its IPv6 address you assigned in the second task of this exercise (fd44:ecc6:e322::c12). Note: This confirms that all lab virtual machines successfully registered their AAAA DNS records in the DNS server hosted on LON-DC1. We will use their ability to interact with the DNS server via DNSv6 in the third exercise of this lab. Results: After completing this exercise, you will have configured static IPv6 address and DNSv6 settings on all lab virtual machines (LON-WIN10, LON-WIN81, and LON-DC1). You also will have tested DNSv6 name resolution by verifying the presence of the LON-DC1, LON-WIN10, and LON-WIN81 AAAA records on the DNS server hosted on LON-DC1. Exercise 2: Configure IPv6 components on the Windows 10 lab virtual machine In this exercise, you will configure IPv6 components on the Windows 10 lab computer LON- WIN10. The main tasks for this exercise are as follows: 1. Identify active IPv6 components on the Windows 10 lab virtual machine (LON-WIN10) 2. Disable the IPv6 tunnel adapter on the Windows 10 lab virtual machine (LON-WIN10) and verify the outcome Task 1: Identify active IPv6 components on the Windows 10 lab virtual machine (LON-WIN10) 1. On the LON-WIN10 lab virtual machine, in the Administrator: Windows PowerShell window, type the following and press the Enter ipconfig 2. Examine the output and note that the tunnel adapter is enabled but disconnected. Note: Our intention in this case is to disable components that are not needed. You will disable the tunnel adapter in the next task of this exercise. Obviously your decision in such case should be based on a thorough analysis conducted to determine whether disabling such components does not have any negative implications on the functionality you might need.

6 Task 2: Disable the IPv6 tunnel adapter on the Windows 10 lab virtual machine (LON-WIN10) and verify the outcome 1. On the Windows 10 lab virtual machine (LON-WIN10), in the Administrator: Windows PowerShell window, run the following script: $registrypath = HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters $registryentry = DisabledComponents $registryvalue = 0x1 New-ItemProperty Path $registrypath Name $registryentry Value $registryvalue PropertyType DWORD -Force Note: This script sets the value of the DisabledComponents registry entry to 0x1, which effectively disables IPv6 on all tunnel interfaces. This registry entry also allows you to control other aspects of IPv6 behavior, including disabling it entirely. The configuration options are described in details in the Microsoft Knowledge Base article How to disable IPv6 or its components in Windows at Important: Keep in mind that the DisabledComponents registry entry is a bitmask, so any of its modifications should take into account its existing value (in order to avoid changes to already implemented features). In this lab, you simply set the value, since its original configuration is known (matching what was configured in the image on which the lab virtual machine is based). In real-world scenarios, you should first check whether the entry already exists and, if so, read its value first and modify only individual bit or bits that control the functionality you intend to implement. 2. Once the script completes, restart LON-WIN10 Windows 10 lab virtual machine. 3. Once LON-WIN10 restarted, sign in to it with the following credentials: USERNAME: ADATUM\Administrator PASSWORD: Pa$$w0rd 4. On the LON-WIN10 lab virtual machine, right-click the Windows PowerShell icon on the taskbar and select Run as Administrator. 5. In the Administrator: Windows PowerShell window, type the following and press the Enter ipconfig 6. Examine the output and note that the tunnel adapter is no longer listed. Results: After completing this exercise, you will have disabled the IPv6 tunnel interface on the Windows 10 lab virtual machine. Note: When you finish this lab select the End lab link to reset the virtual machines.