Network Design

A Microsoft Windows Network  can be configured as a basic peer-to-peer network, or as a Microsoft Windows Domain Network.  Peer-to-peer networks usually take advantage of the Microsoft Windows Work group networking built-in as part of all Windows Operating systems.  A File Server is not required, security is usually not a concern, and there is no central management of the network.  Everyone with a computer simply connects to the network's backbone and is automatically made part of the network.  Individual users manage their own computer's security and shared resources.  This is the most common network found in small 3 - 10 computer offices.  It is hard to maintain and problematic at best.

In the design of a small office network, the most primary questions are, does the office require a File Server to support file, printer, and application sharing; will the network be wired or wireless; and how will Internet access be controlled.  Usually, the software in this environment is installed on individual computers; Internet access is open to everyone via a local SOHO router/firewall; and remote access usually isn't needed or software such as PC Anywhere or Remote Desktop is used to grant remote access. 

It's not until the need for multi-user access to Management Information Systems or Business Practice Application software will a small offices consider adding a file server to the peer-to-peer network; however, in many instances, a true File Server is not used, but rather a dedicated Workstation might be added to the  network and the MIS or BPA software is shared for all to use.  Absolutely no security is in place here.  Everyone has All-Rights to the entire system; which is a disaster waiting to happen.

One thing you can't (easily) do with peer-to-peer networks is join them through routers, across the Internet, or between remote offices. 

Microsoft Windows Domain Network Design

A Microsoft Windows Domain is not simply thrown together without a design plan.  A network should be born from a requirements analysis document that details the proposed Network.  The Requirements Analysis Document should address all relevant networking issues.  In the remainder of this document, I will outline some of the primary questions our requirements analysis will expose.  As you will see, there are many things to consider.

This billet must be addressed first; although it is usually the last thing a client thinks about.  Most networks are thrown together, and then the question of security is brought up.  Security is the most primary issue to be considered.  Security can be broken down into the following:

The major components of the network

• File Server Design
• Network topology
• Workstations
• Printers / Print Servers
• Network Protocols
• Wireless Configuration / Access Control
• Electronic Mail
• Anti-Virus

DRAFT  Last Modified 3/18/2007