【正文】 s or device39。 and Windows XP are configured by default as DHCP clients, which obtain IP addresses and DHCP options automatically from the DHCP server. Foundation Network Planning Before you deploy a foundation work, you must plan the following items. 12 ?? Planning subs ?? Planning basic configuration of all servers ?? Planning the deployment of ADDNS01 ?? Planning domain access ?? Planning the deployment of WINS01 ?? Planning the deployment of DHCP01 ?? Planning the deployment of NPS01 The following sections provide more detail on each of these items. Planning subs In Transmission Control Protocol/Inter Protocol (TCP/IP) working, routers are used to interconnect the hardware and software used on different physical work segments called subs. Routers are also used to forward IP packets between each of the subs. Determine the physical layout of your work, including the number of routers and subs you need, before proceeding with the instructions in this guide. In addition, to configure the servers on your work with static IP addresses, you must determine the IP address range that you want to use for the sub where your foundation work servers are located. In this guide, the private IP address range is used as an example, but you can use any private IP address range. The following recognized private IP address ranges are specified by Inter Request for Comments (RFC) 1918: ?? – ?? – ?? – When you use the private IP address ranges as specified in RFC 1918, you cannot connect directly to the Inter using a private IP address because requests going to or from these addresses are automatically discarded by Inter service provider (ISP) routers. To add Inter connectivity to your foundation work later, you must contract with an ISP to obtain a public IP address. Important When using private IP addresses, you must use some type of proxy or work address translation (NAT) server to convert the private IP address ranges on your local work to a public IP address that can be routed. For more information, see Planning the deployment of DHCP01. 13 Planning basic configuration of all servers For each server in the foundation work, you must change the password for the Administrator account on the local puter, rename the puter, and assign and configure a static IP address for the local puter. Planning the Administrator account password For security reasons, it is important to create a password for the Administrator account and to use a strong password. In addition, it is remended that you use a different Administrator account password for each server on your work. The following is an example of a strong password. Configuration item: Example value: Administrator password Example: J*p2leO4$F Note Strong passwords contain a minimum of 7 characters that consist of each of the following: uppercase letters (A, B, C, lowercase letters (d, e, f), numerals (0, 1, 2, 3), and keyboard symbols (39。. 6 About this guide This guide is designed for work and system administrators who are installing a new work or who want to create a domainbased work to replace a work that consists of workgroups. The deployment scenario provided in this guide is particularly useful if you foresee the need to add more services and features to your work in the future. It is remended that you review design and deployment guides for each of the technologies used in this deployment scenario to assist you in determining whether this guide provides the services and configuration that you need. Network hardware requirements To successfully deploy a foundation work, you must deploy work hardware, including the following: ?? Ether, Fast Ether, or Gigabyte Ether cabling ?? A hub, Layer 2 or 3 switch, router, or other device that performs the function of relaying work traffic between puters and devices. ?? Computers that meet the minimum hardware requirements for their respective client and server operating systems. Note This guide depicts the use of four server puters. In some cases, such as on small works, you can use fewer servers. For example, you can install DHCP and WINS on the same server rather than on separate servers. What this guide does not provide This guide does not provide instructions for deploying the following: ?? Network hardware, such as cabling, routers, switches, and hubs ?? Additional work resources, such as printers and file servers ?? Inter connectivity ?? Remote access ?? Wireless access ?? Client puter deployment Note Client puters running Windows Vista and Windows XP are configured by default to receive IP address leases from the DHCP server. Therefore, no additional DHCP or Inter Protocol version 4 (IPv4) configuration of client puters is required. 7 Technology Overviews The following sections provide brief overviews of the required and optional technologies used to create a foundation work. Active Directory Domain Services A directory is a hierarchical structure that stores information about objects on the work. A directory service, such as AD DS, provides the methods for storing directory data and making this data available to work users and administrators. For example, AD DS stores information about user accounts, such as names, passwords, phone numbers, and so on, and enables other authorized users on the same work to access this information. DNS DNS is a name resolution protocol for TCP/IP works, such as the Inter or an anization work. A DNS server hosts the information that enables client puters to resolve easily recognized, alphanumeric DNS names to the IP addresses that puters use to municate with each other. DHCP DHCP is an IP standard for simplifying management of host IP configuration. The DHCP standard provides for the use of DHCP servers as a way to manage dynamic alloca