Chapter Summary

In this chapter, we described TCP/IP planning, design, and basic implementation. We also covered ways to troubleshoot TCP/IP. Now you can look at workstation problems with more confidence because you know how to ping devices on your network (and know what you are pinging ). You also know how to see whether you have an IP address or find what IP address you do have. You learned ways to plan a TCP/IP network as well as the devices that populate a network.

KEY TERMS

Before taking the exam, make sure you are comfortable with the definitions and concepts for each of the following key terms. You can use Appendix A, "Glossary," for quick reference.

• TCP/IP

• Network Address Translation (NAT)

• Physical address

• Network interface card (NIC)

• Layer 3 switch

• Router

• Default gateway

• Subnet mask

• Public address

• Private address

• Proxy server

• Firewall

• Protocol analyzer

Good networks begin with good planning and good designs. To plan and design a good network, you need to understand the IP addressing and routing requirements of your organization. With this knowledge in mind, you can move forward and start planning the IP subnets you need. This creates a solid backbone from which the rest of your network can be built. In this chapter, we looked at planning an IP-based network from many different angles. All networks should have a design and/or plan, and included in that plan should be information regarding where you would place your network resources (file, print, Internet access, and so on) as well as what protocols will be used to connect to and access such resources.

In all networks today, not connecting to the Internet would massively hamper a company's growth. Email, Web browsing, and a plethora of other solutions need Internet access to function, so not having Internet connectivity would be a huge problem. In this chapter, we also covered the importance of planning an Internet connectivity strategy. We looked at strategy, planning, and design. Networks have problems that at times are hard to solve or reproduce for one reason or another, but still need to be solved nonetheless. Using tools such as Network Monitor and System Monitor can help you find problems as well monitor traffic traversing your LAN. Once your network is connected to the Internet, many things can happen. You may have problems with Network Address Translation planning and implementation, with DNS, and of course, with clients trying to connect to and use the Internet.

All network administrators need to know, understand, and embrace TCP/IP. You need to know how to troubleshoot TCP/IP issues, as well as those issues resulting from problems with a DHCP server.