【正文】 tion of IP addresses and other related configuration details for DHCPenabled clients on your work. Every puter on a TCP/IP work must have an unique IP address. The IP address (together with its related sub mask) identifies both the host puter and the sub to which it is attached. When you move a puter to a different sub, the IP address must be changed. DHCP allows you to dynamically assign an IP address to a client from a DHCP server IP address database on your local work. For TCP/IPbased works, DHCP reduces the plexity and amount of administrative work involved in reconfiguring puters. WINS (optional) While DNS is a required ponent of a foundation work, WINS is optional because, like DNS, it is a naming service. In some cases, you might not need both DNS and WINS, but older operating systems and applications might require WINS. For medium to small works, WINS is extremely easy to install and manage, and it is not resourceintensive. If you are in doubt about whether you need WINS, you can test your work functionality without it and install it if needed. WINS provides a distributed database for registering and querying dynamic mappings of NetBIOS names for puters and groups used on your work. WINS maps NetBIOS names to IP addresses and was designed to solve the problems arising from NetBIOS name resolution in 8 routed environments. WINS is the best choice for NetBIOS name resolution in routed works that use NetBIOS over TCP/IP. NetBIOS names are used by earlier versions of Windows operating systems to identify and locate puters and other shared or grouped resources required to register or resolve names for use on the work. NetBIOS names are a requirement for establishing working services in earlier versions of Windows operating systems. Although the NetBIOS naming protocol can be used with work protocols other than TCP/IP (such as NetBEUI or IPX/SPX), WINS was designed specifically to support NetBIOS over TCP/IP (NetBT). WINS simplifies the management of the NetBIOS namespace in TCP/IPbased works. NPS (optional) Network Policy Server (NPS) allows you to centrally configure and manage work policies with the following three features: Remote Authentication DialIn User Service (RADIUS) server, RADIUS proxy, and Network Access Protection (NAP) policy server. NPS is an optional ponent of a foundation work, but you should install NPS if any of the following are true: ?? You are planning to expand your work to include any remote access servers that are patible with the RADIUS protocol, such as a puter running Windows Server 2020 and Routing and Remote Access service. ?? You plan to deploy NAP. ?? You plan to deploy wired or wireless access. TCP/IP TCP/IP in Windows Server 2020 is the following: ?? Networking software based on industrystandard working protocols. ?? A routable, enterprise working protocol that supports the connection of your Windowsbased puter to both local area work (LAN) and wide area work (WAN) environments. ?? Core technologies and utilities for connecting your Windowsbased puter with dissimilar systems for the purpose of sharing information. ?? A foundation for gaining access to global Inter services, such as the World Wide Web and File Transfer Protocol (FTP) servers. ?? A robust, scalable, crossplatform, client/server framework. TCP/IP provides basic TCP/IP utilities that enable Windowsbased puters to connect and share information with other Microsoft and nonMicrosoft systems, including: ?? Windows Vista ?? Windows Server 2020 operating systems ?? Windows XP 9 ?? Inter hosts ?? Apple Macintosh systems ?? IBM mainframes ?? UNIX systems ?? Open VMS systems ?? Networkready printers, such as HP LaserJet series printers that use HP JetDirect cards Foundation Network Overview The following illustration shows the ponents of a foundation work. 10 Foundation Network Components Following are the ponents of a foundation work. 11 Router This deployment guide provides instructions for deploying a foundation work with two subs separated by a router that has DHCP forwarding enabled. You can, however, deploy a Layer 2 switch, a Layer 3 switch, or a hub, depending on your requirements and resources. If you deploy a switch, the switch must be capable of DHCP forwarding or you must place a DHCP server on each sub. If you deploy a hub, you are deploying a single sub and do not need DHCP forwarding or a second scope on your DHCP server. Static TCP/IP configurations All of the servers in this deployment are configured with static IPv4 addresses. Client puters are configured by default to receive IP address leases from the DHCP server. Global catalog and DNS server Both Active Directory Domain Services (AD DS) and Domain Name System (DNS) are installed on this server, providing directory and name resolution services to all puters and devices on the work. WINS server (optional) Installing Windows Inter Name Service (WINS) on your foundation work is optional. It is often difficult to determine whether applications and services require WINS for name resolution. In some cases, you might need WINS。 operating systems that implements and supports the TCP/IP protocol suite. ?? Automatic IP addressing with Dynamic Host Configuration Protocol (DHCP). Manual configuration of IP addresses on all puters on your work is timeconsuming and less flexible than dynamically providing puters and other devices with IP address leases from a DHCP server. ?? Name resolution services, such as Domain Name System (DNS) and Windows Inter Name Service (WINS). DNS and WINS allow users, puters, applications, and services to find the IP addresses of puters and devices on the work using the work basic input/output system (NetBIOS) name or Fully Qualified Domain Name of the puter or device. ?? A forest, which i