370 likes | 506 Views
70-291: MCSE Guide to Managing a Microsoft Windows Server 2003 Network Chapter 1: Networking Overview. Objectives. Define a network and describe its usage Describe some of the features of Windows Server 2003 Understand the differences in the editions of Windows Server 2003
E N D
70-291:MCSE Guide to Managing a Microsoft Windows Server 2003 NetworkChapter 1:Networking Overview
Objectives • Define a network and describe its usage • Describe some of the features of Windows Server 2003 • Understand the differences in the editions of Windows Server 2003 • Identify the different types of networks commonly found in industry • Describe common network protocols and their usage 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Objectives (continued) • Outline the Open Systems Interconnection (OSI) model and how it is used as a model for transmission of information across a network • Recognize the components in the Windows Server 2003 networking architecture • List common networking services available in Windows Server 2003 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Defining Networks • Information is usually transmitted between computers via different types of media • Media attaches to a computer system through adapter • Network: • Consists of two or more computers that can exchange information through a medium • Servers share information or other resources • Clients access shared resources 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Defining Networks (continued) • Single computer may be both a server and a client • Windows Server 2003 is called a network operating system (NOS) • Windows Server 2003 is the latest NOS superceding Windows 2000 and Windows NT4 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Windows Server 2003 Editions • Multiple versions of Windows Server 2003 exist • Each version is defined to meet the need of a certain market segment • Versions Include: • Web Edition • Standard Edition • Enterprise Edition • Datacenter Edition 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Web Edition • Lower-cost edition • Designed to be a dedicated web server • Designed to be a direct competitor with the Linux operating system • The server must be a member server or a standalone server • Load balancing is supported 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Web Edition (continued) • Clustering is not supported • Limited virtual private networking (VPN) support • Lacks support for Macintosh services • Internet Authentication Service is not supported • No support for Remote Installation Services • Lacks support for Windows Media Services • Terminal Services are not supported 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Standard Edition • Most likely to be used as a departmental file and print server or application server • Provides remote installation services (RIS) • Can be used as a domain controller, member server, or standalone server • Supports load balancing • Does not support clustering 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Standard Edition (continued) • Full VPN support • Support for Macintosh services • Support for Windows Media Services • Support for terminal services 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Enterprise Edition • Designed to enable large enterprises to deliver highly available applications and web services • Available in both 32-bit and 64-bit versions • Server can be a member server, domain controller, or standalone server • Supports load balancing • Clustering and Metadirectory Services are supported 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Enterprise Edition (continued) • Capable of 64-bit processing • Support for hot add memory • Non-Uniform Memory Access is supported (NUMA) 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Datacenter Edition • Designed for mission-critical applications that require the highest levels of availability and scalability • Available in both 32 and 64-bit editions • Cannot be bought as retail software • Customer cannot add, update, or remove drivers and hardware 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Datacenter Edition (continued) • Server can be a member server, domain controller, or standalone server • Support for load balancing and clustering • Metadirectory Services are not supported • 64-bit processing supported • Hot add memory supported 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Datacenter Edition (continued) • NUMA supported • Requires datacenter program • Internet Connection Firewall (ICF) is not supported 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Hardware Requirements for Windows Server 2003 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Windows Server 2003 Installation Hardware Requirements 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Windows Server 2003 Installation Hardware Requirements (continued) 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Network Types and Protocols • Local area networks (LANs) connect computers within close proximity • LANs are the most common types of networks • Metropolitan area networks (MANs) connect computers separated by moderate distances • Wide area networks (WANs) typically connect computers between cities, across countries, or even around the world 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Network Types and Protocols (continued) • A network protocol packages information into packets • A media access method sends packets onto the media itself • IPv4 • Most common LAN protocol used today • Also the standard protocol used to transmit information over the internet 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Network Types and Protocols (continued) • IPv6 offers enhancements to IPv4 • Both IPv4 and IPv6 are referred to as TCP/IP • IPX/SPX protocol: • Used for backward compatibility with older networks • Macintosh computers use the AppleTalk protocol 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Network Types and Protocols (continued) • Ethernet is the most common media access method used to send TCP/IP packets over a network • In the token ring media access method, the computer with the token is allowed to transmit over the network 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Network Architecture • Various hardware and software that allow the transfer of information amongst computers on a network 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
The OSI Model • Open System Interconnection model • A seven-layer model • Explains the different components used when sending or receiving data 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
The OSI Model (continued) • Seven layers include: • Application • Presentation • Session • Transport • Network • Data link • Physical 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
The OSI Model (continued) • Server will interact with the application layer first • Client interacts at the physical layer first 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
The OSI Model 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
The Windows Network Architecture • Four main software components that comprise OSI: client, service, protocol, adapter • Network Driver Interface Specification (NDIS) resides between protocols and adapter software • Transport Driver Interface resides between clients and protocols and between services and protocols 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
The Windows Network Architecture (continued) 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
NDIS • Developed by Microsoft and 3Com • Used to speed the development of device drivers and enhance networking capabilities • Developers of network card drivers and protocols can independently write code that communicates with NDIS • Acts as intermediary for all communication between protocol and network card driver 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
NDIS (continued) • Bindings between protocols and adapters are controlled by NDIS • A single adapter can be bounded to multiple protocols and visa-versa 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
TDI • Transport Driver Interface • Provides clients and services with access to network services • Emulates two network access methods: • Network Basic Input/Output System (NetBIOS) • Windows Sockets (WinSock) • NetBIOS is the older network interface • WinSock is used by Internet Explorer, Outlook Express, and other internet applications 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Common Network Services • Dynamic Host Configuration Protocol (DHCP) • Domain Name System (DNS) • Windows Internet Naming System (WINS) • Routing and Remote Access Service (RRAS) • Network Address Translation (NAT) 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Common Network Services (continued) • Internet Connection Sharing (ICS) • Internet Authentication Service (IAS) • IP Security (IPSec) • Internet Connection Firewall (ICF) • Public key infrastructure (PKI) 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Common Network Services (continued) • Network load balancing • Automated System Recovery • Internet Protocol version 6 (IPv6) • Point-to-Point Protocol over Ethernet (PPPoE) • Volume Shadow Copy 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Summary • Windows Server 2003: latest version of the Windows network OS with many new features • Four editions of Windows Server 2003: Web, Standard, Enterprise, and Datacenter Editions • Networks consist of two or more computers that share information • Information must be formatted using a network protocol before being sent on the network itself 70-291: MCSE Guide to Managing a Microsoft Windows Server Network
Summary (continued) • OSI: General network architecture model that describes how information is sent to and received from a network • TDI layer resides between clients and protocols or between services and protocols • NDIS is responsible for binding protocols to network adapters • Many network services are available in Windows Server 2003 70-291: MCSE Guide to Managing a Microsoft Windows Server Network