Chapter 5 Lab – Troubleshooting Network Connectivity
This LAB requires a workstation running Windows or UNIX that has the TCP/IP protocol installed. Ideally, the workstation would be connected to a LAN that allows Internet access. In this project, you will view and modify a client’s TCP/IP properties using the ipconfig command.
1. Click the Windows icon and on the “Search” box that immediately follows, type CMD
2. Your command prompt will likely appear as a letter C followed by a colon and then the name of the directory in which you’re currently working. (For instance, you might see a prompt that reads “C:\Documents and Settings\CISUSER 1>.”) Type ipconfig and press Enter to view a summary of your workstation’s TCP/IP properties.
3. On a separate sheet of paper, write down the values of the four items displayed in the output (or paste them here).
4. Next, you’ll issue the same command, but add the /all switch to obtain the complete TCP/IP configuration for your workstation. Type ipconfig /all and then press Enter.
5. Read through the output of the ipconfig /all command. If you are connected to a network that uses DHCP, notice the date and time when your lease was obtained and when it is due to expire. On your paper, write down your machine’s host name and also the MAC address for your workstation’s NIC. (or paste them here). (or paste them here).
6. Next, type ipconfig /release and press Enter. What message is displayed? What implications do you predict this command will have on connectivity? There’s no connectivity.
7. Using your screen shot as a reference, attempt to ping the DHCP server and the DNS server. What are the results?_ _________________________________________________________________________
8. Type ipconfig and press Enter. Note that your adapter has no IP address and no subnet mask. These two parameters are necessary to communicate with TCP/IP.
9. To get an IP address lease again, type ipconfig /renew and press Enter. New IP information, (which might be the same address as before), is assigned.
10. Type ping ip_address, where ip_address is the address of BMCC website or ip_address of another workstation in our Lab and press Enter. Is this IP address responding? If not, what might be the problem?
In this part, you will gain experience with TCP/IP troubleshooting commands. To complete this project, you may use any type of workstation that has the TCP/IP protocol suite installed and is connected to the Internet. The following steps cover Windows, UNIX, and Linux workstations. Note that if your computer runs a newer version of Linux, you might have to replace traceroute with tracepath in the route tracing command syntax.
1. If you are using a workstation running a UNIX or Linux operating system with a GUI interface, open a shell prompt window. If you are using a workstation running the Windows operating system, click Start, select All Programs, click Accessories, and then select Command Prompt. The Command Prompt window opens.
2. At the prompt, type netstat -a and press Enter. Recall that netstat is the command that reveals all TCP/IP port connections, even if they are not actively exchanging data. How many connections are listed on your computer? Many many connections.
3. Look at the State column in your connection listing. How does the value in this column differ for TCP connections? Why do you suppose this is the case?______________________________________
4. Type netstat -s and press Enter. How many different TCP/IP core protocols are currently in use on your machine? Of those, which one sent and received the most packets? 6 TCP/IP protocols are in use on my machine. The IPv4 sent and received the most.
5. Next, you experiment with another TCP/IP utility, the traceroute function. If you are using a workstation running a UNIX or Linux operating system, type traceroute www.cengage.com at the shell...
Please join StudyMode to read the full document