khse.vlab.elementk.com vlab content manager print all

Lab: USING WINDOWS APPLICATIONS AS NETWORK TOOLS

Lab Summary

Lab Summary

Lab Scenario

Scenario

Launching Your Lab Quick Start Instructions Assignment Story Conditions Notes Diagram

Launching Your Lab

The Status of your Lab is displayed at the top of the left navigation column. Click the Start Lab Now button. A progress bar displays while the lab is being initialized. During this time you can view items under the Content area of the left navigation bar.

When Initialization is complete the Status changes to In Progress. The clock starts and a lab diagram displays in the main content area. Click on the diagram that appears and your virtual lab experience will begin.

If your connection isn't working, verify connectivity by clicking Verify Connection in the Tools section on the left navigation bar.

Quick Start Instructions

Once a lab has finished initializing, click on the Sample Solution link if one is available. For performance based labs, Sample Solution will not be available. IT IS IMPORTANT TO WAIT UNTIL AFTER INITIALIZATION BEFORE GOING TO THE SAMPLE SOLUTION. The reason is that during initialization, you are assigned custom IP addresses that are dynamically added to your lab instructions. This makes the lab easier to follow than the traditional method of trying to look up pod-specific information in tables. After initialization, the Sample Solution will have the correct information for your gear. To console into the routers and switches mentioned in the lab steps, click on the network diagram shown on the main page. Once you have completed a lab, if you have additional time and wish to take it again, go to the Device Controls link and click on Reload. When the devices are ready, you can start the lab again.

Print this page

vLab Title 336300 USING WINDOWS APPLICATIONS AS NETWORK TOOLSSkills By completing these labs, you will be able to:

Use ipconfig to determine Windows IP settings. Verify Windows network settings. Confirm connectivity with the ping command. Run debugs on Cisco routers. Verify a 3-way TCP handshake using debug commands. Verify DNS settings on a Windows PC. View a routing path using the tracert command.

Level Of Difficulty BasicCourse ICND1 Lab Length 60 minutesCertification CCENT Desired Learner Outcome You will gain the skills required for the practical portion of the CCENT

certification and will be able to configure small Cisco networks.Desired Network Outcome Working through these labs, you will gain hands-on experience and

practice in implementing and operating a simple Cisco network that includes real switches, routers, and remote access technologies.

DependenciesAuthor Trey McMahon Vendor

Network Type Cisco SPV2Technology CiscoReferences ICND1

Cisco Systems, Interconnecting Cisco Network Devices 1, Cisco Systems, Inc., Cisco authorized courseware for CCNA certification. James Boney, Cisco IOS In a Nutshell, O'Reilly, A Desktop Quick Reference for IOS on IP Networks

of 11Print All

10/10/2011http://khse.vlab.elementk.com/vlab/contentManagerPrintAll.vlab

Assignment

Gain skills required for the practical portion of the CCENT certification: Once a lab is finished initializing, click on the Sample Solution link. IT IS IMPORTANT TO WAIT UNTIL AFTER INITIALIZATION BEFORE GOING TO THE SAMPLE SOLUTION. The reason is that during initialization, you are assigned custom IP addresses that are dynamically added to your lab instructions. This makes the lab easier to follow than the traditional method of trying to look up pod-specific information in tables. After initialization, the Sample Solution will have the correct information for your gear. To console into the routers and switches mentioned in the lab steps, click on the network diagram shown on the main page. Once you have completed a lab, if you have additional time and wish to take it again, go to the Device Controls link and click on Reload. When the devices are ready, you can start the lab again. This content also applies to: ICND1

Story

N/A

Conditions

The devices in blue on the diagram are the routers and switches that you have control over. The devices in green are core devices with fixed configurations which play the role of the service provider. All of the devices that you access through vLab are real Cisco routers and switches. Nothing is simulated.

Notes

After taking a vLab for the first time using the Sample Solution, try the Suggested Approach link for a challenge. You've got a number of tools available on the left bar of the main page to aid you in your lab. Here are brief notes on each. Summary: lab length, title, book references Suggested Approach: contains WHAT to do, but not HOW to do it; use this if you have already completed the lab once and wish to test your mastery in a second attempt Sample Solution: start here when taking the lab for the first time; explanations of the WHY behind your configurations are given when needed; you can also print this out from home to use as a study guide for the CCENT certification Check Results: since the labs already have built-in verification steps, baseline configurations are found here for reference Device Controls: place a check next to each device; clicking Reload will make the gear ready to take a lab again or to take a new lab; if you become disconnected, clicking clearline will allow you to reconnect without losing your configurations

Diagram

Suggested Approach

Suggested Approach

The Suggested Approach steps are provided to test your mastery when taking a vLab for the second time. For your first attempt, follow the steps listed under Sample Solution.

of 11Print All


USING WINDOWS APPLICATIONS AS NETWORK TOOLS 1) From the Windows desktop, click start. 2) On your PC, choose Run, and enter cmd in the Run window dialog box. Click OK to continue. 3) Enter the command ipconfig in the command line window of your PC. 4) From the Start menu on your PC, choose Run, and enter ncpa.cpl in the Run window dialog box. 5) Under the first column, right-click on the connection your PC uses to connect to the network and select Properties. 6) Scroll down to the bottom of the Connection Properties window and left-click Internet Protocol (TCP/IP) to highlight it. Then click the Properties button. 7) From the command line window, ping the address of the default gateway that you obtained from the ipconfig command. 8) Console into R2 (Router 2). Enter the enable command. 9) On R2, enter global configuration mode. 10) On R2, enter interface configuration mode for serial 1/0. 11) On R2, enable interface s1/0. 12) Console into R1 (Router 1). Enter global configuration mode. 13) On R1, enable interface serial 1/1. 14) On R1, return to the privileged mode prompt. 15) Enter the debug ip tcp packet command and the debug ip tcp transactions command on R1. 16) From R1, initiate a TCP connection with R2 by entering the telnet 10.7.0.2 command. 17) Disable all debugging on R1. 18) From the Start menu on your PC, choose Run, and enter cmd in the Run window dialog box. 19) From the command line window on your PC, enter the command: ipconfig /all 20) From the command line window of your PC, ping the DNS server. 21) Using a Windows command, discover the IP addresses of routers that packets pass through to reach the DNS server. 22) Using a Windows command on your PC, discover the IP addresses of routers that packets pass through to reach the host: 4.2.2.1 23) From your PC, trace the route to 4.2.2.1 again, but this time do not use the /d parameter in the command. 24) You have finished the lab.

Sample Solution

Sample Solution

Task IndexTask 1 USING WINDOWS APPLICATIONS AS NETWORK TOOLS

Task 1

USING WINDOWS APPLICATIONS AS NETWORK TOOLS

Step 1 : From the Windows desktop, click Start. Action:

of 11Print All


1) Click Start

Result: Step 2 : On your PC, choose Run, and enter cmd in the Run window dialog box. Click OK to continue. Action:

1) Click Run 2) Open: cmd 3) Click OK Result: Explanation: The letters cmd are an abbreviation for command. Entering this will open a command line window on your PC. Step 3 : Enter the command ipconfig in the command line window of your PC. Action:

1) Enter ipconfig

Result: Basic IP information configured for your PC should appear. The graphic shown here is only an example. Make note of your default gateway address. You will need it in an upcoming step. Explanation: Your IP address is unique within the network. The subnet mask shows which portion of the IP address is the network portion and which is the host portion. For example, if your IP address were 10.50.17.6 with a subnet mask of 255.255.0.0, your network portion would be 10.50 and your host portion would be 17.6. Gateway is another term for router. Any packets that leave your PC that are not destined for the local network will be sent to the default gateway. Step 4 : From the Start menu on your PC, choose Run, and enter ncpa.cpl in the Run window dialog box. Action:

1) Close the command line window 2) Click Start 3) Click Run 4) Open: ncpa.cpl 5) Click OK

of 11Print All


Result: Your Network Connections window should appear. The graphic shown here is only an example. Explanation: You may be aware of an easier way to get to this window. The command ncpa.cpl is used here because it works in both XP and Vista to take you directly to Network Connections. Step 5 : Under the first column, right-click on the connection your PC uses to connect to the network and select Properties. Action:

1) Right-click on the name of your PC connection 2) Click Properties Result: Your Connection Properties window should appear. Explanation: Depending on your PC setup, you may see several connections listed, including Ethernet, wireless, or VPN. The correct one to choose should show the word, Connected, under the Status column. Step 6 : Scroll down to the bottom of the Connection Properties window and left-click Internet Protocol (TCP/IP) to highlight it. Then click the Properties button. Action:

1) Highlight Internet Protocol (TCP/IP) by left-clicking it 2) Click Properties Result: Your Internet Protocol (TCP/IP) Properties window should appear. Explanation: Observe the settings. Do not make any changes. You may find that the Obtain an IP address Automatically radio button has been selected with all of the fields blank, or the Use the Following IP Address radio button has been chosen and the fields configured with IP address information matching the output you obtained from the ipconfig command.

of 11Print All


Step 7 : From the command line window, ping the address of the default gateway that you obtained from the ipconfig command. Action:

1) Close the Internet Protocol (TCP/IP) Properties and Connections Properties windows. 2) Click Start 3) Click Run 4) Open: cmd 5) Enter ping X.X.X.X In place of the Xs use your default gateway address. Result: Your pings should be successful. Close the command line window after reading the explanation below. Explanation: Pings are used to test connectivity. Packets, known as echoes, are sent to the destination address and then replies, known as echo-replies, are sent back to the source. If you receive the message, Request timed out, this indicates that no replies were received. By default, the Windows ping command sends four ping packets (ICMP echo requests). Step 8 : Console into R2 (Router 2). Enter the enable command. Action:

r2> enable r2#

Result: Anytime you see a device blinking, it is a reminder to console into a new device. Explanation: Notice that your prompt changes from r2> to r2#. This indicates that you were in user mode and are now in privileged exec mode. From privileged exec mode, you can enter debug commands. In an upcoming step, you will enter two debug commands to observe a TCP 3-way handshake between R1 and R2. Step 9 : On R2, enter global configuration mode. Action:

r2# config t r2(config)#

Result: Explanation: Notice that the prompt has changed from r2# to r2(config)#. Changes can be made to the configuration when the word (config) is found in the prompt. Step 10 : On R2, enter interface configuration mode for serial 1/0. Action:

r2(config)# interface s1/0 r2(config-if)#

Result: Explanation: In configuration interface mode, your prompt changes again. This time to r2(config-if)#. From interface configuration mode, you can make changes that only affect that specific interface. Step 11 : On R2, enable interface s1/0. Action:

r2(config-if)# no shut

of 11Print All


r2(config-if)#

Result: Explanation: The no shut command is an abbreviation for no shutdown. Any IOS command can be abbreviated as long as there isn’t another command that starts with the same character string. Step 12 : Console into R1 (Router 1). Enter global configuration mode. Action:

r1> enable r1# config t r1(config)#

Result: Anytime you see a device blinking, it is a reminder to console into a new device. Step 13 : On R1, enable interface serial 1/1. Action:

r1(config)# interface s1/1 r1(config-if)# no shut r1(config-if)#

Result: Step 14 : On R1, return to the privileged mode prompt. Action:

r1(config-if)# end r1#

Result: Explanation: While in any type of configuration mode, you cannot enter verification commands, such as debugs. Therefore, you need to return to privileged mode. It is possible to get there by entering the exit command multiple times, but the end command is handy in that it takes you directly to privileged mode. Step 15 : Enter the debug ip tcp packet command and the debug ip tcp transactions command on R1. Action:

r1# debug ip tcp packet r1# debug ip tcp transactions r1#

Result: Explanation: Debugs allow you to see “under the hood” of the router to view processes as they take place that are normally hidden. Step 16 : From R1, initiate a TCP connection with R2 by entering the telnet 10.7.0.2 command. Action:

r1# telnet 10.7.0.2

of 11Print All


r1#

Result: EXAMPLE OUTPUT

You will see a lot of output, but the point of this step is to focus on the three-way handshake. First, look for the line near the top that contains TCP: sending SYN, seq 3662969175, ack 0. Your output will have a different sequence number. This line is the first part of the handshake, the SYN. Second, look for the line that contains tcp0: I SYNSENT 10.7.0.2:23 10.7.0.1:28216 seq 1158457196 OPTS 4 ACK 3662969176 SYN WIN 4128 Your output will have different sequence and acknowledgment numbers. Notice that it begins with the letter I for Input. This was received from the other router. The IP address 10.7.0.2 is R2 and :23 indicates the port number for telnet. IP address 10.7.0.1 is this router (R1). It uses an ephemeral port (randomly picked), so it will not match the example here of :28216. In the first part of the handshake, R1 sent out a sequence number and now it is receiving an acknowledgement number from R2 that is one digit higher. Third, look for the line that contains tcp0: O ESTAB 10.7.0.2:23 10.7.0.1:28216 seq 3662969176 ACK 1158457197 WIN 4128. Again, your sequence and acknowledgement numbers will be different, but compare this third step with the second step. You should find that the acknowledgement number is one digit higher than the sequence number sent by R2. Here is a summary of the conversation, using the example numbers: SYN: R1 sends seq 3662969175, ack 0 to R2. SYN-ACK: R2 replies back with seq 1158457196, ack 3662969176 ACK: R1 sends seq 3662969176, ack 1158457197 to R2. Step 17 : Disable all debugging on R1. Action:

r1# undebug all r1#

Result: Step 18 : From the Start menu on your PC, choose Run, and enter cmd in the Run window dialog box. Action:

1) Click Start 2) Click Run 3) Open: cmd 4) Click OK Result: Step 19 : From the command line window on your PC, enter the command: ipconfig /all Action:

of 11Print All


1) Enter ipconfig /all

Result: Explanation: You will notice additional information with the /all parameter. Make note of the IP address of your DNS server. The graphic shown here is only an example. You will need to know your DNS server address for the upcoming steps. You may have more than one available. Step 20 : From the command line window of your PC, ping the DNS server. Action:

1) Enter ping X.X.X.X In place of the Xs, use the IP address of the DNS server you discovered in a previous step. Result: Your pings should be successful. Step 21 : Using a Windows command, discover the IP addresses of routers that packets pass through to reach the DNS server. Action:

1) Enter tracert /d X.X.X.X In place of the Xs, use the IP address of the DNS server you discovered in a previous step. Result: If your trace route times out, you can stop the process by pressing Ctrl-c. Explanation: The /d parameter in the command, prevents the attempt to use DNS to look up IP addresses discovered along the path and put them in the output. Each IP address you see in the output is a hop, a router that was traversed, in order to ultimately get to the DNS server. Step 22 : Using a Windows command on your PC, discover the IP addresses of routers that packets pass through to reach the host: 4.2.2.1 Action:

1) Enter tracert /d 4.2.2.1 Result: If your trace route times out, you can stop the process by pressing Ctrl-c.

of 11Print All


Check Results

Check Results

This vLab was designed with verification commands and detailed explanations already built in to give you a deeper understanding of the technologies. The routers in this lab have baseline configurations in place. The configurations for these Cisco devices are listed below for reference.

hostname r1 ! no ip domain lookup ! interface FastEthernet0/0 description CONNECTION TO SW1 ip address 10.7.1.1 255.255.255.0 ! interface FastEthernet0/1 shutdown ! interface Serial1/0 shutdown ! interface Serial1/1 description CONNECTION TO R2 ip address 10.7.0.1 255.255.255.0 shutdown ! interface Serial1/2 description CONNECTION TO FRAME SWITCH ip address 172.41.7.1 255.255.255.0 encapsulation frame-relay frame-relay map ip 172.41.7.5 47 broadcast no frame-relay inverse-arp shutdown ! interface Serial1/3 shutdown ! line con 0 exec-timeout 30 0 logging synchronous

Explanation: Tracing to this destination should have a higher hop count than your test with the DNS server. Step 23 : From your PC, trace the route to 4.2.2.1 again, but this time do not use the /d parameter in the command. Action:

1) Enter tracert 4.2.2.1 Result: If your trace route times out, you can stop the process by pressing Ctrl-c. Explanation: With each hop, a DNS reverse-lookup is performed to see if there is a hostname that matches the IP address. If one is found, the name of the router is provided in your output. A DNS reverse-lookup starts with an IP address and translates it into a hostname. A regular DNS lookup start with a hostname, like www.elementk.com, and translates it into an address, like 67.137.6.238. Step 24 : You have finished the lab. Action: You can take this lab again if time permits. Result: You can test your mastery of the material when you take a lab for the second time. Instead of using the Sample Solution link which walks you through each step, you can use the Suggested Approach link. This provides the same steps, but without the walkthrough.

of 11Print All


line aux 0 line vty 0 4 logging synchronous login ! end

hostname r2 ! no ip domain lookup ! interface FastEthernet0/0 shutdown ! interface FastEthernet0/1 shutdown ! interface Serial1/0 description CONNECTION TO R1 ip address 10.7.0.2 255.255.255.0 clock rate 64000 shutdown ! interface Serial1/1 shutdown ! interface Serial1/2 description CONNECTION TO FRAME SWITCH ip address 172.41.7.2 255.255.255.0 encapsulation frame-relay frame-relay map ip 172.41.7.5 94 broadcast no frame-relay inverse-arp shutdown ! interface Serial1/3 shutdown ! line con 0 exec-timeout 30 0 logging synchronous line aux 0 line vty 0 4 logging synchronous login ! end

of 11Print All


khse.vlab.elementk.com vlab content manager print all

Documents