Troubleshoot IP Configuration Problems 2
Lab Report: 5.8.7 Troubleshoot IP Configuration Problems 2
- In the Networking Closet, activate the DHCP scope for the local network
- Verify that the Executive Office and IT Administrator workstations can communicate with the Internet
Following is one way to troubleshoot this problem:
1. In the Executive Office, begin troubleshooting the problem by verifying the scope of the connectivity problem.From the workstation, ping the computer in the Networking Closet and ping the Internet Service Provider (ISP)(The ping to both locations fails).
2. In the IT Administrator office, verify the connectivity problem between the workstation the Networking Closetcomputer and the ISP. (The ping to both locations fails). The problem most likely is related to the IPconfiguration for the network.
3. In the Executive Office, open the command prompt and use the ipconfig /all command to check the Local AreaConnection configuration. You should notice the following problems:
- The default gateway and DNS server addresses have not been configured on the workstation. This meansthat 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 theDHCP server.
- The IP address is in the APIPA range (169.254.0.1 to 169.254.255.254). This means that the workstationassigned itself an IP address. The workstation will be able to communicate with other hosts on the localnetwork that have also configured their own IP address through APIPA.
4. In the Networking Closet, confirm that the DHCP service is enabled and activated for the local network.
- In Hyper-V Manager, click CORPSERVER. Expand the window to view all virtual machines.
- Right-click the CorpDHCP12 server and click Connect (maximize the window for easier viewing ifdesired).
- In Server Manager, click Tools > DHCP to start the DHCP console.
- Expand the node for the DHCP server, and then browse to and expand the IPv4 protocol. The downarrow for Scope [192.168.0.1] Subnet1 indicates that the scope is not active.
- Right-click Scope [192.168.0.1] Subnet1 and click Activate. The down arrow for the scope is gone andthe DHCP service for the local network is now active.
5. In the Executive Office, issue the ipconfig /renew command. This will request the new IP address informationfrom the DHCP server, and it will reconfigure the settings for the Local Area Connection.
6. In the Executive Office, use the ipconfig /all command to check the Local Area Connection configuration. Youshould notice the line for the default gateway, DNS server, and DHCP server are now configured, along with anew IP address within the DHCP scope for the local network.
7. In the Executive Office, confirm the resolution of the problem by pinging the ISP. The ping to the ISP succeeds.
8. In the IT Administrator Office, repeat step 5 to fix the problem for that workstation.