Introduction

In this chapter, we look at how to plan, implement, and maintain a Windows Server 2003 network infrastructure. Before we delve into the specifics of "how" to do this, we first introduce the "why." Why should you worry so much about your network infrastructure? The answer is simple: If you don't have a well-developed network infrastructure, the rest of your applications, services, and systems will fail. Don't believe it? Let's look at an example from a client with a poorly designed network infrastructure.

ABC Corporation has been in business for 10 years . It is the primary producer of widgets for the world. ABC Corp. needs to merge with three new companies by the end of the year to broaden its widget inventory. The four widget companies will form one network after the merger is complete. You are the network administrator responsible for making this happen. Following are issues you will most likely see arise:

• Wasteful IP numbering schemes

• Routing loops and problems with routing tables from improperly designed networks or networks connected improperly

• A need to connect internal DNS namespaces, WINS servers, and Active Directory

• A need to have email systems work together

• A need to tie applications and databases together and make them accessible to all users in all plants

The whole point to this example is that without a "rock solid" network infrastructure, you are assured to see problem after problem arise from lack of planning and design. Some of the items listed here are business solutions that your users demand and expect. It's up to you to understand the infrastructure well enough so that you can implement these solutions easily enough.

The goal of this chapter is not only to present you the information you need to pass this exam, but also to introduce you to the importance of actually doing this work for real.