Tingnan ang lahat ng mga set ng pag-aaral

Chapter 4 labs

Pataasin ang iyong marka sa homework at exams ngayon gamit ang Quizwiz!

4.3.6 Configure DHCP Options

Complete this lab as follows: Access the CorpDCHP virtual server.From Hyper-V Manager, select CORPSERVER.Maximize the Hyper-V Manager window to view the available server.Right-click CorpDCHP and select Connect. Configure the DHCP server options.From Server Manager, select Tools > DHCP.Maximize the DHCP window for better viewing.Expand CorpDHCP.CorpNet.local > IPv4.Right-click Server Options and select Configure Options.Under Available Options, select the 006 DNS Servers.Under IP Address, enter 192.168.0.11.Select Add to add the IP address to the list.Under IP Address, enter the second 192.168.10.11 and then select Add.Scroll down and select 015 DNS Domain Name.In the String value field, enter CorpNet.local.Select OK to save the options you have defined. Configure DHCP scope options.Expand Scope [192.168.0.1] Subnet1.Right-click Scope Options and select Configure Options.Under Available Options, select the 003 Router.Under IP address, enter 192.168.0.5.Select Add to add the IP address to the list.Select OK to save the options you have defined.

4.9.5 Explore IP Configuration

Complete this lab as follows: From CorpServer (located in the Networking Closet), mouse over the Network icon in the Notification Area.Note that the Notification Area appears normal (a computer icon is shown), which indicates a connection to the local network and the internet. When you mouse over the Network icon, you see the details of this status. Access the Network Connections window.Right-click Start and then select Settings.Select Network & Internet.The Settings Status diagram confirms that CorpServer is connected to the local network and to the internet. Ping the ISP to verify connectivity through the router and the internet.From the top right, select Exhibits.Locate the IP address of the ISP.From the top right, select Answer Questions.Answer Question 1.Close the Exhibits window.Right-click Start and select Windows PowerShell (Admin).From the PowerShell prompt, type ping ISP_IPaddress and press Enter.Notice that the ping was successful, verifying a valid connection to the internet. Use the IPConfig and tracert commands to find the devices used to access the ISP.From the PowerShell prompt, type ipconfig /all and press Enter.Locate and examine the vEthernet (External) configuration settings and note the following: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.10Subnet 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.From the PowerShell prompt, type tracert ISP_IPaddress to see the path to the ISP.Answer Question 2.From the top right, select Exhibits.Answer Question 3.Minimize the Lab Questions window.Close the Exhibits window. From the Executive Office, check the status of the link and network activity lights.From the top left, select Floor 1 Overview.Under Executive Office, select Hardware.Above the workstation, select Back to switch to the back view of the workstation.The link and network activity lights on the network card are on and blinking. This indicates that there is a physical connection to the switch and there is activity on the connection. This points to a TCP/IP configuration problem. Verify the connectivity on the Exec workstation.On the Exec monitor, select Click to view Windows 10.In the Notification Area, mouse over the Network icon.Notice that the pop-up indicates there is no internet access.Right-click Start and then select Settings.Select Network & Internet.The Settings Status diagram confirms that the Exec computer has no connection to the internet.Close the Settings app.Right-click Start and select Windows PowerShell (Admin).From the PowerShell prompt, type ping Exec and press Enter.Notice that the ping was successfulFrom the PowerShell prompt, type ping CorpServer and press Enter.Notice that the ping to CorpServer failed.From the PowerShell prompt, type ipconfig /all and then press Enter. From this command, the following is shown for the Ethernet interface card:DHCP Enabled: NoIPv4 Address: 192.168.0.62Subnet Mask: 255.255.255.240Default Gateway: 192.168.0.4 This information provides the following clues to the problem: The network is using DHCP, but this workstation is not enabled for DHCP. Given the workstation's current subnet mask, the IPv4 address of the workstation and the default gateway are not on the same network. 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. In Step 4, you learned that CorpServer (192.168.0.10) had a default subnet mask for the Class C IP address range (255.255.255.0), which doesn't match Exec. Fix the subnet mask for the Exec computer.Right-click Start and then select Settings.Select Network & Internet.From the left pane, select Ethernet.From the right pane, select Change adapter options.Right-click Ethernet and select Properties.Select Internet Protocol Version 4 (TCP/IPv4) and then select Properties.Change the Subnet mask to 255.255.255.0 and then select OK.From the PowerShell prompt, type ping CorpServer and then press Enter.Notice that the ping is now successful.From the PowerShell prompt, type ping 198.28.2.254 (the ISP) and then press Enter.Notice that the ping is still unsuccessful.From the PowerShell prompt, type tracert 198.28.2.254 (the ISP) and then press Enter.The command times out, indicating that the gateway address on Exec is not configured correctly. The gateway address (router) on the network diagram is 192.168.0.5. Fix the default gateway for the Exec computer.From the Ethernet Properties dialog, select Internet Protocol Version 4 (TCP/IPv4) and then select Properties.Change the Default gateway to 192.168.0.5Select OK and then select Close.Close the Network Connections window.From the Settings app, select Status.The Status pane now shows a connection to the internet.Close the Settings app.Notice that the network icon in the Notification Area is now showing a computer, indicating a connection to the internet.From the PowerShell prompt, type ping 198.28.2.254.The ping is now successful.From the PowerShell prompt, type tracert 198.28.2.254 and press Enter.The route taken to get to the ISP is now shown. Since there is now a valid connection to the internet, leave the static address for now and begin to troubleshoot the computer in Office 1. From Office 1, troubleshoot for network connectivity.From the top left, select Floor 1 Overview.Under Office 1, select Hardware.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. Once again, this points to a TCP/IP configuration problem.On the Office1 monitor, select Click to view Windows 10.In the Notification Area, mouse over the Network icon.Notice that the pop-up indicates there is no internet access.Right-click Start and select Windows PowerShell (Admin).From the PowerShell prompt, type ipconfig /all and then press Enter. Examine the information for the Ethernet network card and note the following: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. From this, you can conclude that there is an issue with the DHCP server. From CorpServer, access the CorpDHCP server.From the top left, select Floor 1 Overview.Under Networking Closet, select CorpServer.From the Hyper-V Manager, select CORPSERVER.Maximize the window for better viewing.Double-click CorpDHCP to connect to the CorpDHCP virtual server. From CorpDHCP, launch the DHCP console and activate the scope.From CorpDHCP's menu bar, select Tools > DHCP.Expand CorpDHCP.CorpNet.local > IPv4.Notice that the folder icon for Scope [192.168.0.1] Subnet1 has a down arrow, indicating that the DHCP scope is not active.Right-click Scope [192.168.0.1] Subnet1 and select Activate. From Office1, check to see if activating DHCP fixed the issue.From the top left, select Floor 1 Overview.Under Office 1, select Office1.From the PowerShell prompt, type ipconfig /renew and press Enter. This command requests new IP address information from the DHCP server.Notice that the networking icon in the Notification Area still indicates that Office1 has no connection to the internet.From the PowerShell prompt, type ipconfig /all and press Enter.Notice the line for the default gateway, DNS server, and DHCP server (along with the new IP address) is now within the DHCP scope for the local network.From the PowerShell prompt, type ping CorpServer and press EnterThe ping command is successful.From the PowerShell prompt, type ping 198.28.2.254 (the ISP) and then press Enter.Although you can ping CorpServer, you are still unable to ping the ISP.Review the output from the ipconfig command.Notice that the default gateway does not match the default gateway used by CorpServer or Exec. Since this IP information is coming from the DHCP server, you need to check the DHCP scope. On CorpServer, from CorpDHCP, reconfigure the settings for the DHCP scope.From the top left, select Floor 1 Overview.Under Networking Closet, select CorpServer.From the DHCP console, expand Scope [192.168.0.1] Subnet1.Right-click Scope Options and then select Configure Options.Highlight the 003 Router line.Under IP address, select 192.168.0.2 and then click Remove.In the IP address field, change the address to 192.168.0.5 and then click Add.Select OK. From Office1, check to see if fixing the DHCP scope resolved the issue.From the top left, select Floor 1 Overview.Under Office 1, select Office1.From the PowerShell prompt, type ipconfig /renew and then press Enter. This command requests new IP address information from the DHCP server.Notice that the networking icon in the Notification Area now indicates that Office1 has a connection to the internet.From the PowerShell prompt, type ipconfig /all and then press Enter.Notice the line for the default gateway is now set to 192.168.0.5.From the PowerShell prompt, type ping 198.28.2.254 (the ISP) and then press Enter.You can now ping the ISP. On Exec, reconfigure the Ethernet connection to use DHCP.From the top left, select Floor 1 Overview.Under Executive Office, select Exec.Right-click Start and then select Settings.Select Network & Internet.Select Ethernet and then select Change adapter options.Right-click Ethernet and then select Properties.From the Ethernet Properties dialog, select Internet Protocol Version 4 (TCP/IPv4) and then click Properties.Select Obtain an IP address automatically.Select Obtain DNS server address automatically.Select OK and then select Close.From the PowerShell prompt, type ipconfig /all and then press Enter.Notice that the Ethernet card is now using DHCP (DHCP Enable: Yes).From the PowerShell prompt, type tracert 198.28.2.254 and then press Enter.The command returns a path to the ISP through the gateway. The network is now fully functional, and your troubleshooting is complete. Score the lab.From the top right, select Answer Questions.Select Score Lab. Q1What is the IP address of the ISP? 198.28.2.254 Q2How many hops did it take to access the ISP 4 Q3What is the name of the device accessed on the third hop? pfSense

4.9.7 Troubleshoot IP Configuration 2

Complete this lab as follows: Troubleshoot From the Exec computer, begin troubleshooting by verifying the scope of the connectivity problem.Under Executive Office, select Exec.Right-click Start and then select Windows PowerShell (Admin).From the PowerShell prompt, run the following ping commands. Press Enter after each command:ping 192.168.0.10 (CorpServer)ping 198.28.2.254 (The Internet Service Provider, or ISP)Notice that both pings are unsuccessful.ping ITAdmin (the name of the computer in the IT Administration office).Notice that the ping to ITAdmin is successful. However, it is responding using an APIPA IP address. This indicates that this computer is not getting its IP address from the DHCP as it should. From CorpServer computer, continue troubleshooting the problem by trying to access the ISP.From the top left, select Floor 1 Overview.Under Networking Closet, select CorpServer.Right-click Start and then select Windows PowerShell (Admin).From the PowerShell prompt, type ping 198.28.2.254 (the ISP).Notice that the ping to the ISP is successful.From the PowerShell prompt, type tracert 198.28.2.254 and press Enter.From the top right, select Exhibits.From the top right, select Answer Questions.Answer Question 1.Close the Exhibits and Answer Questions windows. From the ITAdmin computer, continue troubleshooting the problem by trying some additional ping tests.From the top left, select Floor 1 Overview.Under IT Administration, select ITAdmin.Right-click Start and then select Windows PowerShell (Admin).From the PowerShell prompt, run the following ping commands. Press Enter after each command:ping 192.168.0.10 (CorpServer)ping 198.28.2.254 (the ISP)Notice that the ping to the ISP fails.ping exec (the name of the computer in the Executive Office)Notice that the ping to the ITAdmin is successful. However, the Exec computer is responding with an APIPA IP address.From the top right, select Answer Questions.Answer Question 2. From ITAdmin, use the ipconfig /all command to continue troubleshooting.From the PowerShell prompt, type ipconfig /all and press Enter.Answer Questions 3 and 4. From Exec, use the ipconfig /all command to continue troubleshooting.From the top left, select Floor 1 Overview.Under Executive Office, select Exec.From the PowerShell prompt, type ipconfig /all and press Enter.Answer Questions 5.Minimize the Lab Questions dialog. Fix the Issue Since it appears that the DHCP server is not functioning correctly, check the current state of the DHCP services. Access the CorpDHCP virtual server.From the top left, select Floor 1 Overview.Under Networking Closet, select CorpServer.From Hyper-V Manager, select CORPSERVER.Maximize the window to view all virtual machines.Double-click CorpDHCP to connect to the server. Confirm that the DHCP service is enabled and activated for the local network.From Server Manager, select Tools > DHCP to start the DHCP console.Maximize the window for better viewing.Expand CorpDHCP.CorpNet.local > IPv4.The down arrow for Scope [192.168.0.1] Subnet1 indicates that the scope is not active.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. Verify the fix by viewing the IP information for Exec and using the ping command.From the top left, select Floor 1 Overview.Under Executive Office, select Exec.From the PowerShell prompt, type ipconfig /all and press Enter to check the Ethernet configuration.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.From the PowerShell prompt, type ping 198.28.2.254 and press Enter.Notice that the ping to the ISP succeeds.From the PowerShell prompt, type tracert 198.28.2.254 and press Enter.(Optional) Repeat step 3 for the ITAdmin computer.From the top right, select Answer Questions.Select Score Lab. Q1After looking at the exhibits and the results of the tracert command, which of the following IP addresses is assigned to the building A network router? 192.168.0.5 Q2Which of the following best describes what you have learned from your troubleshooting up to this point? The connections from building A to the ISP are working. Q3Mark all of the observations you found to be true after examining the results of the ipconfig /all command. The IP information for the Ethernet adapter is supposed to come from a DHCP server., The IP address is an APIPA address, not a valid address for this network. Q4Which of the following is the most likely reason the ping tests to the ISP failed from Exec and ITAdmin, but were successful from CorpServer? The DHCP server is probably not assigning IP addresses correctly. Q5Why can the Exec and ITAdmin computers ping each other while they cannot ping CorpServer or ISP? Both are using an APIPA address.

4.5.7 Create CNAME Records

4.5.6 Create Host Records

Complete this lab as follows: Access the CorpDC virtual server.From Hyper-V Manager, select CORPSERVER.Double-click CorpDC to connect to the server.Maximize the window for better viewing. Create a primary reverse lookup zone.From Server Manager, select Tool > DNS.Expand CORPDC.Right-click Reverse Lookup Zones and select New Zone.Select Next.Make sure Primary Zone is selected.Make sure Store the zone in Active Directory is selected and then select Next.Keep the default replication scope setting and select Next.Keep the default reverse lookup zone settings and select Next.Type 192.168.0 as the network ID.Select Next.Keep the default dynamic update settings and then select Next.Select Finish. Create a host (A) and associated pointer (PTR) record.From DNS Manager, expand Forward Lookup Zones.Right-click CorpNet.local and select New Host (A or AAAA).In the Name field, enter the host name.In the IP address field, enter the IP address.Select Create associated pointer (PTR) record as needed. The reverse lookup zone must exist for this record to be created.Select Add Hosts.Select OK.Repeat steps 3c-3g to add the additional host records.Select Done.

4.5.5 Create Standard DNS Zones

Complete this lab as follows: Access the CorpDC virtual server.From Hyper-V Manager, select CORPSERVER.Double-click CorpDC to connect to the server.Maximize the window for better viewing. Create a primary forward lookup zone.From Server Manager, select Tools > DNS.Expand CORPDC (the server that will host the zone).Right-click Forward Lookup Zones and select New Zone.In the New Zone wizard, select Next.Make sure Primary zone is selected.Clear Store the zone in Active Directory (this option is only available for domain controllers) and then select Next.In the Zone name field, enter acct.CorpNet.com for the zone and then select Next.Verify that Create a new file with this file name is selected and then click Next.Make sure Do not allow dynamic updates is selected and then click Next.Select Finish to complete the New Zone wizard. Configure zone transfers.Expand Forward Lookup Zones.Right-click acct.CorpNet.com (the new zone) and select Properties.Select the Zone Transfers tab.Verify that Allow zone transfers is selected.Select To any server.Select OK. Create a forward secondary zone.Expand CORPDC3 (the server that will host the new zone).Right-click Forward Lookup Zones and then select New Zone.Select Next.Select Secondary zone as the zone type and then select Next.In the Zone name field, enter acct.CorpNet.com and then select Next.In the Master Servers box, select Click here.Enter 192.168.0.11 or CorpDC.CorpNet.Local as the server that hosts a copy of the zone.Press Enter or click away from the IP address to begin validation.After validation is complete, select Next.Click Finish to complete the New Zone wizard.

4.3.8 Create DHCP Client Reservations

4.4.5 Add a DHCP Server on Another Subnet

Complete this lab as follows: Access the CorpDCHP virtual server.From Hyper-V Manager, select CORPSERVER.Maximize the Hyper-V Manager window to view the available server.Double-click CorpDCHP to connect to the server. Create an IPv4 scope on the CorpDHCP.From Server Manager, select Tools > DHCP.Expand the CorpDHCP.CorpNet.local server node.Right-click IPv4 and then select New Scope.Click Next.In the Name field, enter MySubnet and then select Next.In the Start IP address field, enter 192.168.10.21In the End IP address field, enter 192.168.10.199Click Next > Next > Next > Next.From the Router (Default Gateway) dialog, enter an IP address of 192.168.10.5, select Add, and then select Next.From the Domain Name and DNS Server dialog, add two DNS server addresses as follows:In the IP address field, enter 198.28.56.108 and then select Add.In the IP address field, enter 163.128.78.93 and then select Add.Select Next and then Next again.Leave the Yes, I want to activate this scope now option selected and then select Next.Select Finish to complete the process of creating the DHCP scope.

4.3.4 Configure a DHCP Server

Complete this lab as follows: Access the CorpDHCP Hyper-V server.From Hyper-V Manager, select CORPSERVER.Resize the window to view all virtual machines.Double-click CorpDHCP to access the server. Access the DHCP New Scope Wizard.From Server Manager's menu bar, select Tools > DHCP.Expand CorpDHCP.CorpNet.local.Right-click IPv4 and select New Scope. Name the scope and configure the IP address range.From the New Scope Wizard, select Next.In the Name field, enter Subnet1 and then select Next.In the Start IP address field, enter 192.168.0.20.In the End IP address field, enter 192.168.0.200.Make sure the length is set to 24.Make sure the subnet mask is 255.255.255.0 and then select Next.From the Add Exclusions and Delay window, select Next.Use the default lease duration and select Next.Make sure Yes, I want to configure these options now is selected and then select Next. Configure the default gateway and DNS server.In the IP address field, enter the default gateway address of 192.168.0.5.Select Add and then select Next.In the IP address field, enter the DNS server address of 163.128.78.93.Select Add and then select Next.From the WINS Servers window, select Next. Activate the scope just created.Make sure Yes, I want to activate this scope now is selected and then select Next.Click Finish to close the wizard and create the scope. Configure the laptop in the Lobby to obtain IP and DNS addresses automatically from the DHCP server.From the top left, select Floor 1 Overview.Under Lobby, select Gst-Lap.In the notification area, right-click the Network icon and select Open Network and Internet settings.From the left pane, select Ethernet.From the right pane, select Change adapter options.Right-click Ethernet and then select Properties.Select Internet Protocol Version 4 (TCP/IPv4) and then click Properties.Select Obtain an IP address automatically.Select Obtain DNS server address automatically.Select OK.Click Close to close Ethernet Properties.

4.3.7 Create DHCP Exclusions

4.7.8 Configure an IPv6 Address

Complete this lab as follows: Access the Network Connections window.Right-click Start and then select Settings.Select Network & Internet.From the right pane, select Change adapter options. Configure the external vEthernet network adapter.Right-click the vEthernet (external) adapter and select Properties.Select Internet Protocol Version 6 (TCP/IPv6).Select Properties.Select Use the following IPv6 address and configure the settings as follows:IPv6 address: 2620:14F0:45EA:0001:192:168:0:10Subnet prefix length: 64Select OK.Select Close. Verify the IPv6 address.Right-click Start and select Windows PowerShell (Admin) to verify the address configuration.At the prompt, type ipconfig /all and press Enter view the IPv6 Address.

4.1.13 Configure IP Addresses on Mobile Devices

Complete this lab as follows: Access the iPad IP address settings dialog.Select Settings.Select Wi-Fi.Under Choose A Network, for CorpNet, select the information icon (i). Configure a static IP address.From the right pane, select Static.Configure the IP information as follows:IP address: 192.168.0.85Subnet mask: 255.255.255.0Router (default gateway): 192.168.0.5DNS: 192.168.0.11 Join the iPad to the CorpNet network.Select Join Network.In the Password field, type: @CorpNetWeRSecure!&Select Join.

4.1.11 Configure IP Addresses

Complete this lab as follows: Access the properties for the NIC named Ethernet.Right-click Start and then select Settings.Select Network & Internet.From the right pane, select Change adapter options.Right-click Ethernet and then select Properties. Configure the IP version 4 TCP/IP settings for the Ethernet NIC.Select Internet Protocol Version 4 (TCP/IPv4).Select Properties.Make sure Use the following IP address is selected.This lets you manually configure the IP address and default gateway.Configure the Internet Protocol information as follows:IP address: 192.168.0.254Subnet mask: 255.255.255.0Default gateway: 192.168.0.5Preferred DNS server: 163.128.78.93 or 163.128.80.93Select OK.Select Close. Configure the IP version 4 TCP/IP settings for the Ethernet 2 NIC.From the Network Connections window, right-click Ethernet 2 and then select Properties.Select Internet Protocol Version 4 (TCP/IPv4).Select Properties.Make sure Use the following IP address is selected.Configure the Internet Protocol information as follows:IP address: 10.0.255.254Subnet mask: 255.255.0.0Default gateway: NonePreferred DNS server: NoneSelect OK.Select Close. Ping the preferred DNS server assigned to the Ethernet NIC.Right-click Start and select Windows PowerShell.From the PowerShell prompt, type ping default_preferred_DNS_Server_address and then press Enter.

4.4.4 Configure a DHCP Relay Agent

Complete this lab as follows: Add the DHCP relay agent routing protocol.From Server Manager, select Tools > Routing and Remote Access.Expand IPv4.Right-click General and select New Routing Protocol.Select DHCP Relay Agent and then select OK. Add and configure a relay agent interface.From the left pane, right-click DHCP Relay Agent and select New Interface.Select NetTeam and then select OK.Make sure Relay DHCP packets is selected.Set the boot threshold to 0 (zero).Select OK. Configure the DHCP relay agent properties to identify the DHCP server.Right-click DHCP Relay Agent and select Properties.In the Server address field, enter 192.168.0.14 (the IP address of the DHCP server).Select Add and then select OK. Renew the TCP/IP address and verify the connection.From the top left, select Floor 1.Under Manager Office, select Exec2.Right-click Start and select Windows PowerShell (Admin).In PowerShell, type ipconfig. Notice that the current IP address is on the 169.254.0.0 network.In PowerShell, type ipconfig /renew and then press Enter.The computer should receive an address on the 192.168.10.0 network.From the taskbar, select the network icon to view the connection status.

4.2.4 Configure Alternate Addressing

Complete this lab as follows: Determine the current state of the wireless network.From the Notification area, select the wireless Network icon to view the current state of the wireless network.From the top right, select Answer Questions.Answer the question. Access the Wi-Fi properties dialog.Right-click Start and then select Settings.Select Network & Internet.From the right pane, select Change adapter options.Right-click Wi-Fi and select Properties. Configure the TCP/IPv4 properties to obtain IP and DNS information automatically.Select Internet Protocol Version 4 (TCP/IPv4).Select Properties.Select Obtain IP address automatically.Select Obtain DNS server address automatically. Configure the alternate TCP/IP settings.Select the Alternate Configuration tab to define an alternate configuration for TCP/IP addressing.Select User configured to configure alternate IP settings.Configure the properties as follows:IP Address: 172.16.0.12Subnet Mask: 255.255.0.0Default Gateway: 172.16.255.254Preferred DNS Server: 198.60.22.2Select OK.Select Close. Determine the current state of the wireless network.Select the wireless Network icon in the Notification area and notice that it is now currently connected to the network.From the top right, select Answer Questions.Select Score Lab. What is the current state of the wireless network? There is no internet connection.

4.9.6 Troubleshoot IP Configuration 1

Complete this lab as follows: From the Office2 computer, use the ping and ipconfig commands to test connectivity and gather information.Right-click Start and select Windows PowerShell.From the PowerShell prompt, type ping IP_address and press Enter.Repeat steps 1b to ping the remaining computers.From the top right, select Answer Questions.Answer Question 1.From the PowerShell prompt, type ipconfig /all and press Enter.Notice that DHCP Enabled is set to Yes, meaning the IP information is obtained from a DHCP server.Answer Question 2. From the ITAdmin computer, use the ping and ipconfig commands to test connectivity and gather information.From the top left, select Floor 1 Overview.Under ITAdmin Office, select ITAdmin.Right-click Start and select Windows PowerShell.From the PowerShell prompt, type ping IP_address and press Enter.Repeat steps 2d to ping the remaining computers.Answer Question 3.From the PowerShell prompt, type ipconfig /all and press Enter.Notice that DHCP Enabled is set to Yes, meaning the IP information is obtained from a DHCP server.Answer Question 4.Minimize the Lab Questions dialog. From the CorpServer computer, use the ping and ipconfig commands to test connectivity and gather information.From the top left, select Floor 1 Overview.Under Networking Closet, select CorpServer.Right-click Start and select Windows PowerShell.From the PowerShell prompt, type ping Office2 and press Enter.From the PowerShell prompt, type ping 198.28.2.254 and press Enter.Notice that this computer can get to the internet.From the PowerShell prompt, type ipconfig and press Enter.From the top right, select Answer Questions.Answer Question 5.Since Office2 and ITAdmin obtain their IP addresses from a DHCP server and their default gateway is different from CorpServer (which can access the internet), the problem is most likely related to the IP configuration for the network.Close PowerShell. Access the CorpDHCP server.From Hyper-V Manager, select CORPSERVER.Maximize the window for better viewing.Double-click CorpDHCP to connect to the server. From the CorpDHCP server, use the DHCP console to reconfigure the settings for the DHCP scope.From Server Manager's menu bar, select Tools > DHCP to start the DHCP console.Expand and select CorpDHCP > IPv4 > Scope [192.168.0.1] Subnet1 > Scope Options.Right-click Scope Options and then select Configure Options.Highlight the 003Router option.In the bottom pane, select 192.168.0.4 and then select Remove.In the IP address field (the default gateway address), change the address listed to 192.168.0.5 and select Add.Select OK to apply the change. Verify that the ITAdmin and Office2 computers can access the internet.From the top left, select Floor 1 Overview.Under IT Administration, select ITAdmin.From the PowerShell prompt, type ipconfig /renew.This will request the new IP address information from the DHCP server and reconfigure the settings for the Ethernet connection.Enter ipconfig /all to check the Ethernet configuration.Notice that the default gateway is now correctly configured as 192.168.0.5.At the PowerShell prompt, type ping 198.28.2.254 (the ISP) and then press Enter.From the top left, select Floor 1 Overview.Under Office2, select Office2.Repeat steps 6c-6e to fix the problem for the second workstation.Select Score Lab. Q1From Office2, which, if any, pings failed? The ISP - 198.28.2.254 Q2What is the address of the default gateway assigned to Office2? 192.168.0.4 Q3From ITAdmin, which, if any, pings failed? The ISP - 198.28.2.254 Q4What is the IP address of the default gateway assigned to ITAdmin? 192.168.0.4 Q5What do you see here that might explain why this computer can access the internet, but Office2 and ITadmin can't? The default gateway for CorpServer is different.

4.6.5 Configure NTP

Complete this lab as follows: Install the NTP service on the CorpData server.Under Networking Closet, select CorpData.In the console, type dnf install ntp and then press Enter to begin the installation process.Type y and press Enter to install the NTP package. Verify that the NTP service is running.Type systemctl status ntp and press Enter.From the top left, select Answer Questions.Answer Question 1. Find the NTP server's IP address.Type ip addr show | more to view the NTP server's IP address.Answer Question 2. Add the NTP server as a time source for the Exec computer.From the top left, select Floor1.Under Executive Office, select Exec.Right-click Start and select Windows PowerShell (Admin).Configure Exec to use the NTP server with the following command:w32tm /config /manualpeerlist:192.168.0.24,0x8 /syncfromflags:MANUAL /update Verify that the Exec computer is using the NTP server for time synchronization.In the console, type w32tm /query /status and then press Enter.Select Score Lab. Q1What is the status of the NTP service Active (running) Q2What is the IP address for the NTP server 192.168.0.24

4.5.8 Troubleshoot DNS Records

Complete this lab as follows: Test the connectivity to CorpWeb using the ping command.Right-click Start and select Windows PowerShell (Admin).At the prompt, type ping CorpWeb.CorpNet.local and press Enter.At the prompt, type ping 192.168.0.15 (the IP address for CorpWeb) and press Enter.From the top right, select Answer Questions.Answer Question 1.Close PowerShell. Access the CorpDC virtual server.From Hyper-V Manager, select CORPSERVER.Double-click CorpDC to connect to the server.Maximize the window for better viewing. Create any DNS records needed to fix the problem.In Server Manager, select Tools > DNS.Expand CORPDC > Forward Lookup Zones.Right-click CorpNet.local and select New Host (A or AAAA).In the Name field, enter CorpWeb.Notice that the fully qualified domain name (FQDN) is now CorpWeb.CorpNet.local.Enter 192.168.0.15 in the IP Address field.Select Create associated pointer (PTR) record to automatically create the PTR record for the new host.Select Add Host.Select OK.Select Done to close the New Host dialog. Test the connectivity to CorpWeb using the ping command.Right-click Start and select Windows PowerShell (Admin).At the prompt, type ping CorpWeb.CorpNet.local and press Enter.Answer Question 2.Select Score Lab. Q1While testing connectivity, which ping commands were successful, if any? ping 192.168.0.15 Q2After implementing your fix, which ping commands were successful? ping CorpWeb.CorpNet.local, ping 192.168.0.15

4.9.8 Troubleshoot IP Configuration 3

Complete this lab as follows: Troubleshooting From Office 1, use the ping command to begin troubleshooting the problem by verifying the scope of the connectivity issues.Under Office 1, select Office1.Right-click Start and then select Windows PowerShell.From the PowerShell prompt, run the following ping commands (press Enter after each command):ping 192.168.0.10 (CorpServer)ping 192.168.0.34 (ITAdmin)ping 198.28.2.254 (the internet service provider)Notice that all the pings were unsuccessful. From the IT Administration office, use the ping and ipconfig /all commands to continue determining the scope of the connectivity issues.From the top left, select Floor 1 Overview.Under IT Administration, select ITAdmin.Right-click Start and then select Windows PowerShell.From the PowerShell prompt, run the following ping commands (press Enter after each command):ping 192.168.0.10 (CorpServer)ping 192.168.0.30 (Office2)ping 192.168.0.33 (Exec)ping 198.28.2.254 (the internet service provider)Notice that all the pings were successful.From the PowerShell prompt, type ipconfig /all and press Enter.From the top right, select Answer Questions.Answer Questions 1 and 2. From Office1, use the ipconfig /all command to analyze the differences between Office1 and ITAdmin IP information.From the top left, select Floor 1 Overview.Under Office 1, select Office1.From the PowerShell prompt, type ipconfig /all and then press Enter.Answer Questions 3-6.Minimize the Lab Questions dialog. Fixing the Issue From your troubleshooting steps, you found that Office1 was the only computer having connectivity issues. As you examined and compared Office1's IP settings, you found that it was using the wrong subnet mask and DNS server. Since DHCP was not being used (DHCP Enabled was set to NO), the IP information must have been manually entered using bad or outdated information. You will now rectify the issue by configuring the Office1 computer to obtain its IP information from the DHCP server. From Office 1, configure the network connection to request the IP address information from the DHCP server:Right-click Start and then select Settings.Select Network & Internet.Select Ethernet.From the right pane, select Change adapter options.Right-click Ethernet and then select Properties.Select Internet Protocol Version 4 (TCP/IPv4) and then select Properties.Select Obtain an IP address automatically.Select Obtain DNS server address automatically.Select OK.Select Close.Close the Networking Connections and Settings windows. Verify that Office1 is now able to connect to the internet.From the PowerShell prompt, type ipconfig /all. Verify the following settings:DHCP Enable: YesSubnet mask: 255.255.255.0DNS Servers:192.168.0.11192.168.10.11From the PowerShell prompt, run the following ping commands (press Enter after each command):ping 192.168.0.10 (CorpServer)ping 192.168.0.34 (ITAdmin)ping 198.28.2.254 (the internet service provider)Notice that both pings are successful.From the top right, select Answer Questions.Scroll to the bottom and select Score Lab. Q1What is the subnet mask for ITAdmin? 255.255.255.0 Q2What is the IP address for the first DNS server on ITAdmin? 192.168.0.11 Q3What is the IP address for the subnet mask on Office2? 255.255.255.240 Q4What is the IP address for the first DNS server on Office1? 163.128.78.108 Q5How is Office1 obtaining its IP information? Manually assigned Q6What is most likely causing the networking issues on Office1? There are misconfigured IP addresses.

4.11.6 Explore nslookup

Complete this lab as follows: Use nslookup to query the DNS for the CorpWeb server using its fully qualified domain name.Right-click Start and select Windows PowerShell (Admin).At the PowerShell prompt, type nslookup CorpWeb.CorpNet.local and press Enter.The CorpDC DNS server responds with the name resolution information for CorpWeb. Use nslookup to query the CorpDC3 DNS server for CorpWeb.Type nslookup CorpWeb.CorpNet.local CorpDC3.CorpNet.local and press Enter.The CorpDC3 DNS server responds that it can't find CorpWeb. CorpDC3 does not have a DNS record for CorpWeb. Answer the questions.What is the Problem?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.How would you resolve this problem?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 that the DNS records were consistent between servers.How would you verify that the problem has been fixed?After implementing the above solution, you could verify that the problem was fixed by repeating step 2. The CorpDC3 DNS server should respond with name resolution information for CorpWeb.

4.10.6 Explore Network Communications

Complete this lab as follows: Use the ping and ipconfig commands to troubleshoot network issues.Right-click Start and then select Windows PowerShell (Admin).At the PowerShell prompt, type ping 192.168.0.30 and press Enter to ping Office1.You can successfully ping the IP address of Office1 from ITAdmin.Type ping 199.92.0.33 and press Enter to ping Support.You can't 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.Type ping 192.168.0.5 and press Enter to ping the router's internal interface.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.Type ipconfig and then press Enter to view the IP settings.Notice that there is no default gateway assigned.Type ping 163.128.78.93 and press Enter to ping the external DNS Server.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 can't communicate with devices on other networks. Use the tracert command to see how network packets are forwarded.From the top left, select Floor 1 Overview.Under Executive Office, select Exec.Right-click Start and then select Windows PowerShell (Admin).At the PowerShell prompt, type tracert 198.28.56.1 and press Enter.When you communicate with devices on other networks, the packets go to the default gateway first (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. 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.Enter tracert 163.128.78.93 and press Enter to trace the path to one of the ISP's DNS servers.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.

4.5.4 Configure DNS Addresses

Complete this lab as follows: While completing this lab, use the following DNS information: Preferred DNS server: 208.67.222.222 First alternate DNS server: 208.67.222.220 Second alternate DNS server: 208.67.220.123 Complete this lab as follows: Access the Ethernet properties dialog.Right-click Start and then select Settings.Select Network & Internet.From the right pane, select Change adapter options.Right-click Ethernet and select Properties. Configure the new DNS addresses.Select Internet Protocol Version 4 (TCP/IPv4).Select Properties.Select Use the following DNS server addresses to manually configure the DNS server addresses.Select Advanced to configure more than two DNS server addresses.Select the DNS tab (the top one).Select Add to configure DNS server addresses.Enter the DNS server address and then select Add.Repeat steps 2f-2g to configure the two additional DNS server addresses.Select OK. Validate the new DNS settings.Select Validate settings upon exit and then select OK.Select Close to close Ethernet Properties.

Chapter 4 labs

Kaugnay na mga set ng pag-aaral

fundamental test a & b

The Neurological System (Part 2) Test

Ch. 1 & 2

Analogy 1

mnemotecnias

ISS EXAM 3

A&P 1 chapters 10

19

Chapter 13, 14, and 15 AUDIT

CNA

MIDTERMS 1: ENTREPRENEURSHIP

Unit 4: Chemical Reactions

Chapter 5

chapter 30

Types of Policies

Sodium-Potassium Pump

Visual Basic Chapter 2 Mini-quizes

ISDS 3115 Final

Semester 3: Unit 1 exam

ap gov