Exam 2

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignment. The employee in Office 1 reports that his workstation can communicate with some computers on the network, but not on the internet. You need to diagnose and fix the problem. In this lab, your task is to complete the following: Use the following troubleshooting tools to diagnose the problem in the network:The ping, ipconfig, or tracert command utilityThe Network and Sharing Center in the Windows 10 or Windows Server 2016 operating systemThe DHCP server console in the Windows Server 2016 operating system Fix the problem at the workstation, the DHCP server, or both as necessary. Use the troubleshooting tools to confirm that the problem is resolved.

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

Your branch offices are connected to the main office and the internet through the SFO router. You need to configure static routes on the SFO router for each destination. Both of the serial interfaces connecting the SFO router to the main office and the internet have been configured and are up. Complete this lab as follows: Configure a static route to the 10.0.0.0/8 network (LAX). Configure a default route to the internet. Save your changes to the startup-config file.

In the diagram, select the SFO router. Press Enter. At the prompt, enter: SFO>enable SFO#configure terminal SFO(config)#ip route 10.0.0.0 255.0.0.0 172.17.12.98 SFO(config)#ip route 0.0.0.0 0.0.0.0 160.12.99.1 Make sure to add a space between the 2 octets of zeros. SFO(config)#exit SFO#copy run start Press Enter. Press Enter to save your changes.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignment. The owner of the company in the Executive Office and a temporary employee in IT Administrator office both report that their workstations can communicate with some computers on the network, but cannot communicate with the internet. You need to diagnose and fix the problem. In this lab, your task is to complete the following: Use the following troubleshooting tools to diagnose the problem in the network:The ping, ipconfig, or tracert command utilityThe Network and Sharing Center in the Windows 10 or Windows Server 2016 operating systemThe DHCP server console in the Windows Server 2016 operating system Fix the problem at the workstation, the DHCP server, or both as necessary. Use the troubleshooting tools to confirm the resolution of the problem.

llows: 1. On Exec, verify the connectivity problem by pinging ITAdmin, CorpServer, and the Internet Service Provider (ISP) as follows: Under Executive Office, select Exec. In the Search field on the taskbar, enter cmd. Under Best match, right-click Command Promptand select Run as Administrator. At the command prompt, type ping itadminand press Enter.Notice that ITAdmin is translated to 169.254.201.12, and the ping is returned.The IP address for ITAdmin is in the APIPA range (169.254.0.1 to 169.254.255.254). Since Exec can communicate with ITAdmin, it is likely that Exec is has been assigned an APIPA IP address also. Type ping corpserverand press Enter.The request times out. Type ping 65.86.1.1and press Enter.The request times out. There is probably no default gateway configured so that the workstation can send traffic to another network. Type ipconfig /alland press Enter.Notice that DHCP is enabled, but there is no default gateway address or DHCP Server entry.Notice that the Autoconfiguration IPv4 Address is 169.254.201.10.This confirms that Exec is using an APIPA IP address. It also indicates that there is a problem getting IP configurations from a DHCP server. 2. On ITAdmin, verify the connectivity problem by pinging Exec, CorpServer, and the Internet Service Provider (ISP) as follows: From the top navigation tabs, select Floor 1 Overview. Under IT Administration, select ITAdmin. In the Search field on the taskbar, enter cmd. Under Best match, right-click Command Promptand select Run as Administrator. At the command prompt, type ping execand press Enter.Notice that Exec is translated to 169.254.201.10, and the ping is returned. Type ping corpserverand press Enter.The request times out. Type ping 65.86.1.1and press Enter.The request times out. Type ipconfig /alland press Enter.Notice that DHCP is enabled, but there is no default gateway address or DHCP Server entry.Notice that the Autoconfiguration IPv4 Address is 169.254.201.12.This is the same problem occurring with the Exec workstation. 3. Activate the scope as follows: From the top navigation tabs, select Floor 1 Overview. Under Networking Closet, select CorpServer. In Hyper-V Manager, CORPSERVER. Maximize the window for easier viewing. Under Virtual Machines, right-click CorpDHCPand select Connect. In Server Manager, select Tools> DHCP. In the left pane, expand CorpNet.com. Select IPv4.In the center pane, notice that the Scope [192.168.0.1] Subnet1 is inactive. It has a small red down arrow added to the folder icon. Right-click Scope [192.168.0.1 Subnet1and select Activate. 4. Use Exec to renew the IP address configurations on the Ethernet adapter as follows: From the top navigation tabs, select Floor 1 Overview. Under Executive Office, select Exec. At the command prompt, type ipconfig /renewand press Enter. Type ipconfig /alland press Enter.Notice that the IPv4 address is now 192.168.0.30, the default gateway address is now 192.168.0.5, and the DHCP Server is now 192.168.0.14. Type ping corpserverand press Enter.Notice the reply from CorpServer. Type ping 65.86.1.1and press Enter.Notice the reply from the ISP address. Type ping itadminand press Enter.The request times out. This is expected because ITAdmin has not renewed its IP addresses. 5. Renew ITAdmin's IP address configurations on the Ethernet adapter as follows: From the top navigation tabs, select Floor 1 Overview. Under IT Administration, select ITAdmin. At the command prompt, type ipconfig /renewand press Enter. Type ipconfig /alland press Enter.Notice that the IPv4 address is now 192.168.0.31, the default gateway address is now 192.168.0.5, and the DHCP Server is now 192.168.0.14. Type ping corpserverand press Enter.Notice the reply from CorpServer. Type ping 65.86.1.1and press Enter.Notice the reply from the ISP address. Type ping execand press Enter.Notice the reply from Exec.

You are a network technician for a small corporate network. Executives have decided to add IP phones for guests in the Lobby and another for the company owner in the Executive Office. In this lab, your task is to complete the following: In the Lobby, complete the following:Connect the LAN port on the IP phone to the Ethernet port on the wall outlet.Plug in the IP phone using the power adapter. In the Executive Office, complete the following:Connect the LAN port on the IP phone to the Ethernet port on the wall outlet.Plug in the IP phone using the power adapter.Use the surge protector from the Shelf to provide more power outlets.Connect the PC port on the IP phone to the workstation's NIC.Confirm that the workstation is still connected to the network and the internet using the Network and Sharing Center.

1. Connect the IP phone in the Lobby to the network as follows: a. Under Lobby, select Hardware. b. On the Shelf, expand Phones. c. Drag the IP phone to the Workspace. d. Above the IP phone, select Back to switch to the back view of the phone. e. On the Shelf, expand Cables. f. Drag the Cat5e Cable to the LAN port on the phone. g. In the Selected Component pane, drag the other connector to the Ethernet port on the wall outlet. h. On the Shelf, select the power adapter. i. In the Select Connector window, drag the DC power connector to the DC power connector on the phone. j. In the Selected Component pane, drag the AC power plug to the wall outlet. k. Above the IP phone, select Front to switch to the front view of the phone to confirm that it is on. 2. Connect the IP phone in the Executive Office to the network as follows: a. In the top navigation tabs, select Floor 1 Overview. b. Under Executive Office, select Hardware. c. On the Shelf, expand Phones. d. Drag the IP phone to the Workspace. e. Above the IP phone, select Back to switch to the back view of the phone. f. On the Shelf, expand Cables. g. Drag the Cat5e Cable to the LAN port on the phone. h. In the Selected Component pane, drag the other connector to the Ethernet port on the wall outlet. i. Above the workstation, select Back to switch to the back view of the workstation. j. Drag the Cat5e Cable to the PC port on the phone. k. In the Selected Component pane, drag the connector to the workstation's NIC. 3. Add a surge protector as follows: a. On the Shelf, expand Outlets. b. Drag the surge protector to the Workspace. c. Drag one or more of the AC power plugs from the wall outlet to an open outlet on the surge protector. d. Select the surge protector. e. In the Selected Component pane, drag the AC power plug to the open plug on the wall outlet. 4. Add a power adapter as follows: a. On the Shelf, expand Cables. b. Drag the power adapter to the DC power connector on the phone. c. In the Selected Component pane, drag the AC power plug to an open plug on the surge protector. d. Above the IP phone, select Front to switch to the front view of the phone. e. Confirm that the phone's display is on. 5. On the Exec monitor, select Click to view Windows 10. 6. In the notification area, right-click the network icon and select Open Network and Sharing Center. The diagram should indicate an active connection to the CorpNet.com network and the internet.

You work as the IT administrator for a small corporate network. You have two servers and a DNS server that use static IP addresses on the 192.168.0.0/24 subnet. You plan to install three more servers soon, so you need to create DNS records for these servers on the CorpDC server. In this lab, your task is to perform the following: Create an IPv4 Active Directory-integrated primary reverse lookup zone for subnet 192.168.0.0/24. Be sure to accept the default replication and dynamic updates settings. Create A records and PTR records for the following hosts:Host NameIP AddressCorpServer192.168.0.10CorpFiles16192.168.0.12CorpFiles12192.168.0.13CorpDHCP192.168.0.14CorpWeb192.168.0.15

1. Create a primary reverse lookup zone as follows: In Hyper-V Manager, select CORPSERVER. Right-click CorpDCand select Connect. In Server Manager, select Tools> DNS. Expand CORPDC. Right-click Reverse Lookup Zonesand select New Zone. Click Next. Make sure Primary zoneis selected. Make sure Store the zone in Active Directoryis selected and then click Next. Keep the default replication scope setting and click Next. Keep the default reverse lookup zone settings and click Next. Enter 168.0as the network ID. Omit any trailing zeroes that are excluded based on the subnet mask. For example, type 192.168.1 for subnet 192.168.1.0/24. Type 10.1 for subnet 10.1.0.0/16. Click Next. Keep the default dynamic update settings and then click Next. Click Finish. 2. Create a host (A) and associated pointer (PTR) record as follows: In DNS Manager, expand Forward Lookup Zones. Right-click comand 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) recordas needed. The reverse lookup zone must exist for this record to be created. Click Add Host. Click OK. Repeat steps 2c - 2g to add additional host records. Click Done.

Done Scenario You just installed the DHCP service on the CorpDHCP server. You configured two scopes. The scope for Building A, Subnet1, is configured on 192.168.0. The scope for Building B, Subnet2, is configured on 192.168.10. After activating the scopes, you find that clients on Subnet1 receive IP addressing information from the DHCP server, but clients on Subnet2 have IP addresses in the 169.254.0.0/16 range. You realize that DHCP messages are not being forwarded through the router. In this lab, your task is to complete the following: Use Routing and Remote Access to configure CorpServer2 as a DHCP relay agent by performing the following:Add the DHCP relay agent routing protocol.Add NetTeam as a DHCP relay agent interface.Set the boot threshold to 0.Configure the DHCP relay agent properties to identify 192.168.0.14 as the DHCP server. Renew the TCP/IP information on Exec2 (the client machine in Building B). Verify that Exec2 has a network connection.

Add the DHCP relay agent protocol as follows: From Server Manager, select Tools> Routing and Remote Access. From the left pane, expand IPv4. Right-click Generaland select New Routing Protocol. Select DHCP Relay Agent. Click OK. 2. Add and configure a relay agent interface as follows: From the left pane, right-click DHCP Relay Agentand select New Interface. Select NetTeam. Click OK. Make sure Relay DHCP packetsis selected. In the Boot threshold field, enter 0. Click OK. 3. Identify the DHCP server as follows: From the left pane, right-click DHCP Relay Agentand select Properties. In the Server address field, enter 168.0.14. Select Add. Click OK. 4. Renew the TCP/IP address as follows: From the location tabs at the top, select Building B. Under Building B, select Inside. Under Manager Office, select Exec2. In the Search the web and Windows field, enter commandand press Enter. In the command prompt, type ipconfig /renewand press Enter.The computer should receive an address on the 192.168.10 network. In the navigation area, select the Network icon to view the connection status and verify that CorpNet.com is connected

You have just authorized the CorpDHCP server to assign IP addresses to client workstations on the 192.168.10.0 subnet. Now you need to create an IPv4 scope on the CorpDHCP server for an address range on this subnet. In this lab, your task is to complete the following: On CorpDHCP, create an IPv4 scope using the following specifications and activate the new scope upon completion:IPv4 scope name: MySubnetAddress range: 192.168.10.21 to 192.168.10.199Default gateway: 192.168.10.5DNS Servers: 198.28.56.108 and 163.128.78.93

Complete this lab as follows: 1. Connect to the CorpDHCP as follows: In Server Manager, select Tools> Hyper-V Manager. In Hyper-V Manager, select CORPSERVER. Maximize the window for easier viewing. Under Virtual Machines, right-click on CorpDCHPand select Connect. 2. Create a scope as follows: In Server Manager, select Tools> DHCP. In the left pane, expand CorpNet.com. Right-click IPv4and select New Scope. Click Next. In the Name field, enter MySubnetand click Next. In the Start IP address field, enter 168.10.21. In the End IP address field, enter 168.10.199. Click Next. In the Add Exclusions and Delay dialog, click Next. In the Lease Duration dialog, click Next. Make sure Yes, I want to configure these options nowis selected and click Next. Under IP address, enter 168.10.5for the router (default gateway). Select Add. Click Next. Under IP address, enter 28.56.108for the DNS server. Select Add. Under IP address, enter 128.78.93for the second DNS Server. Select Add. Click Next. In the WINS Servers dialog, click Next.

You work as the IT security administrator for a small corporate network. You recently placed a web server in the DMZ. You need to configure the perimeter firewall on the network security appliance to allow access to the web server from the LAN and the WAN. You would also like to improve security by utilizing the attack security features provided by the firewall. In this lab, your task is to perform the following: Add an HTTP firewall rule that allows traffic from the WAN to the web server in the DMZ.ParameterSettingFrom ZoneUNSECURE (WAN)To ZoneDMZServiceHTTPActionAllow AlwaysSource HostsAnyInternal IP Address172.16.2.100External IP AddressDedicated WAN Add an HTTPS firewall rule that allows traffic from the WAN to the web server in the DMZ. Use the following table for the HTTP and HTTPS rules:ParameterSettingFrom ZoneUNSECURE (WAN)To ZoneDMZServiceHTTPSActionAllow AlwaysSource HostsAnyInternal IP Address172.16.2.100External IP AddressDedicated WAN Add a firewall rule to allow traffic from the LAN to the DMZ.ParameterSettingFrom ZoneSECURE (LAN)To ZoneDMZServiceAnyActionAllow AlwaysSource HostsAnyDestination HostsAny Enable all the firewall attack checks.

Configure the firewall as follows:From the top menu of the Security Appliance Configuration Utility, select Firewall.From the left pane, select IPv4 Rules.In the right pane, select Add.Modify the firewall rule parameters; then click Apply.Repeat steps 1c-1d for each firewall rule. Enable firewall attack checks as follows:From the left pane, select Attacks.Select all the WAN security checks.Select all the LAN security checks.Select all the ICSA settings; then click Apply.

You work as the IT security administrator for a small corporate network. You need to secure access to your network security appliance, which is still configured with the default user settings. In this lab, your task is to perform the following: Rename the default user account (cisco) with the following parameters:Use the user name xAdmin.Use the password Admin$0nly (0 = zero).Set the idle timeout to 15 minutes.Set for LAN access only (no WAN access).Allow access only from CorpServer (192.168.0.10). Create a new administrative user with the following parameters:Use the user name mbrown.Use the frst name Mary.Use the last name Brown.Set the user type to Administrator.Use the password St@y0ut! (0 = zero).Set the idle timeout to 15 minutes.Set for LAN access only (no WAN access).Allow access only from the administrator's workstation (192.168.0.21).

ExplanationIn this lab, your task is to perform the following:• Rename the default user account (cisco) with the following parameters:o User name: xAdmino Password: Admin$0nly (0 = zero)o Idle timeout: 15 minuteso Set for LAN access only (no WAN access)o Allow access only from CorpServer (192.168.0.10)• Create a new administrative user with the following parameters:o User name: mbrowno First name: Maryo Last name: Browno User type: Administratoro Password: St@y0ut! (0 = zero)o Idle timeout: 15 minuteso Set for LAN access only (no WAN access)o Allow access only from the administrator's workstation (192.168.0.21)Complete this lab as follows:1. Select Start.2. Select Windows Accessories.3. Select Internet Explorer.4. In the URL field, type 198.28.56.18 and press Enter.5. In the Username field, enter cisco.6. In the Password field, enter cisco to log in to the Security Appliance Configuration utility.7. Select Log In.8. Rename the default user account as follows:a. From the Getting Started (Basic) page, select Change Default Admin Password and Add Users.b. Select Edit for the cisco username.c. In the User Name field, enter the new username.d. Select Check to Edit Password.e. Enter the current logged in administrator password.f. Enter the new password.g. Re-enter the new password to confirm the new password.h. Enter the idle timeout; then click Apply.9. Create a new administrative user as follows:a. Select Add to add another user.b. In the User Name field, enter the username.c. Enter the first name.d. Enter the last name.e. From the User Type drop-down list, select Administrator.f. Enter the password.g. Re-enter the password to confirm the new password.h. Enter the idle timeout; then click Apply.10. Edit user policies as follows:a. Under Edit User Policies, select Login to configure a login policy.b. Select Deny Login from WAN Interface; then click Apply.c. Repeat steps 10a-10b for the other user.11. Define network access as follows:a. Under Edit User Policies, select By IP to configure IP address restrictions for login.b. Select Add.c. In the Source Address Type field, make sure IP Address is selected.d. In the Network Address/IP Address field, enter the appropriate IP address; then click Apply.e. Select Allow Login only from Defined Addresses.f. Click Apply to close the dialog.g. Repeat steps 11a-11f for the other user.

You have several printers on Subnet1 that need static IP addresses assigned. In this lab, your task is to configure the CorpDHCP server so that these machines always get the same IP addresses. Additionally, configure each reservation for DHCP only. Use the values in the table below to configure the reservations. Reservation NameIP AddressMAC AddressLaserJet4240-1192.168.0.101aa-61-82-df-04-54LaserJet4240-2192.168.0.102ce-fd-48-90-06-23KonicaColor192.168.0.103c8-ba-99-cd-80-12AcctPrinter192.168.0.104f1-a9-3e-f7-7d-3bSalesPrinter192.168.0.105df-a9-99-cd-80-61

From Hyper-V Manager, select CORPSERVER. Expand the window to view all virtual machines. Right-click CorpDCHPand select Connect. From Server Manager, select Tools> DHCP. In the left pane, expand CorpNet.com. Expand the IPv4 Expand the Scope Right-click Reservationsand select New Reservation. In the Reservation name field, enter a reservation name(such as the computer name). In the IP address field, enter the IP address. In the MAC address field, enter the MAC address. For Ethernet, the MAC address will look like c8ba99cd8012or c8-ba-99-cd-80-12. Under Supported types, select DHCP onlyas needed. Select Addto create the client reservation. Repeat steps 9- 13 for additional reservations. Select Close.

Scenario You have just configured a scope on the CorpDHCP server to service the 192.168.0.0/24 subnet. You defined a scope to distribute IP addresses between 192.168.0.1 and 192.168.0.254. Now you need to prevent the DHCP server from assigning addresses to the servers and network devices. Create an exclusion range to exclude addresses 192.168.0.1 to 192.168.0.29

From Hyper-V Manager, select CORPSERVER. Expand the window to view all virtual machines. Right-click CorpDCHPand select Connect. From Server Manager, select Tools> DHCP. In the left pane, expand CorpNet.com. Expand the IPv4 Expand the Scope Right-click the Address Poolnode and select New Exclusion Range. In the Start IP address field, enter the starting IP address. In the End IP address field, enter the ending IP address. Click Add. Click Closeto close the Add Exclusion Range dialog.

You work as the IT administrator for a growing corporate network. You need to create a storage area network (SAN). Management would like you to use standard Ethernet hardware to lower the cost of the SAN implementation. In this lab, your task is to create an iSCSI virtual disk on CorpiSCSI using the following settings: Use space on Volume D:. Name the disk iSCSIDisk1. Set the size to 5 TB. Set the disk type to Dynamically expanding. Assign a new iSCSI Target called iSCSITarget1. Specify CorpFiles16 as an iSCSI initiator server with access to the virtual disk.

In the left pane of Server Manager, select File and Storage Services.Select iSCSI.In the iSCSI VIRTUAL DISKS panel, select Tasks > New iSCSI Virtual Disk.Under Server, make sure CorpiSCSI is selected.Under Select by volume, select D: then select Next.In the Name field, enter a name for the virtual disk; then click Next.In the Size field, enter the size for the virtual disk.Make sure Dynamically expanding is selected; then click Next.Select New iSCSI Target; then select Next.In the Name field, enter a name for the iSCSI target; then click Next.Specify the access servers as follows:Select Add.Make sure Query initiator computer for ID is selected.Select Browse to locate the server that will be allowed to access the iSCSI disk.In the Enter the object names to select field, enter the server name; then click OK.Click OK.Click Next.Click Next.Click Create.Click Close.To view the iSCSI virtual disk and target you just created, expand the Server Manger window.

Your network has two distribution-layer switches, SwitchA and SwitchB, connected through trunk ports on each of their respective Gi0/1 interfaces. In addition, you recently connected an Access layer switch to the network, SwitchC. Each switch is forwarding the network's traffic for VLANs 10 and 110 using 802.1Q encapsulation. You need to change the native VLAN from the default to VLAN 10 for each trunk link. With 802.1Q trunking, frames from the native VLAN are not tagged. Frames from all other VLANs are tagged. If the native VLAN on one end of the trunk is different from the native VLAN on the other end, the traffic of the native VLANs on both sides cannot be transmitted on the trunk correctly. The native VLAN is VLAN 1 by default, but may be configured. In this lab, your task is to complete the following: On each switch, change the native VLAN from its default to VLAN 10 for each trunk port. Save changes to the startup-config file for each switch.

In this lab, your task is to complete the following: On each switch, change the native VLAN from its default to VLAN 10 for each trunk port. Save changes to the startup-config file for each switch. Complete the following on each switch: Select the switch. Press Enter. At the prompt, enter:SwitchA>enaSwitchA#conf tSwitchA(config)#int range gi 0/1 - 2SwitchA(config-if-range)#switchport trunk native vlan 10 Press Ctrl + Z. At the prompt, enter:SwitchC#copy run start Press Enter. Press Enter to save your changes. Repeat steps 1-7 for each switch.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignment. The employee in Office 1 reports that his workstation can communicate with some computers on the network, but not on the internet. You need to diagnose and fix the problem. In this lab, your task is to complete the following: Use the following troubleshooting tools to diagnose the problem in the network:The ping, ipconfig, or tracert command utilityThe Network and Sharing Center in the Windows 10 or Windows Server 2016 operating systemThe DHCP server console in the Windows Server 2016 operating system Fix the problem at the workstation, the DHCP server, or both as necessary. Use the troubleshooting tools to confirm that the problem is resolved.

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

You are in the process of configuring the switch ports on the Branch1 switch. Devices are currently attached to the switch as shown in the diagram. In this lab, your task is to complete the following: You will be adding an older server to switch port Fa0/6 that uses 10BaseT Ethernet. Manually configure the switch port to use 10 Mbps. Use the speed command to manually set the port speed. You will be adding a hub to switch port Fa0/7 that will be used for a lab for developers. Manually configure the switch port to use half-duplex communications. Use the duplex command to set the duplex. Make sure that ports Fa0/6 and Fa0/7 are enabled and can be used. Be aware that you have not yet connected devices to those ports. Disable all unused interfaces using the shutdown command.Fa0/4 and Fa0/5Fa0/8 through Fa0/23Gi0/1 and Gi0/2Use the interface range command to enter configuration mode for multiple ports at a time. Verify that all remaining ports being used are enabled and configured to automatically detect speed and duplex settings. Use the show interface status command to check the configuration of all ports from a single list. Use this output to verify that all other ports have the correct speed, duplex, and shutdown settings. Modify the configuration to correct any problems you find. When you are finished, all ports should have the following settings: InterfacesStatusDuplexSpeedFastEthernet0/1-3FastEthernet0/24Not shut downAutoAutoFastEthernet0/6Not shut downAuto10 MbpsFastEthernet0/7Not shut downHalfAutoFastEthernet0/4-5FastEthernet0/8-23GigabitEthernet0/1-2Administratively downHalfAuto Use the necessary show commands to review the existing configuration and correct any problems that you find.

Press Enter. At the prompt, enter:Branch1>enableBranch1#configure terminalBranch1(config)#interface FastEthernet0/6Branch1(config-if)#speed 10Branch1(config-if)#interface FastEthernet0/7Branch1(config-if)#duplex halfBranch1(config-if)#interface range FastEthernet0/4-5, FastEthernet0/8-23, GigabitEthernet0/1-2Branch1(config-if-range)#shutdown Press Ctrl + Z. At the prompt, enter: Branch1#show interface status Verify the port configuration of all ports, and then use the necessary commands to correct any problems you find. For example, notice that Fa0/24 is administratively down. Also notice that Fa0/2 is not configured to use auto speed and Fa/03 is not configured to use auto duplex. At the prompt, enter: Branch1#configure terminalBranch1(config)#interface FastEthernet0/24Branch1(config-if)#no shutdownBranch1(config-if)#interface FastEthernet0/2Branch1(config-if)#speed autoBranch1(config-if)#interface FastEthernet0/3Branch1(config-if)#duplex auto Press Ctrl + Z. Run show interface status again to verify your configuration changes. At the prompt, enter: Branch1#copy run start Press Enter. Press Enter to save your changes.

You have created redundant paths between 4 switches. You want to manually determine which switch will serve as the primary root bridge and which will become the root bridge if the primary root bridge fails. The switches have the following MAC addresses: Switch MAC Address SwitchA 00C0.1940.8B80 SwitchB 000E.8411.6800 Switchc 00B0.64FA.C265 SwitchD 0019.E744.7400 Complete the following tasks: • Configure Switchc to be the primary root bridge for VLAN 1. • Configure SwitchA to be the secondary root bridge for VLAN 1 if Switch fails. • Save your changes to the startup-config file on each switch.

Press Enter. At the prompt, enter:SwitchA>ena SwitchA#conf tSwitchA(config) #spanning-tree vlan 1 priority 4096SwitchA(config) #exitSwitchA #copy running-config startup-config Press Enter.

You recently installed a new switch. In the future, you would like to manage the switch from a remote location. To remotely manage the switch, complete the following configuration tasks: Configure the VLAN 1 interface with the IP address 192.168.11.250 and a mask of 255.255.255.0. Configure the switch to use 192.168.11.254 as the default gateway. Save your changes to the startup-config file.

Select Switch. Press Enter. At the prompt, enter:Switch>enableSwitch#configure terminalSwitch(config)#interface Vlan1Switch(config-if)#ip address 192.168.11.250 255.255.255.0Switch(config-if)#exitSwitch(config)#ip default-gateway 192.168.11.254Switch(config)#exitSwitch#copy run start Press Enter. Press Enter to save your changes.

The sales department wants to create an intranet for all sales employees. Internet Information Services (IIS) is installed on CorpWeb and will be used to host the intranet site. Employees need the ability to access the web server using any of the following URLs:http://sales.privatehttp://intranet.sales.privatehttp://www.sales.privateYou created the sales.private zone on the CorpDC server. Now you need to allow clients to connect to the web server by creating DNS records in the zone. Use CorpWeb.CorpNet.com as the fully qualified domain name.In this lab, your task is to:Create an ALIAS (CNAME) record and leave the name blank. (This allows users to connect to the server using the sales.private URL)Create an ALIAS (CNAME) record named intranetCreate an ALIAS (CNAME) record named www

The sales department wants to create an intranet for all sales employees. Internet Information Services (IIS) is installed on CorpWeb and will be used to host the intranet site. Employees need the ability to access the web server using any of the following URLs:http://sales.privatehttp://intranet.sales.privatehttp://www.sales.privateYou created the sales.private zone on the CorpDC server. Now you need to allow clients to connect to the web server by creating DNS records in the zone. Use CorpWeb.CorpNet.com as the fully qualified domain name.In this lab, your task is to:Create an ALIAS (CNAME) record and leave the name blank. (This allows users to connect to the server using the sales.private URL)Create an ALIAS (CNAME) record named intranetCreate an ALIAS (CNAME) record named www

You work as the IT administrator for a small corporate network. The receptionist, Maggie Brown, uses an iPad to manage employee schedules and messages. Her email settings on the device are configured to communicate with an IMAP mail server over insecure port 143. Maggie also needs to use the new password to connect to the wireless network named CorpNet. In this lab, your task is to complete the following: Use the Accounts and Passwords option to go to Maggie Brown's email account settings and change the advanced configuration to Use SSL to securely communicate with the IMAP server over server port 993. Connect Maggie to the CorpNet access point through the Wi-Fi configuration using @CorpNetWeRSecure!& as the password.

Use the Accounts and Passwords option to go to Maggie Brown's email account settings and change the advanced configuration to Use SSL to securely communicate with the IMAP server over server port 993. Connect Maggie to the CorpNet access point through the Wi-Fi configuration using @CorpNetWeRSecure!& as the password.

You have two routers connected as shown in the network diagram. Router Jujuy has already been configured to share route information using OSPF on area 0. All interfaces have been configured and enabled. The actual network statement you use does not have to match the subnet address on an interface. Instead, the network statement and mask must include the subnet address. For example, to enable OSPF on the Fa0/0 interface, you could have used any of the following statements: network 192.168.1.0 0.0.0.255 area 0 network 192.168.0.0 0.0.255.255 area 0 network 192.0.0.0 0.255.255.255 area 0 network 0.0.0.0 255.255.255.255 area 0 In this lab, your task is to complete the following: Configure the Salta router to share information about all directly connected routes with the Jujuy router. When you are finished, save your changes.

When configuring OSPF, routers do not need to use the same process ID, but networks must be defined in the same area.When adding network statements, include the wildcard mask and the area number (in this case area 0).Use the following commands:Press EnterSalta>enableSalta#config tSalta(config)#router ospf 100Salta(config-router)#network 192.168.1.0 0.0.0.255 area 0Salta(config-router)#network 192.168.2.0 0.0.0.255 area 0Salta(config-router)#network 172.17.150.140 0.0.0.3 area 0(Press Ctrl + Z)Salta#copy running-config startup-configPress EnterThe actual network statement you use does not have to match the subnet address on an interface. Instead, thenetwork statement and mask must include the subnet address. For example, to enable OSPF on the Fa0/0 interface,you could have used any of the following statements:network 192.168.1.0 0.0.0.255 area 0network 192.168.0.0 0.0.255.255 area 0network 192.0.0.0 0.255.255.255 area 0network 0.0.0.0 255.255.255.255 area 0

You have redundant paths between three switches, and you would like to configure Rapid PVST+ on each switch and the root bridge for VLAN 1. The switches have the following MAC addresses: SwitchMAC AddressSwitchA00C0.1940.8B80SwitchB000E.8411.68C0SwitchC00B0.64FA.C265 In this lab, your task is to complete the following: Configure each switch to use Rapid PVST+. Configure SwitchC to be the root bridge for VLAN 1. Save your changes to the startup-config file on each switch. Each switch has the default spanning tree configurations. After applying the correct configuration, SwitchC's Fa 0/1 and Fa 0/2 interfaces will be in the designated state. Use the show spanning-tree vlan 1 command to verify the configuration.

switchC> enconf tspanning-tree mode rapid-pvstspanning-tree vlan 1 priority 4096exitcopy run startSwitchA>enconf tspanning-tree vlan 1 priority 8192endcopy run start