This chapter includes the following sections, which address various topics covered on the Designing a Microsoft Windows 2000 Network Infrastructure MCSE exam:
- Designing a Network Infrastructure
Describes the scope of a network infrastructure design and presents an overview of the network services you will use in planning the network. Also introduces the process of examining the business requirements, technical requirements, and existing network infrastructure to plan a design.
- Designing TCP/IP Networks
Describes the process of creating a TCP/IP design as a basis for a complete network infrastructure.
- Designing DHCP Services
Examines the requirements and process of creating a design for DHCP (Dynamic Host Configuration Protocol).
- Designing Name Resolution Services
Provides techniques for developing designs for name resolution services, including DNS (Domain Name Service) and WINS (Windows Internet Naming Service).
- Designing Internet Connectivity
Describes the design considerations for Internet connectivity services, including Microsoft Proxy Server and NAT (Network Address Translation).
- Designing Routing and Remote Access
Provides methods for planning routes between networks, routing protocols, and on-demand routing. Examines planning considerations for remote access solutions, including RAS (Remote Access Service) and RADIUS (Remote Authentication Dial-In User Service).
This chapter deals with the process of designing a network infrastructure : the protocols and services that comprise a network. Microsoft divides network service design into three phases:
- Design
The initial planning, design, and testing for a network or a service within a network
- Implementation
The process of putting the planned design into action on the network
- Management
The administration and management required for day-to-day management of the network or service
This chapter describes the considerations you should use when designing a Windows 2000 network infrastructure. This can include any number of network protocols and services. The main protocols and services you will use in most Windows 2000 design include the following:
- TCP/IP
TCP/IP (Transmission Control Protocol/Internet Protocol) is the main transport protocol used in Windows 2000 networks, as well as the Internet.
- DHCP
DHCP (Dynamic Host Configuration Protocol) allocates IP addresses to clients from a pool of available addresses, eliminating the need for manual address allocation, and can also assign DNS addresses and other configuration.
- DNS and WINS
These services provide name resolution, translating resource names to IP addresses. DNS (Domain Name Service) supports IP hostname resolution, and WINS (Windows Internet Name Service) supports NetBIOS name resolution.
- NAT
NAT (Network Address Translation) translates private IP addresses to public addresses, allowing a single computer to provide Internet access for a private network and eliminating the need for public addresses for all machines on the network.
- Microsoft Proxy Server
Microsoft Proxy Server acts as an intermediary between a private network and the public Internet, similar to NAT. Unlike NAT, Proxy Server provides user-based and site-based security, caching, and support for web publishing.
- Routing
Network routing uses either hardware-based routers or computers running routing software, including Windows 2000, to transmit network traffic between subnets. Routers combine subnets into a single coherent network.
- Remote Access
Windows 2000’s Remote Access services allow remote users to access the network through dial-up modems. Remote Access can also be used with routing to allow dial-on-demand routing to the Internet or other networks.
An essential part of the design of a network infrastructure involves examining the requirements of the business, the technical requirements, and the existing network. The following sections discuss these considerations.
When you are designing a new network, business requirements will be the primary source of information. These include the needs of users (access to files, printers, and other resources) and the needs of management (security, user management, and administration).
Whether you plan to design a network from scratch or augment an existing network, there are technical requirements. These include the operating systems that will be used, the network wiring, and the features of available hardware and software. Carefully note these requirements to avoid creating technical problems when the design is implemented.
In many cases, an existing network is already present and you must design additions to the network, or support for additional services. You should document the existing network thoroughly and take its configuration into account when planning the new network.
Last but not least, any network design should account for the certainty of change in the future. Networks will require support for more computers and more users, as well as support for future technologies and operating systems. A good network design should be flexible and anticipate as many of these changes as possible.