This chapter provides a detailed discussion of Windows 2000 networking, including an explanation of TCP/IP, routing, network address translation (NAT), legacy protocols, and other topics related to Windows 2000 network configuration. | Windows 2000 Networking This chapter provides a detailed discussion of Windows 2000 networking including an explanation of TCP IP routing network address translation NAT legacy protocols and other topics related to Windows 2000 network configuration. TCP IP on Windows 2000 A little more than a decade ago TCP IP was used only by a relatively small number of computers connected to the Internet. As the number of networks connected to the Internet grew explosively and as companies expanded to include more and more networks within the enterprise TCP IP has come to be the protocol of choice for most organizations. The reasons are many but commonly include standardization ability to route and of course need for Internet connectivity. Windows 2000 offers strong support for TCP IP. It can be considered its primary protocol for and the foundation of Active Directory which is the keystone of Windows 2000 networks. On the client side the TCP IP protocol enables full support for connecting to both peer and server computers running TCP IP the Internet and TCP IP-based services such as networked printers. On the server side Windows 2000 offers all the configuration and management tools you would expect including support for dynamic address allocation through DHCP name resolution through DNS NetBIOS name resolution through WINS and a full range of configuration and troubleshooting tools. In This Chapter TCP IP on Windows 2000 TCP IP Basics IP Routing Network Address Translation Troubleshooting TCP IP SNMP Legacy Protocols 416 Part IV Networking and Communications Services Windows 2000 offers a few new features to support TCP IP clients. Windows 2000 DHCP clients for example can request updates for their host records with a Windows 2000 DNS server enabling DHCP clients to have up-to-date host entries in their domains. Windows 2000 DHCP servers can also initiate updates on behalf of TCP IP clients including non-Windows 2000 clients. Windows 2o00 DHCP servers can request an update of
