Chapter Summary

To have a reliable, routable network, you need to do effective planning.

In Windows Server 2003, TCP/IP is installed by default. Many features of Windows Server 2003 rely on TCP/IP; thus, in this version of Windows, TCP/IP cannot be uninstalled from a computer's network adapters. TCP/IP requires a valid IP address, subnet mask, default gateway, and DNS servers to operate properly in a large network environment. This information may be entered manually at each client computer and server, or it can be done automatically through DHCP (this is the preferred option). DHCP assigns the client computer an IP address when it is needed. If you're using Windows Server 2003 along with older NetBIOS-reliant operating systems, chances are that you'll be using WINS as well. WINS resolves NetBIOS names, such as Computer5, to IP addresses, such as 192.168.0.125. You can access the WINS properties through the WINS tab of the Advanced TCP/IP Settings dialog box.

When something goes awry with a TCP/IP configuration, you need to be able to determine the cause and the required corrective action. Windows Server 2003 (and Windows XP) provides you with a suite of tools that you can use to troubleshoot TCP/IP configuration. You will most commonly find yourself relying on the ping and ipconfig command-line tools. You can also use the Network Diagnostics tool to collect and display information in the Windows GUI. The more advanced, and more powerful, netsh command is also available to manage almost any networking setting.

Key Terms

• Class A IP address

• Class B IP address

• Class C IP address

• default gateway

• IP address

• ipconfig

• ping

• netsh

• subnet mask

• TCP/IP

• TCP/IP filter

• VLSM