Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Pinging 172.16.3.1 with 32 bytes of data: Step 1: Communicate with the default gateway. In this Part, you will test connectivity to the next network device, R3, to continue troubleshooting.
You now have the correct information to get to the default gateway. Click the radio button next to Static to assign the interface IP Configuration information:.Because PC-B cannot reach a DHCP server, you will need to provide static IP address information. You should be provided with an IP address if there is a DHCP server on the network.Notice the icons between PC-B and S3 turn green after a few seconds to indicate communication between the two devices. Click On next to Port Status to enable the interface. This means that, most likely, either the E thernet port on PC-B or S3 is not enabled. Minimum = 3ms, Maximum = 16ms, Average = 6msīecause there were successful replies, we know that TCP/IP is installed and working correctly. Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Īpproximate round trip times in milli-seconds: Ping the loopback address to ensure that TCP/IP is installed and working properly.Begin by troubleshooting t he protocol stack first. This means that the connection is physically down between the two or TCP/IP is not correctly configured on PC-B. In the Packet T racer work area, you can see that the connection between PC-B and S3 has red icons. Step 2: Troubleshoot the basic configuration of PC-B. We will begin troubleshooting from PC-B and work our way over to the server, troubleshooting along the way. There may be one or many different problems between PC-B and the server. Step 1: Test the connectivity of the network.
In this Part, y ou are on PC-B, trying to reach the web page of the DEVASC Server. In the topology, they are named with their URL: and. Note : In this activity, the two web servers are referred to as DEVASC Server and Example Server. You may often find more than one problem preventing a connection from working. To troubleshoot network issues, it is necessary to take a step-by-step methodical approach, using clues to determine the problem and implement a solution. As a developer, you may need to troubleshoot network issues to regain connectivity. This may be due to a simple device misconfiguration, or many, seemingly unrelated problems that must be systematically resolved. Often, these components may not work properly. Networks have a lot of components working together to ensure connectivity and data delivery. Part 4: Troubleshoot DNS Background / Scenario