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 utility
-the network and sharing center in the windows 10 or windows server 2016 operating system
-the DHCP server console in the windows server 2016 operating system

The first thing that you should do would be to ping the computer in the Networking Closet, if this fails then the next step would be to ping the service provider. If both of these pings fail it is most likely because the configuration of the IP addresses are configured wrong. In this case use the command prompt to type in the following

ipconfig /all

this will open up the entire configuration info. If the problem is truly the configuration then your DNS address should show up as not configured. This can happen when a DHCP is enabled. Check if DHCP is enabled, if so then you would need to type the following into the command prompt

ipconfig /renew

This will renew the ip address information from the DHCP server and should create the proper DNS configuration as well and solve the issue.

codiepienagoya codiepienagoya · Answer 2 · 2021-12-08T10:14:45+01:00

Following are the solution to the given question:

Initiate troubleshooting in the Executive by exploring the scope of the connectivity issue. Ping the laptop in the network closet from your workstation. A ping to a location failed.
Ping your internet service provider. The ping to the address fails.
Verify any connection issues here between workstations, the Network Closet computer, and also the ISP in the IT Administrator's office. (Pings to both locations failed.) The issue is now almost definitely due to the channel's IP setup.
To examine the Local Area Connection setup, open the cmd in the Executive Office and type ipconfig /all. Some of the following issues must be noted: The workstation's default route and DNS server addresses have still not been configured.
It implies that connectivity is confined to computers just on the local network.
Its DHCP Enabled option has been enabled. Yes, a DHCP server is configured just on the workstation. Its line with the DHCP Server address wasn't shown. This means the workstation was unable to communicate with the DHCP server. This IP address corresponds to an APIPA domain (169.254.0.1 to 169.254.255.254). It shows that the computer assigns an IP address to it only. The workstation would be capable of communicating with the other hosts on the local network who have given their unique IP via APIPA.
Verify that its DHCP service for the local area network is active and active in the Network Closet.
CORPSERVER should be the first option in Hyper-V Manager. To see all the virtual machines, open the window. Join by correcting CorpDHCP (maximize the window for easier viewing if desired). For launch, the DHCP console in Server Manager, go to Tools > DHCP. CorpDHCP.CorpNet.com must be extended. IPv4 enlargement.
Scope [192.168.0.1] Subnet1 has a dropdown, suggesting that this is not operational. Select Activate from the menu bar of Scope [192.168.0.1] Subnet1. The scope's "dislike" button has gone, and the DHCP service for the local network is now operational.
Launch the command prompt inside the Executive and type ipconfig /renew. This will obtain the new Ip from the DHCP server and change the Ethernet connection settings.
To check the Internet setup, type ipconfig /all. You should now see lines for the default gateway, DNS server, and DHCP server, and a new IP address in the DHCP scope for the local network.
Ping the ISP in the Executive Office to confirm that the problem has been resolved. Your ping to the ISP is good.
Rep step 6 in the IT Administrator Office to fix the dispute with the workstations.

Learn more:

brainly.com/question/14728944