Cisco packet tracer practice file : Test a Wireless Connection

In this post you'll gain knowledge about how to Test a Wireless Connection

So Lets start this:

First download this file from here:  Test a Wireless Connection

After that do the following activity:

Learning Objectives

• Configure a PC to join a wireless network.
• Test the wireless connection.

Introduction

In this activity, you will configure PC3 to connect to the network via the Linksys WRT300N.

Task 1: Configure the wireless connection

Step 1. Configure PC3 to connect to the WRS1.

1. Click PC3 to open the Physical Device View.
2. Click the Desktop tab for PC3.
3. Select the PC Wireless button. The Link Information window opens with the note: No association with access point.
4. Click the Connect tab in the window.
5. When WRS_LAN appears as an available wireless network, click the Connect button.
6. Enter ABCDE12345 as the WEP key and click the Connect button.
7. Select the Link Information tab. A message should display: You have successfully connected to the access point. If you do not receive this message, troubleshoot the steps in this activity.

Task 2: Verify the address configuration of PC3

Step 1. View IP address configuration of PC3.

1. Close the PC Wireless window.
2. Click the Command Prompt button.
3. Type ipconfig /all and then press the Enter key.
4. What is the physical address of the computer? What is another name for the physical address?

5. What is the IP address of the computer?

6. What is the subnet mask of the computer?

7. What is the default gateway of the computer?

8. What is the DNS server address? What service does the DNS server provide to the network?

Task 3: Verify the network connection between PC3 and the rest of the network

Step 1. Verify connectivity between PC3 and the rest of the network using the ping command.

1. From the Command Prompt window, ping the default gateway for PC3. The ping should be successful. A successful ping resembles the output below:

PC>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time=203ms TTL=255
Reply from 192.168.2.1: bytes=32 time=94ms TTL=255
Reply from 192.168.2.1: bytes=32 time=94ms TTL=255
Reply from 192.168.2.1: bytes=32 time=78ms TTL=255

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 203ms, Average = 117ms

2. From the Command Prompt window, ping PC1 using its IP address of 192.168.1.11. (The ping should be successful.)

Step 2. Verify connectivity and the path between PC3 and the rest of the network using the tracert command.

1. The tracert command is used to determine the path between a local host, in this case PC3, and a remote host. From the Command Prompt verify the path between PC3 and PC2 using the below command from the Command Prompt on PC3.
   
   Type tracert 192.168.1.12 and then press the Enter key.

2. The output of the command should resemble the following information:

PC>tracert 192.168.1.12

Tracing route to 192.168.1.12 over a maximum of 30 hops: 

1 187 ms 94 ms 93 ms 192.168.2.1
2 * 125 ms 125 ms 192.168.1.12

Trace complete.

3. Following the output of the command, the ICMP packets generated by the tracert command show the packets traveling across the WRS1 LAN interface to the host, PC2.

Task 4: Using DNS

Step 1. Verify connectivity to the web server using DNS.

1. Close the Command Prompt window on PC3.
2. Click the Web Browser button.
3. Enter http://www.example.com in the URL window and click the GO button. The webpage for the server should display.
4. DNS is used to resolve domain names to IP addresses. To verify the resolution, close the Web Browser window on PC3.
5. Click the Command Prompt button to open the Command Prompt on PC3.
6. In the Command Prompt window ping the webserver using the domain name www.example.com. This should generate the following output:

PC>ping www.example.com

Pinging 192.168.3.100 with 32 bytes of data:

Reply from 192.168.3.100: bytes=32 time=138ms TTL=126
Reply from 192.168.3.100: bytes=32 time=156ms TTL=126
Reply from 192.168.3.100: bytes=32 time=172ms TTL=126
Reply from 192.168.3.100: bytes=32 time=140ms TTL=126
Ping statistics for 192.168.3.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 138ms, Maximum = 172ms, Average = 151ms

Note that the domain name www.example.com was translated by the DNS server to the IP address for the webserver, 192.168.3.100. This verifies proper operation of the DNS server.

So far all the DNS requests were done automatically by other applications. In item (c) it was done by the web browser and in item (f) by the ping command. To generate DNS requests directly to the server use the nslookup command.

7. Still from PC3 Command Prompt, type nslookup www.example.com. The command followed by its output should look like the following:

PC>nslookup www.example.com

Server: [192.168.3.100]

Address: 192.168.3.100

Non-authoritative answer:

Name: www.example.com

Address: 192.168.3.100

PC>

When entered in the format above, nslookup will submit a request to a DNS server asking “What’s the IP address associated to the name www.example.com”.

The first line of the command’s output informs the name of the DNS server who received the DNS request. PC3 sent the request to 192.168.3.100 because it learned from WRS1 via DHCP 192.168.3.100 was to be used to resolve names. Since no name was defined to 192.168.3.100, the IP address was shown.

The second line informs the IP address of the DNS server used in the request.

The third, fourth and fifth lines reveal the actual answer to the request: the name www.example.com is associated to the 192.168.3.100 IP address.

Your completion percentage should be 100%. If not, click Check Results to see which required components are not yet completed.