yulia_zoNe

Lab 9.2.7 Troubleshooting Using Network Utilities
Objectives

• Use network utilities and the integrated router GUI to determine device configurations.
• Select the appropriate network utilities to help troubleshoot connectivity problems.
• Diagnose accessibility problems with Web, FTP, Telnet, and DNS servers.
• Identify and correct physical problems related to cable types and connections.

Background / Preparation
In this lab, you use the browser and various troubleshooting utilities, such as ipconfig, ping, tracert, netstat, and nslookup to diagnose and correct connectivity problems. These command line interface (CLI) utilities are available on most current operating systems, although the exact command and syntax may vary. Windows XP commands and syntax are used in this lab.
Your instructor will set up the network topology similar to the one shown here and will preconfigure the client computer, integrated router, server, and external router for each scenario in the lab. Various software and hardware connectivity problems will be introduced, and you will diagnose the cause from the client computer.
There are six scenarios. Work in teams of three, with each person taking the lead in two of the scenarios, and the other team members assisting.
The following resources are required:

• Computer running Windows XP Professional with Web, FTP, and Telnet clients (CLI or GUI).
• Server running a combination of DNS, HTTP, FTP, and Telnet services (preconfigured). This server will simulate Internet connections and can be a server with these services actually installed and running or a server running the Discovery Live CD.
• Integrated router configured as a DHCP server and client (default configuration).
• Router with two Ethernet interfaces configured as a DHCP server to integrated router (preconfigured).
• Ethernet Cat-5 (minimum) straight and crossover cabling to connect hosts and network devices.

Step 1: Build the network and configure the hosts

1. Have your instructor set up a network topology similar to the one shown with the Host-A client computer, integrated router, server, and router preconfigured.
2. Work from Host-A to issue commands to troubleshoot problems introduced by the instructor.
3. All commands are issued from a command prompt window. Open a command prompt window by clicking Start > All Programs > Accessories > Command Prompt. Keep the window open for the duration of the lab.

Step 2: Record the baseline IP address information for computers and integrated router
NOTE: Perform this step before the instructor introduces problems.

1. Host-A configuration—Issue the command that displays the IP address information for Host-A, including the DNS server, and record the information below. Which command did you use?

IP address: 192.168.10.2
Subnet mask: 255.255.255.0
Default gateway IP address: 192.168.10.1
DNS server IP address:
DHCP server IP address:
How did Host-A obtain its IP address?

1. Integrated router configuration—From Host-A, open a browser and go to the integrated router GUI by entering 192.168.1.1 as the URL address. Log in to the integrated router using the default user ID and password (check with your instructor if necessary). Check the internal and external IP address information and record it below.

Internal IP address: 192.168.10.3
Subnet mask: 255.255.255.0
Is the DHCP server enabled?
Ya, DHCP servernya enabled.
External (Internet) IP address: 10.1.1.5
Subnet mask: 255.255.255.0
Default gateway IP address: 10.1.1.1
DNS server IP address:
Server configuration—Obtain the Server IP configuration from your instructor and record the information below.
IP address: 192.168.4.2
Subnet mask: 255.255.255.0
Default gateway IP address: 192.168.4.1
Web Server 1 protocol and name:
Web Server 2 protocol and name:
FTP Server 1 protocol and name:
FTP Server 2 protocol and name:
Step 3: Scenario 1—Diagnose Web server access

1. After your instructor sets up the problem for this scenario, use various utilities to diagnose the problem.
2. Open your browser and enter the name of the Web Server 1 from Step 2. What happened?
3. Which commands did you use to diagnose the problem?
4. Report the problem or suspected problem to the instructor. What was the problem?
5. What did you do to correct the problem, if anything?
6. You may need to contact the instructor to correct the problem. When the problem is corrected, retest and verify access to the server.

Step 4: Scenario 2—Diagnose Web server access

1. After your instructor sets up the problem for this scenario, use various utilities to diagnose the problem.
2. Open your browser and enter the name of the Web Server 2 from Step 2. What happened?
3. Which commands did you use to diagnose the problem?
4. Report the problem or suspected problem to the instructor. What was the problem?
5. What did you do to correct the problem, if anything?
6. You may need to contact the instructor to correct the problem. When the problem is corrected, retest and verify access to the server.

Step 5: Scenario 3—Diagnose FTP server access

1. After your instructor sets up the problem for scenario, use various utilities to diagnose the problem.
2. Use your FTP client (CLI or GUI) to connect to FTP Server 1 from Step 2. What happened?
3. Which commands did you use to diagnose the problem?

1. Report the problem or suspected problem to the instructor. What was the problem?
2. What did you do to correct the problem, if anything?

1. You may need to contact the instructor to correct the problem. When the problem is corrected, retest and verify access to the server.

Step 6: Scenario 4—Diagnose FTP server access

1. After your instructor sets up the problem for this scenario, use various utilities to diagnose the problem.
2. Use your FTP client (CLI or GUI) to connect to FTP Server 2 from Step 2. What happened?
3. Which commands did you use to diagnose the problem?
4. Report the problem or suspected problem to the instructor. What was the problem?
5. What did you do to correct the problem, if anything?
6. You may need to contact the instructor to correct the problem. When the problem is corrected, retest and verify access to the server.

Step 7: Scenario 5—Diagnose Telnet server access problem

1. After your instructor sets up the problem for this scenario, use various utilities to diagnose the problem.
2. Use a Telnet client (CLI or GUI) to connect to the name of Server 1 identified in Step 2. What happened? Which commands did you use to diagnose the problem?
3. Report the problem or suspected problem to the instructor. What was the problem?
4. What did you do to correct the problem, if anything?
5. You may need to contact the instructor to correct the problem. When the problem is corrected, retest and verify access to the server.

Step 8: Scenario 6—Analyze TCP connections to Host-A

1. Ask your instructor to verify that all problems introduced with the lab setup have been corrected. Using the appropriate clients, connect to the Web, FTP, and Telnet servers simultaneously from Host-A.
2. From the command line, issue a command to display the current active TCP connections to Host-A with names of the servers and protocols. Which command did you use?
3. Which named connections did you see?
4. From the command line, issue a command to display the current active TCP connections to Host-A with IP addresses and protocol port numbers. Which command did you use?
5. Which IP addresses and port numbers did you see?
6. From the command line, issue a command to display the current active TCP connections to Host-A, along with the program that created the connection. Which command did you use?
7. Which program executable (filename with an .exe extension) is listed for each of the connections?

Step 9: Reflection

1. When troubleshooting the problem scenarios during this lab, which troubleshooting technique did you use primarily (top-down, bottom-up, or divide and conquer)?

Jawab:
Divide and conquer

1. Which utility or command do you feel was the most useful for network troubleshooting?

Jawab:
Divide and conquer
Lab 9.3.3 Troubleshooting Physical Connectivity
Objectives

• Examine device LEDs to determine proper Ethernet connectivity.
• Select the correct Ethernet cable for use between various types of devices.
• Visually inspect cables for potential problems.
• Use a cable tester to help identify cabling problems.

Background / Preparation
Physical cabling is one of the most common sources of network problems. This lab focuses on connectivity issues related to network cabling. You will visually inspect cabling and LED link lights to evaluate physical connections and to determine if the correct type of cable is being used based on the devices they interconnect. You will also use a cable tester to identify problems with cables.
The instructor will set up the network topology similar to the one shown and will preconfigure the hosts and network devices. The instructor will introduce various connectivity problems, and you will diagnose the cause of these problems by inspecting link lights and testing cables between devices. Various cable types, both good and bad, will be used to interconnect devices for each scenario in the lab.
Work in teams of two, with each person taking the lead in half of the problem scenarios.
The following resources are required:

• Computer running Windows XP Professional (preconfigured)
• Server (preconfigured)
• Integrated router configured as a DHCP server and client (default configuration)
• Router with two Ethernet interfaces configured as the DHCP server to integrated router (preconfigured)
• Mix of Ethernet Cat-5 (minimum) straight-through and crossover cabling, both good and bad, to connect hosts and network devices
• Basic Cat-5 Ethernet cable tester (RJ-45 pin-to-pin continuity checker)
• Advanced cable tester (optional), such as Fluke 620 (or similar)

Step 1: Build the network and configure the hosts

1. Ask your instructor to set up a network topology similar to the one shown with a preconfigured Host-A client computer, integrated router, server, and router. Initially, correct and properly functioning cabling is used so that end-to-end connectivity can be verified. The instructor then introduces cabling problems in each scenario.
2. Problems can consist of using the wrong type of` cable between two devices (straight-through or crossover) or using a defective cable (miswired or improperly terminated). Observe device interface link lights, visually inspect cables, and use a cable tester to determine the problems.
3. Complete steps 2 and 3 of this lab before the instructor introduces problems.

Step 2: Record the correct cable types used between devices

1. Refer to the topology diagram and record the cable type that should be used (straight-through or crossover) based on the devices being connected. Have your instructor verify this information before proceeding.
2. Which type of cable should be used from Host-A to the integrated router?
3. Which type of cable should be used from the integrated router (router portion) to Hub/Switch?
4. Which type of cable should be used from Hub/Switch to Router?
5. Which type of cable should be used from Router to Server?

Step 3: Record the IP address information for the computers

1. Use the ipconfig command, or get the IP address of Host-A from your instructor, and record it here.

Host-A IP address:

1. Get the server IP address from your instructor and record it here.

Server IP address:

1. Before starting on problem scenarios, verify end-to-end connectivity by pinging from Host-A to Server. If you do not get a reply from the server, check with your instructor. There may be a problem with the initial hardware or software setup.

Step 4: Scenario 1

1. After your instructor sets up the problem, use visual inspection and a cable tester to isolate the problem.
2. Ping from Host-A to Server. What happened?
3. Check the LED link lights on the various device interfaces. Write down any that are not lit.
4. Disconnect and inspect the cable connecting the network interfaces that were not lit. Describe the problem and how you were able to identify it.
5. What did you do to correct the problem?
6. When the problem is corrected, retest and verify end-to-end connectivity by pinging from Host-A to Server. Was the ping successful?

Step 5: Scenario 2

1. After your instructor sets up the problem, use visual inspection and a cable tester to isolate the problem.
2. Ping from Host-A to Server. What happened?
3. Check the LED link lights on the various device interfaces. Write down any that are not lit.
4. Disconnect and inspect the cable connecting the network interfaces that were not lit. Describe the problem and how you were able to identify it.
5. What did you do to correct the problem?
6. When the problem is corrected, retest and verify end-to-end connectivity by pinging from Host-A to Server. Was the ping successful?

Step 6: Scenario 3

1. After your instructor sets up the problem, use visual inspection and a cable tester to isolate the problem.
2. Ping from Host-A to Server. What happened?
3. Check the LED link lights on the various device interfaces. Write down any that are not lit.
4. Disconnect and inspect the cable connecting the network interfaces that were not lit. Describe the problem and how you were able to identify it.
5. What did you do to correct the problem?
6. When the problem is corrected, retest and verify end-to-end connectivity by pinging from Host-A to Server. Was the ping successful?

Step 7: Scenario 4

1. After your instructor sets up the problem, use visual inspection and a cable tester to isolate the problem.
2. Ping from Host-A to Server. What happened?
3. Check the LED link lights on the various device interfaces. Write down any that are not lit.
4. Disconnect and inspect the cable connecting the network interfaces that were not lit. Describe the problem and how you were able to identify it.
5. What did you do to correct the problem?
6. When the problem is corrected, retest and verify end-to-end connectivity by pinging from Host-A to Server. Was the ping successful?

Step 8: Reflection

1. What are some general rules to help you determine which type of Ethernet cable (straight-through or crossover) to use to connect different types of network hosts and devices?
2. Which types of problems can a cable tester detect that might not be determined by visual inspection?