sign in sign up
<<
Home , Address pool, Alias (command), Cd (command), Copy (command), Default gateway, Df (Unix)

Lab Report: 5.1.7 Configure IP Addresses

Performance Your Score: 0 of 2 (0%) Elapsed : 14 seconds

Task Summary Actions you were required to perform: In Configure settings for Local Area ConnectionHide Details

Use 192.168.0.254 for the IP address Use 255.255.255.0 for the subnet mask Use 192.168.0.5 for the Use 163.128.78.93 or 163.128.80.93 as the preferred DNS server

In Configure settings for Local Area Connection 2Hide Details

Use 10.0.255.254 for the IP address Use 255.255.0.0 for the subnet mask Do not configure a default gateway address Do not configure a DNS server address

Explanation When configuring IP addresses, keep in mind the following:

You cannot assign the subnet address to a (such as 192.168.0.0 or 10.0.0.0). The /x notation identifies the number of bits in the subnet mask. /8 indicates a subnet mask of 255.0.0.0. /16 indicates a subnet mask of 255.255.0.0. /24 indicates a subnet mask of 255.255.255.0. Portions of the subnet mask that include a 1 identify the subnet address. This portion of the address must be the same for all on the subnet. Portions of the subnet mask that include a 0 identify the host address. This portion of the address must be unique between all hosts. You cannot assign the last address to a host (such as 192.168.0.255 or 10.0.255.255).

Use the following values for the TCP/IP properties in this scenario:

Default gateway Preferred DNS server Connection Host address Subnet mask address address 163.128.78.93 or 192.168.0.254 255.255.255.0 192.168.0.5 163.128.80.93 Ethernet 2 10.0.255.254 255.255.0.0 None None

Complete this lab as follows:

1. In the Notification area, right-click the Network icon. 2. Select Open Network and Sharing Center. 3. To configure the Ethernet adapter, select Ethernet. 4. In the Ethernet Status dialog, select Properties. 5. Select Protocol Version 4 (TCP/IPv4) 6. Select Properties. 7. sure that Use the following IP address is selected to manually configure the IP address and default gateway. 8. Enter the required IP address, subnet mask, default gateway, and preferred DNS server address; then select OK. 9. In the Ethernet Properties dialog, select Close. 10. In the Ethernet Status, select Close. 11. Select Change adapter settings to configure the other network adapter. 12. Right-click Ethernet 2 adapter, and click Properties. 13. Repeat steps 5 through 8 to modify the TCP/IP settings for the other network adapter. Lab Report: 5.1.8 Configure IP Addresses on Mobile Devices

Performance Your Score: 0 of 1 (0%) Elapsed Time: 8 seconds

Task Summary Actions you were required to perform: In Secure IMAP network communications and authenticate to CorpNet-Wireless Wi-FiHide Details

Enable SSL for IMAP communications Use port 993 Connect to CorpNet Wi-Fi

Explanation Complete this lab as follows:

1. Set the email account to use SSL and the secure port 993 as follows: a. Select Settings. b. Select , Contacts, Calendars. . Select Maggie Brown. d. Select [email protected]. e. Select Advanced. f. Slide the button to enable Use SSL. g. Verify that the server port is set to 993. h. the , select Account. i. Click Done. 2. Connect to CorpNet-Wireless Wi-Fi as follows: a. Click Wi-Fi. b. Click CorpNet. c. In the Password field, enter @CorpNetWeRSecure!& as the password. d. Click . Lab Report: 5.2.3 Configure Alternate Addressing

Your Performance

Your Score: 0 of 3 (0%) Pass Status: Not Passed Elapsed Time: 6 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Configure automatic IP addressing through DHCP In Configure automatic DNS addressing In Configure an alternate TCP/IP addressHide Details

IP address: 172.16.0.12 Subnet mask: 255.255.0.0 Default gateway: 172.16.255.254 DNS Server: 198.60.22.2

Explanation In this lab, you configure the Version 4 (TCP/IPv4) properties with the following settings:

On the General tab, set the following parameters: Obtain an IP address automatically Obtain DNS server address automatically On the Alternate Configuration tab, set the following parameters: IP Address: 172.16.0.12 Subnet Mask: 255.255.0.0 Default Gateway: 172.16.255.254 Preferred DNS Server: 198.60.22.2

Complete this lab as follows:

1. In the notification area, right-click the Network icon and select Open Network and Sharing Center. 2. In the left pane, select Change adapter settings. 3. Right-click Wi-Fi and select Properties. 4. Select Internet Protocol Version 4 (TCP/IPv4). 5. Select Properties. 6. Select Obtain an IP address automatically. 7. Select Obtain DNS server address automatically. 8. Select the Alternate Configuration tab to define an alternate configuration for TCP/IP addressing. 9. Select User configured to configure alternate IP settings. 10. Enter the IP address. 11. Enter the subnet mask. 12. Enter the default gateway. 13. Enter the preferred DNS server. 14. Click OK. 15. Click Close. 16. Select the Network icon in the notification area to view the currently connected network. Lab Report: 5.3.2 Configure a DHCP Server

Performance Your Score: 0 of 3 (0%) Elapsed Time: 10 seconds

Task Summary Actions you were required to perform: In Configure the IPv4 DHCP scope on ServerHide Details

Scope name: Subnet1 Address range: 192.168.0.1 to 192.168.0.254 Subnet mask: 255.255.255.0 Lease duration: Accept the default Default gateway (): 192.168.0.5 DNS Server: 163.128.78.93

In Activate the IPv4 DHCP scope on Server In Configure the laptop in the Support Office to obtain IP and DNS addresses automatically from the DHCP server Explanation In this lab, your task is to complete the following:

On the CorpDHCP server (running as a guest on CorpServer in the Networking Closet), create a DHCP IPv4 scope with the following parameters:

Scope name: Subnet1 Address range: 192.168.0.1 to 192.168.0.254 Length: 24 Subnet mask: 255.255.255.0 Exclusions and delays: Do not set Lease duration: Accept the default duration Scope option for the Router (default gateway): 192.168.0.5 Parent domain: Accept the default Scope option for DNS servers: 163.128.78.93 WINS Servers: Do not set On CorpDHCP, activate the Subnet1 scope. On the Gst-Lap laptop in the Lobby, confirm the DHCP scope settings by configuring the local area connection to obtain its IP and DNS addresses automatically from the DHCP server.

Complete this lab as follows:

1. Configure and activate the IPv4 DHCP scope on server as follows: a. In Hyper- Manager, select CORPSERVER. b. Resize the window to view all virtual machines. c. Right-click CorpDHCP and select Connect. d. Maximize the window for easier viewing e. In Server Manager, select Tools > DHCP. f. the DHCP server. g. Right-click IPv4 and select New Scope. h. In the the New Scope Wizard, select Next. i. In the Name field, enter the scope name; then select Next. j. In the IP address field, enter the start IP address. k. In the End IP address field, enter the end IP address. l. Make sure that the length is correct. m. Make sure that the subnet mask is correct; then select Next. n. In the Add Exclusions and Delay window, select Next. o. Use the default lease duration and select Next. p. Make sure , I want to configure these option now is selected; then click Next. q. In the IP address field, enter the default gateway address. r. Select Add; then click Next. s. In the IP address field, enter DNS server address. t. Select Add; then click Next. u. In the WINS Servers window, select Next. v. Make sure Yes, I want to activate this scope now is selected; then select Next. . Click Finish to close the wizard and create the scope. 2. Configure the laptop in the Lobby to obtain IP and DNS addresses automatically from the DHCP server as follows: a. From the top, select Floor 1 Overview. b. Under Lobby, select Gst-Lap. c. In the notification area, right-click the Network icon and select Open Network and Sharing Center. d. Select Ethernet. e. In the Ethernet Status window, select Properties. f. Select Internet Protocol Version 4 (TCP/IPv4). g. Select Properties. h. Select Obtain an IP address automatically. i. Select Obtain DNS server address automatically. j. Select OK. k. Click Close to close Ethernet Properties. l. Click Close to close Ethernet Status. Lab Report: 5.3.4 Configure DHCP Options

Your Performance

Your Score: 0 of 3 (0%) Pass Status: Not Passed Elapsed Time: 8 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Configure the 006 DNS Servers option on the server as 192.168.0.11 and 192.168.10.11 In Configure the 015 DNS Domain Name option on the server as CorpNet.com In Configure the 003 Routers option on the scope as 192.168.0.5 Explanation Complete this lab as follows:

1. Configure DHCP server options as follows: a. From Hyper-V Manager, select CORPSERVER. b. Maximize the Hyper-V Manager window to view the available server. c. Right-click CorpDCHP and select Connect. d. From Server Manager, select Tools > DHCP. e. Expand CorpDHCP.CorpNet.com. f. Expand IPv4. g. Right-click Server Options and select Configure Options. h. Under Available Options, select the 006 DNS Servers. i. Under IP Address, enter the IP address. j. Select Add to add the IP address to the list. k. Repeat steps 1i-1j to add additional IP addresses. l. Click Apply. m. Under Available Options, select 015 DNS Domain Name. n. In the String value field, enter CorpNet.com. o. Click OK to save the options you have defined. 2. Configure DHCP scope options as follows: a. Expand Scope [192.168.0.1] Subnet1. b. Right-click Scope Options and select Configure Options. c. Under Available Options, select the 003 Router. d. Under IP address, enter 192.168.0.5. e. Click Add to add the IP address to the list. f. Click OK to save the options you defined.

Server options apply to every scope on the server. Scope options override the server settings for a specific scope. Lab Report: 5.3.5 Create DHCP Exclusions

Your Performance

Your Score: 0 of 1 (0%) Pass Status: Not Passed Elapsed Time: 8 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Create an exclusion range from 192.168.0.1 to 192.168.0.29 Explanation Because all addresses that need to be excluded are in a contiguous ranges, you complete this task by creating an exclusion range. In this lab, create the exclusion on the Subnet1 subnet. Use 192.168.0.1 as the beginning address and 192.168.0.29 as the ending address of the exclusion.

Complete this lab as follows:

1. From Hyper-V Manager, select CORPSERVER. 2. Expand the window to view all virtual machines. 3. Right-click the CorpDCHP server and select Connect. 4. From Server Manager, select Tools > DHCP. 5. In the left pane, expand the CorpDHCP.CorpNet.com. 6. Expand the IPv4 protocol. 7. Expand the Scope folder. 8. Right-click the node and select New Exclusion Range. 9. In the Start IP address field, enter the starting IP address. 10. In the End IP address field, enter the ending IP address. 11. Click Add. 12. Click Close to close the Add Exclusion Range dialog. Lab Report: 5.3.6 Create DHCP Client Reservations

Your Performance

Your Score: 0 of 5 (0%) Pass Status: Not Passed Elapsed Time: 8 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Create a reservation for LaserJet4240-1Hide Details

Name the reservation LaserJet4240-1 Assign the IP address of 192.168.0.101 Use aa6182df0454 as the MAC address Make the DHCP

In Create a reservation for LaserJet4240-2Hide Details

Name the reservation LaserJet4240-2 Assign the IP address of 192.168.0.102 Use cefd48900623 as the MAC address Make the type DHCP

In Create a reservation for KonicaColorHide Details

Name the reservation KonicaColor Assign the IP address of 192.168.0.103 Use c8ba99cd8012 as the MAC address Make the type DHCP

In Create a reservation for AcctPrinterHide Details

Name the reservation AcctPrinter Assign the IP address of 192.168.0.104 Make the type DHCP Use f1a93ef77d3b as the MAC address

In Create a reservation for SalesPrinterHide Details

Name the reservation SalesPrinter Assign the IP address of 192.168.0.105 Use dfa999cd8061 as the MAC address Make the type DHCP

Explanation To make sure each machine always receives the same IP address from the DHCP server, you need to create a client reservation for each machine's network adapter. Create the reservations so that they meet the following specifications:

Reservation Name IP Address MAC Address

LaserJet4240-1 192.168.0.101 aa-61-82--04-54 LaserJet4240-2 192.168.0.102 ce-fd-48-90-06-23

KonicaColor 192.168.0.103 c8-ba-99--80-12

AcctPrinter 192.168.0.104 f1-a9-3e-f7-7d-3b

SalesPrinter 192.168.0.105 df-a9-99-cd-80-61

By default, the reservations are enabled for both DHCP and BootP. You must change the default setting to enable DHCP only.

Complete this lab as follows:

1. From Hyper-V Manager, select CORPSERVER. 2. Expand the window to view all virtual machines. 3. Right-click the CorpDCHP server and select Connect. 4. From Server Manager, select Tools > DHCP. 5. In the left pane, expand the CorpDHCP.CorpNet.com. 6. Expand the IPv4 protocol. 7. Expand the Scope folder. 8. Right-click Reservations and select New Reservation. 9. In the Reservation name field, enter a reservation name (such as the computer name). 10. In the IP address field, enter the IP address. 11. In the MAC address field, enter the MAC address. For Ethernet, the MAC address will look like c8ba99cd8012 or c8-ba-99-cd-80-12. 12. Under Supported types, select DHCP only as needed. 13. Select Add to create the client reservation. 14. Repeat steps 9-13 for additional reservations. 15. Select Close. Lab Report: 5.3.8 Configure a DHCP Client

Your Performance

Your Score: 0 of 2 (0%) Pass Status: Not Passed Elapsed Time: 8 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Configure the wireless network connection to use DHCPHide Details

Use DHCP for addressing information Use DHCP for DNS server information

In Configure an alternate IP configurationHide Details

Configure an alternate configuration Use 192.168.2.13 for the IP address Use 255.255.255.0 for the subnet mask Use 192.168.2.254 for the default gateway Use 192.168.2.254 for the preferred DNS server

Explanation In this lab, your task is to complete the following:

Record the laptop's static IP and DNS configuration settings. Configure the laptop to obtain IP and DNS addresses automatically. Create an alternate TCP/IP connection with the static settings.

Complete this lab as follows:

1. From the notification area, right-click the Network icon and select Open Network and Sharing Center. 2. Select Change adapter settings. 3. Right-click Wi-Fi. 4. Select Properties. 5. Select Internet Protocol Version 4 (TCP/IPv4). 6. Select Properties. 7. Record the current static values for the IP address, subnet mask, default gateway, and DNS server address. 8. Select Obtain an IP address automatically to use DHCP. 9. Select Obtain DNS server address automatically. 10. Select the Alternate Configuration tab. 11. Select User configured. 12. Enter the IP address, subnet mask, default gateway, and DNS server address you recorded in step 4. 13. Select OK. 14. Click Close. Lab Report: 5.4.3 Configure a DHCP Relay Agent

Your Performance

Your Score: 0 of 5 (0%) Pass Status: Not Passed Elapsed Time: 9 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Add the DHCP Relay Agent protocol In Add NetTeam as a DHCP relay agent interface In Set the boot threshold to 0 In For the DHCP protocol, configure 192.168.0.14 as a DHCP server address In Refresh the IP address on Exec2 Explanation In this lab, your task is to complete the following:

Use Routing and Remote Access to configure CorpServer2 as a DHCP relay agent by performing the following: Add the DHCP relay agent . Add NetTeam as a DHCP relay agent interface. Set the boot threshold to 0. Configure the DHCP relay agent properties to identify 192.168.0.14 as the DHCP server. Renew the TCP/IP information on Exec2 (the client machine in Building B). Verify that Exec2 has a network connection.

Complete this lab as follows:

1. Add the DHCP relay agent routing protocol as follows: a. In Server Manager, select Tools > Routing and Remote Access. b. Expand IPv4. c. Right-click General and select New Routing Protocol. d. Select DHCP Relay Agent; then click OK. 2. Add and configure a relay agent interface as follows: a. In the left pane, right-click DHCP Relay Agent and select New Interface. b. Select NetTeam; then click OK. c. Make sure Relay DHCP packets is selected. d. Set the boot threshold. e. Click OK. 3. Configure the DHCP relay agent properties to identify the DHCP server as follows: a. Right-click DHCP Relay Agent and select Properties. b. In the Server address field, enter the IP address of the DHCP server. c. Select Add; then click OK. 4. Renew the TCP/IP address and verify the connection as follows: a. From the top menu, select Floor 1. b. Select Exec2. c. Right-click Start and select Command Prompt (Admin). d. In the command prompt, type /renew and press Enter. The computer should receive an address on the 192.168.10 network. e. From the the taskbar, select the Network icon to view the connection status. Lab Report: 5.4.4 Add a DHCP Server on Another Subnet

Your Performance

Your Score: 0 of 5 (0%) Pass Status: Not Passed Elapsed Time: 7 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Name the scope MySubnet In Set the address rangeHide Details

Use 192.168.10.21 as the first address in the range for MySubnet Use 192.168.10.199 as the last address in the range for MySubnet

In Assign a default gateway address of 192.168.10.5 on the MySubnet scope In Assign DNS server addressesHide Details

Use 198.28.56.108 for one of the DNS server addresses in the MySubnet scope Use 163.128.78.93 for the other DNS server address in the MySubnet scope

In Activate the MySubnet scope Explanation In order for a DHCP server to begin assigning IP addresses from a range of addresses on the 192.168.10.0 subnet to client workstations, you must create a DHCP scope.

Complete this lab as follows:

1. From Hyper-V Manager, click CORPSERVER. Expand the window to view all virtual machines. 2. Right-click the CorpDCHP server and select Connect (maximize the window for easier viewing if desired). 3. From Server Manager, select Tools > DHCP. 4. Expand the CorpDHCP server node. 5. Right-click IPv4; then select New Scope. 6. Click Next. 7. In the Name field, enter MySubnet; then select Next. 8. In the Start IP address field, enter 192.168.10.21. 9. In the End IP address field, enter 192.168.10.199. 10. Click Next > Next > Next > Next. 11. For the Router address, enter 192.168.10.5; then click Add > Next. 12. For the first DNS Server, enter 198.28.56.108; then click Add. 13. For the second DNS Server, enter 163.128.78.93; then click Add. 14. Click Next > Next. 15. Leave the Yes, I want to activate this scope now option selected; then click Next. 16. Click Finish to complete the of creating the DHCP scope. Lab Report: 5.5.4 Configure DNS Addresses

Performance Your Score: 0 of 6 (0%) Elapsed Time: 5 seconds

Task Summary Actions you were required to perform: In Use static DNS server addresses In Add 208.67.222.222 as a DNS server In Add 208.67.222.220 as a DNS server In Add 208.67.220.123 as a DNS server In Configure DNS server addresses in the required order In Use DHCP for IP address and default gateway information Explanation In this lab, your task is to complete the following:

Configure the IPv4 settings for the Local Area Connection network connection to use the following DNS server addresses: Preferred DNS server: 208.67.222.222 First alternate DNS server: 208.67.222.220 Second alternate DNS server: 208.67.220.123 Have Dorm-PC validate the static DNS server information.

Complete this lab as follows:

1. In the notification area, right-click the Network icon and select Open Network and Sharing Center. 2. Select Ethernet. 3. Select Properties. 4. Select Internet Protocol Version 4 (TCP/IPv4). 5. Select Properties. 6. Select Use the following DNS server addresses to manually configure the DNS server addresses. 7. Select Advanced to configure than two DNS server addresses. 8. Select the DNS tab. 9. Select Add to configure DNS server addresses. 10. Enter the DNS server address. 11. Select Add. 12. Repeat steps 9–11 to configure additional DNS server addresses. 13. Click OK. 14. Select Validate settings upon ; then select OK. 15. Click Close to close Ethernet Properties. 16. Click Close to close Ethernet Status. Lab Report: 5.5.5 Create Standard DNS Zones

Your Performance

Your Score: 0 of 4 (0%) Pass Status: Not Passed Elapsed Time: 8 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Create the acct.CorpNet.com primary forward lookup DNS zone on CorpDC.Hide Details

Zone name: acct.CorpNet Zone type: Primary Deselect Store the zone in Active Select Do not allow dynamic updates

In Allow zone transfers to any server In Create the acct.CorpNet.com secondary zone on CorpDC3Hide Details

Zone name: acct.CorpNet Zone type: Secondary

In Configure CorpDC (192.168.0.11) as the master server for the zone Explanation In this lab, your task is to complete the following:

Create a primary forward lookup zone on CorpDC using the following parameters: Deselect Store the zone in Active Directory. Use the zone name acct.CorpNet.com. Use the default name for the zone . Do not allow dynamic updates. Allow zone transfers to any server. Create a secondary forward lookup zone called acct.CorpNet.com on CorpDC3. Specify CorpDC (192.168.0.11) as the master DNS server for the zone.

Complete this lab as follows:

1. Create a primary forward lookup zone as follows: a. In Hyper-V Manager, select CORPSERVER. b. Maximize the window to view all virtual machines. c. Right-click CorpDC and select Connect (maximize the window for easier viewing if desired). d. In Server Manager, select Tools > DNS. e. Expand the DNS server that will host the zone. f. Right-click Forward Lookup Zones and select New Zone. g. In the New Zone wizard, select Next. h. Make sure Primary zone is selected. i. Unmark Store the zone in Active Directory (this option is only available for domain controllers); then select Next. j. In the Zone name field, enter the name for the zone; then select Next. k. Verify that Create a new file with this file name is selected; then and select Next. l. Specify the updates that will be accepted for the DNS zone; then select Next. m. Select Finish to complete the New Zone wizard. 2. Configure zone transfer as follows: a. Under Forward Lookup Zones, right-click the new zone and select Properties. b. Select the Zone Transfers tab. c. Verify that Allow zone transfers is selected. d. Select To any server. e. Select OK. 3. Create a Forward Secondary Zone as follows: a. From DNS Manager, expand the server that will host the new zone. b. Right-click Forward Lookup Zones and select New Zone. c. Select Next. d. On the Zone Type dialog, select Secondary zone as the zone type; then select Next. e. Enter the primary zone name; then select Next. f. In the Master Servers box, select Click here below IP Address. g. Enter the IP address or the name of a server that hosts a of the zone. h. Press Enter or click away from the IP address to begin validation. i. After it is validated, select Next. j. Click Finish to complete the New Zone wizard. Lab Report: 5.5.6 Create Host Records

Your Performance

Your Score: 0 of 6 (0%) Pass Status: Not Passed Elapsed Time: 15 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Create a reverse lookup zone for the 192.168.0 Subnet In Create A and PTR records for CorpServer.CorpNet.comHide Details

Create the CorpServer A record using 192.168.0.10 PTR record created for CorpServer

In Create A and PTR records for CorpFiles16.CorpNet.comHide Details

Create the CorpFiles16 A record using 192.168.0.12 PTR record created for CorpFiles16

In Create A and PTR records for CorpFiles12.CorpNet.comHide Details

Create the CorpFiles12 A record using 192.168.0.13 PTR record created for CorpFiles12

In Create A and PTR records for CorpDHCP.CorpNet.comHide Details

Create the CorpDHCP A record using 192.168.0.14 PTR record created for CorpDHCP

In Create A and PTR records for CorpWeb.CorpNet.comHide Details

Create the CorpWeb A record using 192.168.0.15 PTR record created for CorpWeb

Explanation In this lab, you perform the following tasks:

Create an IPv4 Active Directory-integrated primary reverse lookup zone for subnet 192.168.0.0/24. Be sure to accept the default replication and dynamic updates settings. Manually create A records and PTR records for the following hosts: Host Name IP Address CorpServer 192.168.0.10 CorpFiles16 192.168.0.12 CorpFiles12 192.168.0.13 CorpDHCP 192.168.0.14 CorpWeb 192.168.0.15

Complete this lab as follows: 1. Create a primary reverse lookup zone as follows: a. In Hyper-V Manager, select CORPSERVER. b. Right-click CorpDC and select Connect. c. In Server Manager, select Tools > DNS. d. Expand CORPDC. e. Right-click Reverse Lookup Zones and select New Zone. f. Click Next. g. Make sure Primary zone is selected. h. Make sure Store the zone in Active Directory is selected; then click Next. i. Keep the default replication scope setting and click Next. j. Keep the default reverse lookup zone settings and click Next. k. Type 192.168.0 as the network ID.

Omit any trailing zeroes that are excluded based on the subnet mask. For example, type 192.168.1 for subnet 192.168.1.0/24. Type 10.1 for subnet 10.1.0.0/16.

l. Click Next. m. Keep the default dynamic update settings; then click Next. n. Click Finish. 2. Create a host (A) and associated pointer (PTR) record as follows: a. In DNS Manager, expand Forward Lookup Zones. b. Right-click CorpNet.com and select New Host (A or AAAA). c. In the Name field, enter the host name. d. In the IP address field, enter the IP address. e. Select Create associated pointer (PTR) record as needed. The reverse lookup zone must exist for this record to be created. f. Click Add Host. g. Click OK. h. Repeat steps 2c through 2g to add additional host records. i. Click Done. Lab Report: 5.5.7 Create CNAME Records

Your Performance

Your Score: 0 of 3 (0%) Pass Status: Not Passed Elapsed Time: 10 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Create an (CNAME) record with a blank name pointing to CorpWeb.CorpNet.comHide Details

Make sure the record type is Alias (CNAME) Leave the name blank Use CorpWeb.CorpNet.com as the target host

In Create the intranet Alias (CNAME) record pointed to CorpWeb.CorpNet.comHide Details

Make sure the record type is Alias (CNAME) Use intranet as the record name Use CorpWeb.CorpNet.com as the target host

In Create the www Alias (CNAME) record pointed to CorpWeb.CorpNet.comHide Details

Make sure the record type is Alias (CNAME) Use www as the record name Use CorpWeb.CorpNet.com as the target host

Explanation In this lab, you create CNAME (ALIAS) records in the sales.private domain using the following values:

ALIAS Name Target Host (FQDN)

(leave blank) CorpWeb.CorpNet.com

intranet CorpWeb.CorpNet.com

www CorpWeb.CorpNet.com

Complete this lab as follows:

1. In Hyper-V Manager, select CORPSERVER. 2. Right-click CorpDC and select Connect. 3. In Server Manager, select Tools > DNS. 4. Expand CORPDC. 5. Expand the Forward Lookup Zones. 6. Right-click the sales.private zone and select New Alias (CNAME). 7. In the Alias name field, enter the alias name (to use the parent domain name for the alias, leave the field blank). 8. Enter the fully qualified domain name of the host. 9. Click OK. 10. Repeat steps 6-9 to create additional records. Lab Report: 5.5.8 Troubleshoot DNS Records

Performance Your Score: 0 of 1 (0%) Elapsed Time: 9 seconds

Task Summary Actions you were required to perform: In Create an A record for CorpWeb using 192.168.0.15 Explanation In this lab, your task is to complete the following:

Ping the CorpWeb server using its full name of CorpWeb.CorpNet.com. Ping the CorpWeb server using its IP address 192.168.0.15. Create any DNS records needed to fix the problem. Host name: CorpWeb IP address: 192.168.0.15 Use the ping command to verify that the problem is fixed.

This problem is caused because the CorpWeb server does not have a host (A) record in DNS. Because you can ping the server using its IP address, you know that the server is running and responsive. On the CorpNet zone, you should have created the host record for CorpWeb using 192.168.0.15 as the address.

Complete this lab as follows:

1. Right-click Start and select select Command Prompt (Admin). 2. At the command prompt, enter ping CorpWeb.CorpNet.com and press Enter. Notice that the ping is unable to CorpWeb. 3. Type ping 192.168.0.15 and press Enter. This time the ping succeeds using the IP address, indicating that there is a problem with the CorpWeb DNS record. 4. In Hyper-V Manager, select CORPSERVER. Resize the window to view all virtual machines. 5. Right-click CorpDC and select Connect (maximize the window for easier viewing if desired). 6. In Server Manager, select Tools > DNS. 7. Expand CORPDC. 8. Expand Forward Lookup Zones. 9. Right-click CorpNet.com and select New Host (A or AAAA). 10. In the Name field, enter CorpWeb. 11. In the IP Address field, enter the 192.168.0.15. 12. Select Create associated pointer (PTR) record to automatically create the PTR record for the new host. 13. Select Add Host. 14. Select OK. 15. Select Done to close the New Host dialog. 16. From the Command Prompt window on CorpServer, enter ping CorpWeb.CorpNet.com and press Enter. Now the ping succeeds. Lab Report: 5.6.9 Configure an IPv6 Address

Your Performance

Your Score: 0 of 2 (0%) Pass Status: Not Passed Elapsed Time: 9 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Use 2620:14F0:45EA:0001:192:168:0:10 as the IPv6 address on the vEthernet (External) network adapter In Use 64 as the subnet prefix length for the IPv6 address Explanation Complete this lab as follows:

1. Right-click the Network icon in the notification area and select Open Network and Sharing Center. 2. On the left, select Change adapter settings. 3. Right-click the vEthernet (External) adapter and select Properties. 4. Select Internet Protocol Version 6 (TCP/IPv6). 5. Select Properties. 6. Select Use the following IPv6 address. 7. In the IPv6 address field, enter 2620:14F0:45EA:0001:192:168:0:10 as the IPv6 address. 8. In the Subnet prefix length field, enter 64. 9. Click OK. 10. Click Close. 11. Right-click Start and select Command Prompt (Admin) to verify the address configuration. 12. Enter ipconfig /all and view the IPv6 Address. Lab Report: 5.8.5 Explore IP Configuration

Performance Your Score: 0 of 5 (0%) Elapsed Time: 9 seconds

Task Summary Actions you were required to perform: In Fix the subnet mask on Exec In Fix the gateway on Exec In Enable the scope on the DHCP Server In Fix the 003 Router option on the DHCP Server In Configure Exec for DHCP Explanation Complete this lab as follows:

1. On CorpServer in the Networking Closet computer, mouse over the Network icon in the notification area. On CorpServer, the Network icon in the notification area appears normal, indicates a connection to the local network and to internet. When you mouse over the Network icon, you see the details of this status. 2. In the notification area, right-click the Network icon and select Open the Network and Sharing Center. The Network and Sharing Center diagram confirms that CorpServer is connected to the local network and the internet. 3. Ping CorpServer (local workstation) and the ISP to verify connectivity to the internet as follows: a. Right-click Start and select Command Prompt (Admin) to open a command window. The ping to CorpServer (local workstation) and the ISP succeed, verifying a valid connection to the internet. b. At the command prompt, enter ipconfig /all to check the Ethernet configuration. Using ipconfig /all provides the following information about the vEthernet (External) on CorpServer: DHCP Enabled: No. This tells us that the server is configured with a static IP address and is not enabled for DHCP IPv4 Address: 192.168.0.10 Subnet Mask: 255.255.255.0. The server is using the default subnet mask for the Class C IP address range. Default Gateway: 192.168.0.5. The router's internal interface is configured as the default gateway. c. At the command prompt, enter tracert to see the to the ISP. Using tracert 65.86.1.1 verifies a path to the ISP through our default gateway. 4. In the Executive Office, check the status of the and network activity lights as follows: a. From the navigation tabs at the top, select Floor 1 Overview. b. Under Executive Office, select Hardware. c. Above the workstation, select Back to switch to the back view of the workstation. The link and network activity lights on the back of the workstation are on and blinking, indicating that there is a physical connection to the switch and there is activity on the connection. This points to a TCP/IP configuration problem. 5. Verify the connectivity on the Exec workstation as follows: a. On the Exec monitor, select Click to view Windows 10. b. In the notification area, mouse over the Network icon. c. Right-click the Network icon and select Open the Network and Sharing Center. On the Exec workstation, the network icon in the notification area has a yellow warning sign with an exclamation point, which indicates a connection to the local network, but no access to the internet. When you select the Network icon, you see the details of this status. The Network and Sharing Center diagram confirms that Exec is connected to the local network, but has no internet access. 6. On Exec, you are able to ping the local interface on Exec by name (since you don't know the IP address yet), but you can't ping CorpServer or the ISP. This indicates that Exec has a valid connection, but can't communicate with CorpServer or the ISP. 7. Using ipconfig /all provides the following information about the Ethernet connection on Exec: DHCP Enabled: No IPv4 Address: 192.168.0.62 Subnet Mask: 255.255.255.240 Default Gateway: 192.168.0.4 This information provides us with at least two clues to the problem: 1. The network is using DHCP, but this workstation is not enabled for DHCP. 2. Given the workstation's current subnet mask, the IPv4 Address of the workstation and the default gateway are not on the same network. In addition, the subnet mask is not the default subnet mask for the Class C IP address range being used. With 255.255.255.240 as a subnet mask, the network would only include addresses from 192.168.0.48 to 192.168.0.63. The IP address for CorpServer (192.168.0.10) and the ISP fall outside of this range. The information in step 3 confirms that the default subnet mask for the Class C IP address range (255.255.255.0) is being used. 8. After correcting the subnet mask on Exec, there are still no changes to the network icon or the diagram in the Network and Sharing Center. 9. After correcting the subnet mask on Exec, you can now ping CorpServer, but you still can't ping the ISP. This indicates that you only have local connectivity. 10. Use tracert 65.86.1.1. The command times out, indicating the following: The ICMP packets are not returning from the first (gateway) in its path to the ISP. Exec is not finding the gateway. The gateway address on Exec is not configured correctly. (The gateway address (router) on the network diagram is 192.168.0.5.) 11. After configuring the correct gateway address on Exec, the network icon and the diagram in the Network and Sharing Center confirm that Exec is connected to the internet. 12. Using the tracert command again returns a path to the ISP through the gateway. Since we have a valid connection to the internet, we will leave the static address for now while we troubleshoot in Office 1. 13. In Office 1, the link and network activity lights on the back of the workstation are on and blinking. Once again, this points to a TCP/IP configuration problem. 14. On Office1, the network icon and the diagram in the Network and Sharing Center indicate that Office1 is connected to the unidentified network and has no internet access. 15. You are able to ping the local interface, but you can't ping CorpServer or the ISP. This indicates that Office1 has a valid connection to the local network. 16. Using ipconfig /all provides the following information about the Ethernet connection: DHCP Enabled: Yes. This tells us that the workstation is configured to use a DHCP server. IPv4 Address: This address is in the APIPA range (169.254.0.1 to 169.254.255.254). This means that the workstation assigned itself an IP address instead of receiving one from the DHCP server. The workstation will only be able to communicate with other hosts on the local network that have also configured their own IP address through APIPA. Subnet Mask: 255.255.0.0. This is the default subnet mask for the APIPA address. Default Gateway: The address is blank. This means that communication is limited only to other workstations on the local network. DHCP Server line is not shown. This means that the workstation was unable to contact the DHCP server. DNS Servers line is not shown for IPv4. Since DHCP is enabled, the rest of the information should have come from the DHCP server. We can conclude that there is an issue with the DHCP server. 17. On CorpDHCP, launch the DHCP console and activate the scope. 18. On Office1, the ipconfig /renew command will request new IP address information from the DHCP server, and it will reconfigure the settings for the Ethernet connection. 19. The ipconfig /all command will check the Ethernet configuration. You should notice the line for the default gateway, DNS server, and DHCP server, along with the new IP address, which is now within the DHCP scope for the local network. 20. After activating the DHCP server and receiving a valid IP Address, you can now ping CorpServer from Office1, but you still can't ping the ISP. 21. The tracert command times out on Office1, indicating that it can't get to the gateway. As noted above, the gateway should be 192.168.0.5. 22. The ipconfig /all command shows the default gateway is set to 192.168.0.2, but we know it should be 192.168.0.5. Since this address is coming from DHCP, we need to check the DHCP server. 23. On CorpDHCP, launch the DHCP console and reconfigure the settings for the DHCP scope. 24. On Office1, the ipconfig /renew command will request new IP address information from the DHCP server, and it will reconfigure the settings for the Ethernet connection. 25. Use the ipconfig /all command to check the Ethernet configuration. You should notice that the line for the default gateway is now configured correctly. 26. The network icon and the diagram in the Network and Sharing Center indicate that Office1 is connected to the local network and the internet. 27. When you ping the ISP to confirm resolution, the ping succeeds. 28. On Exec, reconfigure the Ethernet connection to use DHCP. 29. The ipconfig /all command now shows the IP address, default gateway, DNS server, and DHCP server that were provided by the DHCP server. 30. The network icon and the diagram in the Network and Sharing Center indicate that Exec is connected to the corporate network with full internet access. 31. Use tracert 65.86.1.1, which returns a path to the ISP through the gateway. The network is now fully functional, and your troubleshooting is complete. Lab Report: 5.8.6 Troubleshoot IP Configuration 1

Your Performance

Your Score: 0 of 3 (0%) Pass Status: Not Passed Elapsed Time: 7 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Reconfigure the DHCP server with 192.168.0.5 as the default gateway In Verify that the Support workstation can communicate with the Internet In Verify that the Office2 workstation can communicate with the Internet Explanation In this lab, your task is to complete the following:

Use the following troubleshooting tools to diagnose the problem in the network: The ping, ipconfig, or tracert command utility The Network and Sharing Center in the Windows 10 or Windows Server 2016 The DHCP server console in the Windows Server 2016 operating system Fix the problem at the workstation, the DHCP server, or both as necessary. Use the troubleshooting tools to confirm the resolution of the problem.

Complete this lab as follows:

1. In the Support Office, begin troubleshooting the problem by verifying the scope of the connectivity problem. From the workstation, ping the computer in the Networking Closet and ping the internet service provider (ISP) (pinging the computer in the Networking Closet succeeds, but the ping to the ISP fails). 2. In Office 2, verify the connectivity problem between the workstation and all other workstations in the network (the ping to all other workstations in the network succeeds, but the ping to the ISP fails). Both steps 1 and 2 confirm that there is not a physical connectivity problem in the local network. The problem is likely related to the IP configuration for the network. 3. In the Support Office, open the command prompt and enter ipconfig /all to check the Local Area Connection configuration. You should notice the following problems: a. The default gateway address is incorrectly configured with 192.168.0.4. This is why the workstation in this scenario can only communicate with hosts on the local network, but not on the internet. b. The DHCP Enabled line is Yes, meaning that the workstation is configured to use a DHCP server. c. The DHCP server address listed is 192.168.0.10. This is the correct DHCP server address. The workstation received addressing and default gateway information from the correct DHCP server. Therefore, the DHCP server has been configured to give out the wrong default gateway address. 4. In the Networking Closet computer on CorpServer, open the CorpDHCP guest server and launch the DHCP console to reconfigure the settings for the DHCP scope as follows: a. In Hyper-V Manager, select CORPSERVER. Expand the window to view all virtual machines. b. Right-click CorpDHCP and select Connect. c. In Server Manager, select Tools > DHCP to start the DHCP console. d. Expand CorpDHCP. e. Expand IPv4. f. Expand Scope [192.168.0.1] Subnet1. g. Select Scope Options. h. Right-click 003 Router. i. Select Properties. j. In the default gateway address field, enter 192.168.0.5 and remove 192.168.0.4. k. Click OK to apply the change. 5. In the Support Office, open the command prompt and enter ipconfig /renew. This will request the new IP address information from the DHCP server and reconfigure the settings for the Ethernet connection. 6. Enter ipconfig /all to check the Ethernet configuration. You should notice the line for the default gateway is now correctly configured as 192.168.0.5. 7. Confirm the resolution of the problem by pinging the ISP. The ping to the ISP succeeds. 8. In Office 2, repeat steps 5-7 to fix the problem for the second workstation. Lab Report: 5.8.7 Troubleshoot IP Configuration 2

Your Performance

Your Score: 0 of 2 (0%) Pass Status: Not Passed Elapsed Time: 6 seconds Required Score: 100%

Task Summary Actions you were required to perform: In In the Networking Closet, activate the DHCP scope for the local network In Verify that the Executive Office and IT Administrator workstations can communicate with the internet Explanation In this lab, your task is to complete the following:

Use the following troubleshooting tools to diagnose the problem in the network: The ping, ipconfig, or tracert command utility The Network and Sharing Center in the Windows 10 or Windows Server 2016 operating system The DHCP server console in the Windows Server 2016 operating system Fix the problem at the workstation, the DHCP server, or both as necessary. Use the troubleshooting tools to confirm the resolution of the problem.

Complete this lab as follows:

1. In the Executive Office, begin troubleshooting the problem by verifying the scope of the connectivity problem. From the workstation, ping the computer in the Networking Closet. The ping to the location fails. 2. Ping the Internet Service Provider (ISP). The ping to the location fails. 3. In the IT Administrator office, verify the connectivity problem between the workstation the Networking Closet computer and the ISP. (The pings to both locations fails). The problem is most likely related to the IP configuration for the network. 4. In the Executive Office, open the command prompt and use the ipconfig /all command to check the Local Area Connection configuration. You should notice the following problems: The default gateway and DNS server addresses have not been configured on the workstation. This means that communication is limited to other computers on the local network. The DHCP Enabled line is Yes, meaning that the workstation is configured to use a DHCP server. The DHCP Server address line is not shown. This means that the workstation was unable to contact the DHCP server. The IP address is in the APIPA range (169.254.0.1 to 169.254.255.254). This means that the workstation assigned itself an IP address. The workstation will be able to communicate with other hosts on the local network that have also configured their own IP address through APIPA. 5. In the Networking Closet, confirm that the DHCP service is enabled and activated for the local network. a. In Hyper-V Manager, select CORPSERVER. Expand the window to view all virtual machines. b. Right-click CorpDHCP and select Connect (maximize the window for easier viewing if desired). c. In Server Manager, select Tools > DHCP to start the DHCP console. d. Expand CorpDHCP.CorpNet.com. e. Expand IPv4. The down arrow for Scope [192.168.0.1] Subnet1 indicates that the scope is not active. f. Right-click Scope [192.168.0.1] Subnet1 and select Activate. The down arrow for the scope is gone, and the DHCP service for the local network is now active. 6. In the Executive Office, open the command prompt and enter ipconfig /renew. This will request the new IP address information from the DHCP server, and it will reconfigure the settings for the Ethernet connection. 7. Enter ipconfig /all to check the Ethernet configuration. You should notice the lines for the default gateway, DNS server, and DHCP server are now configured, along with a new IP address within the DHCP scope for the local network. 8. In the Executive Office, confirm the resolution of the problem by pinging the ISP. The ping to the ISP succeeds. 9. In the IT Administrator Office, repeat step 6 to fix the problem for that workstation.

Lab Report: 5.8.8 Troubleshoot IP Configuration 3

Performance Your Score: 0 of 1 (0%) Elapsed Time: 7 seconds

Task Summary Actions you were required to perform: In On the Office1 computer, configure the network connection to request the IP address information from the DHCP server

Explanation In this lab, your task is to complete the following:

Use the following troubleshooting tools to diagnose the problem in the network: The ping, ipconfig, or tracert command utility The Network and Sharing Center in the Windows 10 or Windows Server 2016 operating system The DHCP server console in the Windows Server 2016 operating system Fix the problem at the workstation, the DHCP server, or both as necessary. Use the troubleshooting tools to confirm that the problem is resolved.

Complete this lab as follows:

1. In Office 1, begin troubleshooting the problem by verifying the scope of the connectivity problem. a. From the workstation, ping CorpServer in the Networking Closet. b. Ping the Internet Service Provider (ISP) (Notice that the ping fails for both CorpServer and the ISP). 2. In the IT Administration office, verify the connectivity problem between the workstation and all other workstations in the network (the ping to all other workstations in the network and the ISP succeeds). Both steps 1 and 2 confirm that there is not a physical connectivity problem in the local network and that the scope of the problem is most likely related to the IP configuration for the Office 1 workstation. 3. On Office 1, open the command prompt and enter the ipconfig /all command to check the Ethernet configuration. You should notice the following problems: The subnet mask is incorrectly configured with 255.255.255.240. The workstation can only communicate with other hosts whose IP addresses have the same network address as determined by the local subnet mask. ITAdmin is 192.168.0.20, and Office 1 is 192.168.0.30. With 255.255.255.240 as a subnet mask, the network would only include addresses from 192.168.0.16 to 192.168.0.31. The IP address for CorpServer (192.168.0.10) and the router fall outside of this range. The DHCP Enabled line shows No. This means that the workstation has been configured with a static IP address. The DNS Servers line shows 163.128.78.108, which is not the address of either of the External DNS Servers. 4. On Office 1, configure the network connection to request the IP address information from the DHCP server: a. Right-click the Network icon and select Open Network and Sharing Center. b. Select Ethernet. c. Select Properties. d. Select Internet Protocol Version 4 (TCP/IPv4). e. Select Properties. f. Select Obtain an IP address automatically. g. Select Obtain DNS server address automatically. h. Select OK. i. Select Close. j. Select Close. 5. On Office 1, open the command prompt and enter ipconfig /all to check the Ethernet configuration. You should notice the line for DHCP Enabled shows Yes, a new IP address, the correct subnet mask, and the correct DNS Server. 6. Confirm the resolution of the problem by pinging the ISP. The ping to the ISP succeeds.

Lab Report: 5.9.8 Explore Network Communications

Your Performance

Your Score: 0 of 1 (0%) Pass Status: Not Passed Elapsed Time: 8 seconds Required Score: 100%

Task Summary Actions you were required to perform: In Use tracert on Exec Explanation In this lab, your task is to complete the following:

1. Right-click Start > Command Prompt (Admin) to open the command prompt. 2. At the command prompt, enter ping 192.168.0.30 and press Enter to ping Office1. 3. You can successfully ping the IP address of Office1 from ITAdmin. 4. Enter ping 199.92.0.33 and press Enter to ping Support. 5. You cannot ping Support from ITAdmin. Notice that the IP address for Support is on a different network (network 199.92.0.0 instead of network 192.168.0.0). Devices on the same local network must have IP addresses in the same network range. If you want to communicate with Support, you will need to change the IP address assigned to Support. 6. Enter ping 192.168.0.5 and press Enter to ping the router's internal interface. 7. You can successfully ping the router's internal interface from ITAdmin. Because ITAdmin and the router's address (192.168.0.5) are on the same network, the ping tests succeed. 8. Enter ping 163.128.78.93 and press Enter to ping the external DNS Server. 9. ITAdmin and the ISP are on a different network (network 192.168.0.0 and 163.128.78.0 respectively). Because ITAdmin does not have a default gateway set, it cannot communicate with devices on other networks. 10. Trace the path between Exec and the internet router's interface as follows: a. From the top navigation tabs, select Floor 1 Overview. b. Under Executive Office, select Exec. c. Right-click Start > Command Prompt (Admin) to open the command prompt. d. At the command prompt, enter tracert 198.28.56.1 and press Enter. 11. When you communicate with devices on other networks, the packets go first to the default gateway (the router between the two networks). The packets are sent to the router interface on the same network as the sending host and then to the next hop in the path as necessary. In this case, there are two IP addresses listed in the tracert output, but only one router (hop) between Exec and the internet router. The last address in the tracert output is the internet router. 12. Enter tracert 163.128.78.93 and press Enter to trace the path to one of the ISP's DNS servers. 13. When you trace the path between Exec and the ISP's DNS server, the path has additional hops. The first lines in the tracert output are the routers (hops) between Exec and the DNS server. The last address in the tracert output is the DNS server. Lab Report: 5.10.4 Explore

Performance Your Score: 0 of 1 (0%) Elapsed Time: 13 seconds

Task Summary Actions you were required to perform: In Explore DNS with nslookup Explanation In this lab, your task is to complete the following:

Use nslookup to query DNS for the CorpWeb server using its full name (CorpWeb.CorpNet.com). What happens? Use nslookup to query the CorpDC3 DNS server for CorpWeb. What happens? What is the problem? How would you resolve this problem? How would you verify that the problem has been fixed?

This problem is caused because the CorpWeb server has a host (A) record in DNS on CorpDC but does not have a host (A) record in DNS on CorpDC3.

Complete this lab as follows:

1. Right-click Start and select Command Prompt (Admin). 2. At the command prompt, enter nslookup CorpWeb.CorpNet.com and press Enter. The CorpDC DNS server responds with name resolution information for CorpWeb. 3. Enter nslookup CorpWeb.CorpNet.com CorpDC3.CorpNet.com and Press Enter. The CorpDC3 DNS server responds that it can't find CorpWeb. CorpDC3 does not have a DNS record for CorpWeb.

The information between the DNS databases is not consistent. Since this DNS zone is an Active Directory- integrated zone, this indicates that Active Directory is not synchronizing properly. You would likely attempt to force replication between the Active Directory Domain Controllers. If CorpDC held a primary zone and CorpDC3 held a secondary zone, you would likely initiate a zone transfer to make sure the DNS records were consistent between servers.

To verify that the problem has been fixed, you can repeat step 3. The CorpDC3 DNS server should responds with name resolution information for CorpWeb.