A.2.5 Network Pro Domain 5: Troubleshooting

You are the security analyst for a small corporate network. You want to find specific information about the packets being exchanged on your network using Wireshark. In this lab, your task is to: Use Wireshark to capture packets from the enp2s0 interface. Use a Wireshark filter to isolate and examine packets for:All network traffic for 192.168.0.0.Answer Question 1.All network traffic for the 192.168.0.45 host.Answer Question 2.All IP traffic with a source address of 192.168.0.45.Answer Question 3.All IP traffic with a destination address of 192.168.0.45.Answer Question 4.All HTTP traffic on port 80.Answer Question 5.All packets with an Ethernet Mac address containing 11:12:13.Answer Question 6.All TCP packets that contain the word "password".Answer Question 7.

Complete this lab as follows: Begin a Wireshark capture.From the Favorites bar, select Wireshark.Maximize the window for easier viewing.Under Capture, select enp2s0.Select the blue fin to begin a Wireshark capture. Apply the net 192.168.0.0 filter.In the Apply a display filter field, type net 192.168.0.0 and press Enter.Look at the source and destination addresses of the filtered packets.Select the red square to stop the Wireshark capture.In the top right, select Answer Questions.Answer Question 1. Apply the host 192.168.0.45 filter.Select the blue fin to begin a Wireshark capture.In the Apply a display filter field, type host 192.168.0.45 and press Enter.Look at the source and destination addresses of the filtered packets.Answer Question 2. Apply the ip.src==192.168.0.45 filter.In the Apply a display filter field, type ip.src==192.168.0.45 and press Enter.Look at the source and destination addresses of the filtered packets.Answer Question 3. Apply the ip.dst==192.168.0.45 filter.In the Apply a display filter field, type ip.dst==192.168.0.45 and press Enter.Look at the source and destination addresses of the filtered packets.Answer Question 4. Apply the tcp.port==80 filter.In the Apply a display filter field, type tcp.port==80 and press Enter.Look in the Info column of the filtered packets.Answer Question 5. Apply the eth contains 11:12:13 filter.In the Apply a display filter field, type eth contains 11:12:13 and press Enter.Look at the source and destination addresses of the filtered packets.Answer Question 6. Apply the tcp contains password filter.In the Apply a display filter field, type tcp contains password and press Enter.Select the red box to stop the Wireshark capture.From the bottom pane, locate the password.Answer Question 7.Select Score Lab.

You are a network technician for a small corporate network. You recently updated the wireless networks in the building. The Exec-Laptop is now having problems connecting to the CorpNet wireless network and the internet. You need to diagnose and fix this problem.

Complete this lab as follows: Check to see if the ITAdmin computer can connect to the wireless network.Under IT Administration, select ITAdmin.In the Notification Area, select the wireless network icon to view the available networks in order to see what is being shown on a working computer.Select the CorpNet wireless network.Select Connect.Enter @CorpNetWeRSecure!& for the security key and then select Next.ITAdmin is now connected to the CorpNet wireless network. Because this computer can connect to the wireless network, the problem may be limited to only the Exec-Laptop laptop in the Executive Office. Troubleshoot and fix the wireless networking on Exec-Laptop.From the top left, select Floor 1 Overview to switch to Exec-Laptop.Under Executive Office, select Exec-Laptop.In the Notification Area, select the wireless network icon to view the available networks.Note that there are no wireless networks shown as available for this laptop. Possible causes for this include:The wireless network interface card is not turned on (the wireless switch on the exterior of the laptop is in the OFF position). Since no wireless networks are shown in the list, you must take additional steps.The wireless network's SSID is not broadcasting. However, from Step 1, you know that the wireless access point is broadcasting the SSID.The wireless access point is not powered on. However, from Step 1, you know that the wireless access point is powered on.From the top left, select Executive Office to switch to the devices found in the executive office.On the front of the Exec-Laptop, check to see if the switch for the wireless network interface card is in the On position.Notice that it is in the OFF position instead.Slide the wireless switch to the On position to turn the wireless network interface card on.On the laptop monitor, select Click to view Windows 10.In the Notification Area, select the wireless network icon to view the available networks. The CorpNet wireless network is now displayed in the list of available networks.Select the CorpNet wireless network.Select Connect.Enter @CorpNetWeRSecure!& for the security key and then select Next.Exec-Laptop is now connected to the CorpNet wireless network.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignment. Employees in Office 1 and the Executive Office are reporting problems with their network connections. In this lab, your task is to explore, diagnose, and fix the reported TCP/IP configuration problems. Use the following troubleshooting tools: The ping, ipconfig, or tracert command utility The Network and Sharing Center in the Windows 10 or Windows 2016 operating system The DHCP server console in the Windows 2019 operating system The network diagram/schematic as found in Exhibits

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.

You are a network technician for a small corporate network. Minutes ago, your entire building had a power blackout. The power has been partially restored, but there are still offices and networking closets without power. Employees in the Executive Office and the Support Office have called to report that they can't access the internet or other computers on the network. You need to diagnose and fix the problem as it pertains to the network. The following IP addresses are used in this lab: LocationComputer NameIP AddressNetworking ClosetCorpServer192.168.0.10Office 1Office1192.168.0.30Office 2Office2192.168.0.31Support OfficeSupport192.168.0.32IT AdministrationITAdmin192.168.0.33Executive OfficeExec192.168.0.34LobbyGst-Lap192.168.0.35 In this lab, your task is to: Use the following troubleshooting tools to diagnose the problem on the network:The ping command utility, to ping the IP addressesThe network activity lights for all networking devicesThe Network and Internet Status page found in the Windows 10 or Windows Server 2019 Settings app Fix the problem and, as necessary, use the known good spares on the Shelf. Use the troubleshooting tools to confirm the problem resolution.

Complete this lab as follows: From Exec, use the ping command to begin troubleshooting the connectivity problem.Under Executive Office, select Exec.Right-click Start and then select Windows PowerShell (Admin).From the PowerShell prompt, type ping workstation IP address and then press Enter.Repeat step 1c for the remaining workstations.Notice that all the pings fail except to itself (192.168.0.34). From Support, repeat the same troubleshooting steps used in the Executive Office to further discover the scope of the problem.From the top left, select Floor 1 Overview.Under Support Office, select Support.From the Favorites bar, select Terminal.From the terminal prompt, type ping workstation IP address and then press Enter.If needed, press Ctrl + C to stop the pinging process.Notice that all the pings fail except the ping to itself (192.168.0.32).

You are a network technician for a small network. The manager in Office 2 says that she can no longer communicate with any other computer on the network. You need to diagnose and fix the problem. The following IP addresses are used in this lab: LocationComputer NameIP AddressNetworking ClosetCorpServer192.168.0.10Office 1Office1192.168.0.30Office 2Office2192.168.0.31Support OfficeSupport192.168.0.32IT AdministrationITAdmin192.168.0.33Executive OfficeExec192.168.0.34LobbyGst-Lap192.168.0.35 In this lab, your task is to: Use the following troubleshooting tools to diagnose the problem on the network:The ping command utilityThe ipconfig command utilityThe network activity lights for all networking devices Fix the problem and, as necessary, use known good spares on the Shelf if needed. Use the troubleshooting tools to confirm the problem's resolution.

Complete this lab as follows: From the IT Administration office, ping each workstation on the network.Under IT Administration, select ITAdmin.Right-click Start and select Windows PowerShell (Admin).From the PowerShell prompt, type ping [workstation's IP] and then press Enter.Notice that all the pings are successful except the one to Office2. This verifies that there is connectivity between all other workstations on the network except Office2. This indicates that the scope of the problem is probably limited to Office2. Because the scope of the problem is currently limited to Office2, you should look for common errors or solutions that you can test quickly. Confirm that the network cable is connected to the NIC and the wall plate.From the top left, select Floor 1 Overview.Under Office 2, select Hardware to view the hardware in Office 2.Above the computer, select Back to view the back of the computer.Notice that an Ethernet cable is plugged into the network card in the computer.Select the Ethernet RJ45 shielded cable that is plugged into the computer.Scroll to the right and view the Ethernet wall plate.Notice that the cable in the computer is plugged into the Ethernet port on the wall plate.Scroll back to the computer and check for activity lights for the network port.Notice that no lights are blinking. This indicates that there is no connection to the network. From Office2, replace the cable between the workstation and the wall plate.Drag the Ethernet cable from the back of the computer and place it on the workspace.Drag the Ethernet cable from the wall plate and place it on the workspace.Under Shelf, expand Cables.Select Cat6a Cable, RJ45.From the Selected Component pane:Drag an RJ45 Shielded Connector to the Ethernet port on the computer.Drag the unconnected RJ45 Shielded Connector to the Ethernet port on the wall plate.The lights for the network card are still not active. You could replace the NIC in Office2, but replacing cables is quicker. From the Networking Closet, check the switch to ensure that it is powered on.From the top left, select Floor 1 Overview.Under Networking Closet, select Hardware.Notice that the power light for the Cisco switch indicates that it is powered on. Also, since the workstation in the IT Administration office can communicate through the switch, you know that the device is not turned off and is functioning properly. From the Networking Closet, observe the activity lights for all ports and check for cable connections.Zoom in on the switch ports.Notice that there are activity lights for other ports, yet there is a lack of activity for port 4.Possible causes include:The cable between Office 2's patch panel port and the switch is bad or disconnected.Port 4 on the switch is disabled or shut down.Select the cable plugged into Off 2.Notice that the other end of the cable (which is highlighted) is plugged into port 4. From the Networking Closet, replace the patch panel cable.Drag the Ethernet cable from Off 2 and place it on the workspace.Drag the Ethernet cable from port 4 and place it on the workspace.Under Shelf, expand Cables.Select Cat6a Cable, RJ45.From the Selected Component pane:Drag an RJ45 Shielded Connector to Off 2.Drag the unconnected RJ45 Shielded Connector to port 4.The activity light for port 4 still does not indicate network activity.Making a console connection to the switch to confirm that port 4 is enabled is a viable approach to this problem, but the lab does not provide a console application to confirm the switch's port settings. From Office 2, add a known good spare NIC to the Office2 computer and connect the Ethernet cable to the new card.From the top left, select Floor 1 Overview.Under Office 2, select Hardware.Above the computer, select Front.Select the power button to turn the computer off.Above the computer, select Motherboard to open the case.Under Shelf, expand Network Adapters.Drag Network adapter, Ethernet 1000BaseTX, PCIe to the PCIe slot on the motherboard.Above the computer, select Back to replace the case.Drag the Ethernet cable from its existing NIC to the new NIC just added. Power on the Office2 computer and test connectivity to the network.Above the computer, select Front.Select the power button to turn the computer on.Right-click Start and then select Windows PowerShell (Admin).At the PowerShell prompt, type ipconfig.Notice that Office2 received a new/different IP address from the DHCP server because the new NIC makes it look like a different computer.From the PowerShell prompt, type ping [workstation's IP] and then press Enter.Repeat step 8e for each remaining computer.All pings are now successful.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignments. The owner of the company in the Executive Office and a temporary employee in the IT Administrator office both report that their workstations can communicate with some computers on the network, but cannot access the internet. You need to diagnose and fix the problem. While completing this lab, use the following IP addresses: Computer NameIP AddressCorpServer192.168.0.10(Unknown)198.28.2.254(the ISP)ITAdmin(Unknown)Exec(Unknown) In this lab, your task is to complete the following: To help troubleshoot the issue, use:The ping, ipconfig, and tracert commands from the above computers.The DHCP server console in the Windows Server 2019 operating system, which is running as a VM on the CorpServer computer. 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: 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.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for IP address assignments. The employee in Office 1 reports that their workstation can communicate with some computers on the network but not on the internet. You need to diagnose and fix the problem. While completing this lab, use the following IP addresses: Computer NameIP AddressCorpServer192.168.0.10Office2192.168.0.30Exec192.168.0.33ITAdmin192.168.0.34(Unknown)198.28.2.254(the ISP) In this lab, your task is to: Use the following troubleshooting tools to diagnose the problem on the network:The ping, ipconfig, or tracert command line utilitiesThe Network & Internet settings on the Windows 10 operating system Fix the problem at the applicable workstation(s) as necessary. Use the troubleshooting tools to confirm that the problem is resolved.

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.

You are a network technician for a small corporate network. An employee in Office 1 says that after she added a pair of speakers to her workstation, she could no longer communicate with the computer in the Networking Closet. You need to diagnose and fix the problem. The following IP addresses are used in this lab: LocationComputer NameIP AddressNetworking ClosetCorpServer192.168.0.10Office 2Office2192.168.0.31IT AdministrationITAdmin192.168.0.33 In this lab, your task is to: Use the following troubleshooting tools to diagnose the problem in the network:The ping command utilityThe network activity lights for all networking devicesThe Network and Internet Status page found in the Windows 10 or Windows Server 2019 Settings app Fix the problem and, as necessary, use the known good spares on the Shelf. Use the troubleshooting tools to confirm the problem resolution.

Complete this lab as follows: From the Office 1 computer, use the ping command to begin troubleshooting the connectivity problem.Under Office 1, select Office1.Right-click Start and then select Windows PowerShell (Admin).From the PowerShell prompt, ping the following computers:CorpServer: Type ping 192.168.0.10 and then press Enter.Office2: Type ping 192.168.0.31 and then press Enter.ITAdmin: Type ping 192.168.0.33 and then press Enter.Notice that all the pings fail. Check for a connection to the internet using the Settings app.Right-click Start and then select Settings.Select Network & Internet.Notice that the diagram on the Status pane shows that the computer is not connected to a network.Close the Settings dialog. Check for a network connection by viewing the NIC port of the Office1 computer.From the top left, select Office 1 to view the hardware in this office.Above the Office1 workstation, select Back to see the back of the computer.Notice that there is no Ethernet cable attached to the computer. However, there is an Ethernet cable plugged into the wall plate. The cable could have been accidently disconnected from the computer when the user added the speakers. Connect the network cable from the wall outlet to Office1.Select the Ethernet cable plugged into the wall plate.From the Selected Component pane, drag the unconnected RJ45 Shielded Connector to the NIC on the back of the Office1 computer.Notice that the status and link lights on the NIC are green and active. Check for network connectivity from Office1.On the Office1 monitor, select Click to view Windows 10.Right-click Start and select Settings.Select Network & Internet.The diagram in Status page shows a connection to the network and internet.(Optional) Ping each workstation on the network.Each ping attempt now succeeds.

You are a network technician for a small corporate network. The employee in Office 1 says that they can't communicate with the computer in Office 2 and has asked that you come to their office to fix the problem. In this lab, the following IP addresses are used: LocationComputer NameIP AddressNetworking ClosetCorpServer192.168.0.10Office 1Office1192.168.0.30Office 2Office2192.168.0.31IT AdministrationITAdmin192.168.0.33Executive OfficeExec192.168.0.34 In this lab, your task is to: Use the following troubleshooting tools to diagnose the problem in the network:The ping command utilityThe network activity lights for all networking devicesThe Network and Internet Status page found in the Windows 10 or Windows Server 2019 Settings app Fix the problem and, as necessary, use the known good spares on the Shelf. Use the troubleshooting tools to confirm that the problem was resolved.

Complete this lab as follows: From the Office1 computer, use the ping command to begin troubleshooting the connectivity problem.Under Office 1, select Office1.Right-click Start and then select Windows PowerShell (Admin).From the PowerShell prompt, type ping workstation and then press Enter.Repeat step 1c for the remaining workstations.Notice that all the pings are successful except the ping to Office2 (192.168.0.31). From the Office2 computer, use the ping command to further troubleshoot the connectivity problem.From the top left, select Floor 1 Overview.Under Office 2, select Office2.Right-click Start and then select Windows PowerShell (Admin).From the PowerShell prompt, type ping workstation and then press Enter.Repeat step 2d for the remaining workstations.Notice that all the pings fail except to itself (192.168.0.31). From Office2, check for a connection to the internet.Right-click Start, and select Settings.Select Network & Internet.Notice the diagram on the Status pane shows no connection to a network.Close the Settings dialog. Check for a network connection by viewing the NIC port of the Office2 computer.From the top left, select Office 2 to view the hardware in this office.Above the Office2 workstation, select Back to see the back of the computer tower.The link and status lights on the NIC port are not blinking, indicating no connection to the network. This can be due to:A bad NICA faulty cable (easy to test)An unplugged cable (easy to test)A turned-off or faulty switch or hub portConfirm that the network cable is connected to the NIC and the wall plate by selecting the cable plugged into the NIC.Notice that both ends of the cable are connected correctly. This means that the Ethernet cable could be faulty. Replace the network cable from Office2 and the wall.Select the network cable plugged into Office2 and drag it to the shelf.Drag the RJ45 cable from the wall plug to the shelf.Under Shelf, select Cat5e Cable, RJ45.From the Selected Component pane:Drag an RJ45 Connector to the network wall plug.Drag the unconnected RJ45 Connector to the NIC on the back of the Office2 computer.Notice the link and status lights for the connection are not green and active. This means that the cable may not have been bad. It's time to check for issues in the Networking Closet. From the Networking Closet, check the switch to ensure that it's powered on.From the top left, select Floor 1 Overview.Under Networking Closet, select Hardware.Notice that the system light for the switch indicates that it is powered on.Observe the activity lights for all ports on the switch.Notice that there is no activity for Port 4. Possible causes include:The cable between Office 2's patch panel port and the switch is bad or disconnected.Port 4 on the switch is disabled or shutdown. Verify that the network cable is connected to Office2's patch panel port and the switch.Select Port 4 on the switch.Notice that it shows the cable is also plugged into the patch panel. This may mean that this cable is faulty. Replace the patch panel cable for Office2 to the switch.Select the cable plugged into Port 4 and drag it to the workspace.From the patch panel, drag the cable plugged into Off 2 to the workspace.Under Shelf, select Cat5e Cable, RJ45.From the Selected Component pane:Drag an RJ45 Connector to Port 4 on the switch.Drag the unconnected RJ45 Connector to the patch panel port for Off 2 (Office 2).Notice the link and status lights for Port 4 are now green and active. From Office 2, check for a network connection.From the top left, select Floor 1 Overview.Under Office 2, select Hardware.Check for an active link light on the network card of the computer.The light is blinking, indicating a network connection.On the Office2 monitor, select Click to view Windows 10.Right-click Start and select Settings.Select Network & Internet.The diagram in Status page shows a connection to the network and internet.(Optional) Ping each workstation in the network.Each ping attempt now succeeds. From Office 1, use the ping command to verify connectivity to Office 2.From the top left, select Floor 1 Overview.Under Office 1, select Office1.From the PowerShell prompt, type ping Office2 and then press Enter.Notice that the ping to Office 2 succeeds. The problems is resolved.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignment. The employees in the IT Administration Office and Office 2 report that their workstations can communicate with some computers on the network but cannot access the internet. You need to diagnose and fix the problem. The following IP addresses are used in your network: DeviceIP AddressCorpServer192.168.0.10ITAdmin192.168.0.31Office2192.168.0.34ns1.nethost.net(ISP)198.28.2.254 In this lab, your task is to troubleshoot and fix the issue using the following procedures: From the Office2 computer, use the ping and ipconfig commands to test connectivity and gather information.Answer Questions 1 and 2. From the ITAdmin computer, use the ping and ipconfig commands to test connectivity and gather information.Answer Questions 3 and 4. From the CorpServer computer, use the ping and ipconfig commands to test connectivity and gather information.Answer Question 5 and determine which changes need to be made to correct the issue. Using the CorpDHCP server, accessed as a VM from CorpServer, implement the fix to the issue. Verify that the ITAdmin and Office2 computers can access the internet.

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.

You are a network technician for a small corporate network. You have recently updated the wireless networks in the building. The WLAN is named CorpNet. In this lab, your task is to explore, diagnose, and fix the wireless network configuration problems. Use the following troubleshooting tools: The Network and Internet settings in the Windows 10 operating system The Windows Settings app The Ruckus wireless controller interface Viewing hardware settings

Complete this lab as follows: Identify the wireless connections on the Office2-Lap.Under Office 2, select Office2-Lap.In the notification area, select the wireless network icon.Which wireless networks are available to Office2-Lap? Which wireless network is Office2-Lap connected to?Available networks are: CorpNet, StarSky, and NetGearWirless. Forget the HomeWireless network on Office2-Lap.Right-click Start and then select Settings.Select Network & Internet.Select Wi-Fi.Select Manage known networks.Which known networks are displayed? CorpNet and HomeWireless.Select HomeWireless.Select Forget.Close the Settings app. View the wireless controller's configuration interface using Google Chrome.From the taskbar, select Google Chrome.In the URL field, enter 192.168.0.6 and then press Enter.Maximize the window for better viewing.In the Admin Name field, enter admin.In the Password field, enter password.Select Login.Select the Configure tab.From the left menu, select WLANs.Under WLANs, select Edit located in the table under Actions.From the top right, select Answer Questions.Answer Questions 1 and 2.Minimize the Lab Questions dialog. Identify the wireless connections on Gst-Lap.From the top left, select Floor 1 Overview.Under Lobby, select Gst-Lap to switch to laptop located in the lobby.From the top right, select Answer Questions.Move the question dialog to the left.In the notification area, select the wireless network icon.Answer Question 3.Minimize the Lab Questions dialog.Right-click Start and then select Settings.Select Network & Internet.Select Wi-Fi.Select Manage known networks.Which known networks are displayed? CorpNet.In the notification area, select the wireless network icon.Select the CorpNet wireless network name.Select Connect automatically and then click Connect.Why did Gst-Lap connect without you entering the network security key? It's already a managed/known network. Identify the wireless connections on Exec-Laptop.From the top left, select Floor 1 Overview.Under Executive Office, select Exec-Laptop.In the notification area, select the wireless network icon (now being shown as an airplane).What wireless networks are available to Exec-Laptop? None.From the top left, select Executive Office to switch to the hardware for of the devices in the executive office.Examine the position of the wireless switch found in the lower left of the laptop's case.What is the position of this switch? Off.Slide the wireless switch to the On position to turn the wireless network interface card on.On the Exec-Laptop monitor, select Click to view Windows 10 to switch to the operating system.Select the wireless network icon in the notification area to view the available networks.Which wireless networks are available to Exec-Laptop now?Manually connect to the CorpNet wireless network as follows:Select the CorpNet wireless network name.Select Connect.Enter @CorpNetWeRSecure!& for the wireless network and then select Next.Exec-Laptop successfully connected to the CorpNet network. Score the lab.From the top right, select Answer Questions.Select Score Lab.

You are the administrator for the CorpNet.local domain. The CorpDC and CorpDC3 servers are the DNS servers for the domain. You are responsible for CorpDC, which resides in Building A. Some users report that they are unable to contact the CorpWeb server. In this lab, your task is to: Test the connectivity to CorpWeb using the ping command.Ping CorpWeb.CorpNet.localPing 192.168.0.15 (the IP address for CorpWeb).Answer Question 1. Create any DNS records needed to fix the problem using the following information:Host name: CorpWebIP address: 192.168.0.15 Test the connectivity to CorpWeb using the ping command.Ping CorpWeb.CorpNet.localPing 192.168.0.15 (the IP address for CorpWeb).Answer Question 2.

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.

In this lab, you explore different methods of troubleshooting network communication problems that may result from such things as bad network cards and cables. While troubleshooting, you will use the ping command, the link and network activity lights on network cards and switches, and the Windows Settings app. Use Exhibits to see the network diagram and wiring schematics of the network as needed.

Complete this lab as follows: View the current state of the first six ports on the Cisco switch and its accompany patch panel.Under Networking Closet, select Hardware.Zoom in on the Cisco switch in the rack to view the power and network activity lights.When a component's power light (the left light) is on, you know the device is plugged in and turned on.The network activity light (the right light) tells you which ports are connected to an active device. When this light is blinking, you know that network traffic is being transmitted through the port.From the top right, select Answer Questions.Answer Questions 1-3.Minimize the Lab Questions window. Determine which computers are plugged into ports 1 and 3.From the Cisco switch, select the wire plugged into ports 1 and 3.Look for at the patch panel and find the cables accompanying port.From the top right, select Answer Questions.Answer Question 4.Minimize the Lab Questions window. From the ITAdmin workstation, ping each of the following computers using the IP addresses shown:Computer nameIP AddressOffice1192.168.0.30Exec192.168.0.34CorpServer192.168.0.10Building A router192.168.0.5CorpNet router's internal interface198.28.56.1CorpNet router's external interface198.28.56.17ISP163.128.1.1From the top left, select Floor 1 Overview.Under IT Administration, select ITAdmin.Right-click Start and then select Widows PowerShell (Admin).Type ping ip_address and then press Enter.Make a note as to whether the ping was successful or not.Repeat step 3d for each remaining IP addresses.Answer Question 5-6.Minimize the Lab Questions window. From ITAdmin, check for network connectivity.Look at the Network icon in the notification area.This icon indicates a normal network connection.Select the Network icon.You are now shown the networks to which this computer is connected (CorpNet.local).Right-click Start and then select Settings.Select Network & Internet.Under Status, you see that this computer is connected to the internet.From the left pane, select Ethernet.You are shown the network to which you are connected.Close the Settings app. From the hardware view of ITAdmin, check for network connectivity and activity by viewing the network card's link lights.From the top left, select IT Administration to view the hardware of the computers in this office.Above the ITAdmin workstation (not the monitor), select Back. Notice that:The link light for the network card is illuminated, indicating a physical connection (link) between this workstation and the next device (the network switch).The network activity light is blinking, indicating that network traffic is being transmitted on this connection.These two lights match what you saw when viewing the cables connecting ITAdmin to the Cisco switch and the patch panel. From Exec operating system, check for network connectivity.From the top left, select Floor 1 Overview.Under Executive Office, select Exec.From the Notification area of the taskbar, view the Network icon.The Network icon in the Notification area indicates that the device is not connected.Select the Network icon.No network connections are shown.Right-click Start and then select Settings.Select Network & Internet.Under Status, you see that this computer is not connected to any networks.Close the Settings app. From the hardware view of Exec, check for network connectivity and activity by viewing the network card's link lights.From the top left, select Executive Office to view the hardware for the computers in this office.Above the Exec workstation (not the laptop), select Back.Zoom in on the Ethernet cable and examine its link lights.The link and network activity lights for the Ethernet port with a cable plugged in are not illuminated. This indicates there is no connection to the switch.Possible causes for no connectivity include:A faulty or disconnected cableA bad network card (NIC)A faulty or disabled switch port From Exec, test the possibility of a bad NIC by dragging the network cable from the existing network card to the onboard port.Drag the Ethernet cable from its existing location to the Ethernet onboard port.Answer Question 7. From Exec operating system, check for network connectivity.On the Exec monitor, select Click to view Windows 10.Use the ping command to try to access the following computers:Right-click Start and then select Widows PowerShell (Admin).Type ping 192.168.0.10 (The CorpServer) and press Enter.Type ping 163.128.1.1 (The ISP) and press Enter.Both pings are successful.Look at the Network icon in the notification area.The icon indicates a normal network connection.Right-click Start and then select Settings.Select Network & Internet.Under Status, you see that this computer is now connected to the internet.Close the Settings app. In the Networking Closet, check the link light status for Exec.From the top left, select Floor 1 Overview.Under Networking Closet, select Hardware.Zoom in on the Cisco switch.The network activity lights on the switch (port 1) are blinking indicating that the Exec computer has a connection and network activity. From the hardware view of Office1, check for network connectivity.From the top left, select Floor 1 Overview.Under Office 1, select Hardware.Above the workstation, select Back.The link and network activity lights are not illuminated, indicating that there is no connection to the switch.Possible causes for no connectivity include:A faulty or disconnected cableA bad network card (NIC)A faulty or disabled switch port Test the network cable for Office1.Unplug the existing Ethernet cable from the wall plate and from the back of the computer.From the Shelf, expand Cables.Select the Cat6a Cable, RJ45 (a known good cable).From the Selected Component pane:Drag one RJ45 Connector to the Ethernet port (red) in the wall plate.Drag the other RJ45 Connector to the Ethernet port in the computer.The link and network activity lights on the NIC still don't show an active connection. Therefore, the cable in the office wasn't the problem. From the wiring closet, test the network patch cable for Office1.From the top left, select Floor 1 Overview.Under Networking Closet, select Hardware.Remove the existing patch cable from Off 1 (Office 1) and from port 3.From the Shelf, select the Cat6a Cable. RJ45.From the Selected Component pane:Drag one RJ45 Connector to the Off 1 port on the patch panel.Drag the other RJ45 Connector to the port 3 on the Cisco switch.The link and network activity lights for port 3 indicates an active connection. The patch cable in the Network Closet was the problem. From Office1, test the network connection to the following devices.From the top left, select Floor 1 Overview.Under Office 1, select Office1.Right-click Start and then select Windows PowerShell (Admin).Ping the following devices:Office1: 192.168.0.30Exec: 192.168.0.34ISP: 163.128.1.1You are now able to ping all devices verifying local and internet connectivity.(Optional)Look at the Network icon in the Notification area.The icon indicates a normal network connection.Right-click Start and then select Settings.Select Network & Internet.Under Status, you see that this computer is now connected to the internet.Close the Settings app. Score the lab.From the top right, select Answer Questions.Select Score Lab.