TCp/IP Lab

TCP/IP Utilities Lab
1. Issue a Ipconfig command at the command prompt. Try some of the popular switches such as /all and /?.

With ipconfig you can check your ip address to ensure you are being assigned one from a DHCP server or that your static ip address is correct. You can also use /flushdns to remove all entries from the DNS name cache if you think it has been corrupted. /displaydns displays the contents of the DNS resolver cache. If you have multiple adapters connected you specify which adapter to release and renew.

2. Issue a Netstat command at the command prompt. Try some of the popular switches such as - p and -a. Capture a screen shot and write a paragraph about how you would use the command to troubleshoot a problem. Put this information in your blog.

Using netstat you can see which protocol might be eating up your bandwidth if your connection is slow. You can flush phantom connections that no longer need to be connected. Using the –b switch you can see what programs are associated with which connections.

3. Issue a Nbtstat command at the command prompt. Nbtstat is designed to help troubleshoot NetBIOS name resolution problems.

Displays NetBIOS over TCP/IP (NetBT) protocol statistics, NetBIOS name tables for both the local computer and remote computers, and the NetBIOS name cache. I do not have NetBios enabled on my network so the only things that show up are

4. Issue a Hostname command. You can change the computers host name thru this command.

5. Use the Nslookup command to view the IP address of at least three domain names.
   

6. Issue a Tracert command at home.
   

If you are running a web server, tracert can reveal lags in the routing if you try to access your site from another pc. Useful for troubleshooting internal networks by identifying where the problem occurs, i.e. a router, switch.