Chapter Two
Network Operating Systems
Objectives
Describe characteristics common to all NOSs (network operating systems)
Compare and evaluate NOSs to select the right one for your Network
Define the requirements for and features of the Windows Server 2008 NOS
Define the requirements for and features of UNIX and Linux NOSs
Create users and groups and assign file permissions on systems running Windows Server 2008
and UNIX
Page 1 of 16
Characteristics of Network Operating Systems
Based on client/server architecture
NOS manages resource sharing
NOS provides many other functions
Some built in
Some configured at installation
Default, customizable settings
NOS components vary by NOS version and type
Network Operating Systems and Servers
Networks use servers exceeding minimum hardware
Determining optimal server hardware
Questions
What kinds of applications will run on the server? How many clients will
connect to the server?
How much storage space will each user need? How much downtime, if any, is
acceptable? Page 2 of 16
Characteristics of Network Operating Systems
Determining optimal server hardware (cont’d.)
Applications influence: Type of
application Resources used
Processing burden
Vendor reputation requirements
High quality, dependability, excellent technical
support Reliable server
Spend as much as necessary Page 3 of 16
Characteristics of Network Operating Systems
Client Support
Important NOS function
Allows efficient communication, resource sharing
NOS client support tasks
Creating and managing client accounts
Enabling clients to connect to the network
Allowing clients to share resources
Managing clients’ access to shared resources
Facilitating communication between clients
Page 4 of 16
Client/Server Communication
Logon process Redirector
Intercepts requests, determines where to handle
File access protocol
Windows XP client communication with Windows
Server 2008
CIFS
(Common Internet File System)
Older protocol SMB
(Server Message Block)
Broad support allows every client type to authenticate,
access resources
Middleware
Translates requests, responses between client, server
3-tier architecture
Page 5 of 16
Users and Groups
After NOS client authentication
Client gains access to NOS services, resources
Administrator account
Most privileged user account
Unlimited rights to server, domain resources, objects
Created by default
Root on UNIX or Linux systems User names
NOS grants each network user access to files and other
shared resources
Groups
Basis for resource and account management
Assists in resource sharing and security control
Example: network administrator for public elementary school
Page 6 of 16
Nesting or hierarchical group arrangement
Simplifies management
Group arrangement
Affects permissions granted to each group’s members Inherited permissions
Passed down from parent group to child group After user, group
restrictions applied
Client allowed to share network resources
Identifying and Organizing Network Elements
Modern NOSs
Similar patterns for organizing information
Users, printers, servers, data files, and applications
Directory
List organizing resources
Associates resources with characteristics
Example: file system directory
Page 7 of 16
LDAP (Lightweight Directory Access Protocol)
Used to access information stored in directory Object
Thing or person associated with network
Attributes
Properties associated with object Schema
Set of definitions
Kinds of objects and object-related information contained in
directory
Two types of definitions:
Classes (object classes): identifies object type specified in directory Attributes: stores
information about object
Containers (OUs or organizational units)
Logically defined receptacles Assemble similar
objects
Account
Page 8 of 16
User record containing all properties
LDAP standard
Directories and contents form trees
Tree
Logical representation of multiple, hierarchical levels within
directory Root, branches, leaves
Page 9 of 16
Identifying and Organizing Network Elements
Before installing NOS
Plan directory tree
Consider current, future needs
Book example
New manufacturing firm: Circuits Now
Page 10 of 16
Sharing Applications
Shared applications
Often installed on file server
Specifically designed to run applications Application licensing types
Per user licensing
Per seat licensing
Site license Installing application on server
Purchase appropriate type and number of licenses
Verify server resources
Install application
Make application available
Provide users access to application
NOS responsible for arbitrating file access
Problem with shared file access
Multiple users simultaneously accessing same data files, same
Page 11 of 16
program files
Sharing Printers
Increases resource management efficiency; reduces costs
Print server
Manages print services Printer attaches to print server
Directly
To convenient network location
All NOSs perform common tasks in
managing printers
To create new printer
Install printer driver
Provides printer availability to users
Ensure appropriate printer queue user rights Networked printers
Appear as icons in Printers folder Client redirector
Determines where print request should transmitted
Network, workstation
Page 12 of 16
Managing System Resources
Limited server system resources
Required by multiple users Modern NOSs capabilities
Maximize server memory, processor, bus, and hard drive use
Accommodates more client requests faster
Improves overall network performance
Memory
Virtual memory can boost total memory available Physical memory: RAM chips
Physical memory required by server varies Task dependent
Virtual memory: stored on hard drive
Page file (paging file, swap file) Managed by operating system
Paging
Moving blocks (pages) from RAM into virtual memory Virtual memory advantages
Easily expands memory available to server applications
Engaged by default Virtual memory disadvantage
Slows operations
Hard drive access versus physical memory access
Page 13 of 16
Multitasking
Execution of multiple tasks at one time
All operating system perform
Does not mean performing more than one operation simultaneously Preemptive multitasking (time sharing: UNIX)
Happens quickly
Appearance of tasks occurring simultaneously
Multiprocessing
Process
Routine of sequential instructions that runs until goal is achieved
Thread
Self-contained; well-defined task within process
Main thread
All processes have one One processor systems
One thread handled at any time
Support use of multiple processors to handle multiple threads Technique to improve response time
Splits tasks among more than one processor
Expedites single instruction completion Symmetric multiprocessing
Splits all operations equally among two or more processors Asymmetric multiprocessing
Assigns each subtask to specific processor Multiprocessing advantage to servers with high processor
usage Page 14 of 16
Windows Server 2008
Released February 2008
Enhancement of Windows Server 2003 GUI (graphical user interface)
Pictorial representation of computer function
NOS GIUs
Enable administrator to manage files, users, groups, security, and printers Enhanced security, reliability, remote
client support, and performance
New server management features
Editions
Standard Edition
Web Edition
Enterprise Edition
Datacenter Edition Popular NOS
Address most network administrator’s needs well
Well-established vendor
Device; program compatibility
Larger market offers technical support General benefits
Offers several general benefits
Offers simple user interfaces Disadvantage
Past criticism for performance, security
Page 15 of 16
Hardware Requirements
Server components
Processing power, memory, and hard drive space Windows Server Catalog
Windows Server 2008 compatible computer components
Available online
Consult it prior to hardware purchases
Page 16 of 16
Memory Model
Addressing schemes
32-bit addressing scheme
64-bit addressing scheme Assigns each application (process)
Own 32-bit memory area
Logical subdivision memory available to server Important Windows Server 2008 feature
Install more server physical memory than allowed in earlier versions Uses virtual memory
NTFS (New Technology File System)
File system
Methods of organizing, managing, and accessing files Through logical structures, software routines
NTFS (New Technology File System)
Installed by default Disk data distribution
Disks divided into allocation units (clusters)
Allocation units combine to form partition Logically separate hard disk storage area
Advantages
Secure, reliable, and allows file compression
Handles massive files
Allow fast access to resources
Used on all Windows operating system versions Since Windows NT
Offers many features Drawback
Cannot be read by older operating systems (Win 98)
Page 17 of 16
Active Directory
Directory service
Originally designed for Windows 2000 Server
Enhanced with Windows Server 2008 Windows Server 2008 network
Workgroup model
Domain model
Workgroups
Peer-to-peer network Decentralized management
Each computer has own database User accounts, security privileges
Significantly more administration effort Practical for small networks
Few users
Simple to design, implement
Domains
Group of users, servers, and other resources
Share centralized account and security information database Client/server network
Page 18 of 16
Active directory
Contains domain databases
Easier to organize and manage resources and security Domains
Domain not confined by geographical boundaries
Domain controllers
Contains directory containing information about
objects in domain Member servers
Do not store directory information
Replication
Process of copying directory data to multiple
domain controllers
OUs (Organizational Units)
Hold multiple objects having similar characteristics
Can be nested Provides allows simpler, more
flexible administration
Trees and Forests OUs
Directory structure above domains
Large organizations use multiple domains
Domain tree
Organizes multiple domains hierarchically
Page 19 of 16
Chapter 2: Network Operating Systems
Contains
Active directory domain
Domains
databases
Easier to organize and
manage resources and
Domain not confined by
security
geographical boundaries
Domain controllers
Contains directory
containing information
about
objects in domain
Member servers
Do not store directory
information
Replication
Process of copying
directory data to
multiple domain
controllers
OUs (Organizational Units)
Hold multiple objects having
similar characteristics
Can be nested Provides
allows simpler, more
flexible administration
Trees and Forests
Active Directory tree
Directory structure
base above OUs
Child domains
domains
Branch off from root domain
Large organizations
Separate groups use
of objects
multiple
with domains
same policies
Domain
Forest tree
A Organizes multiple
collection of one or more
domains hierarchically
domain trees
Root domain Share common schema Domains within
a forest can communicate Domains within same tree Page 20 of 16
Chapter 2: Network Operating Systems
Trust Relationships
Relationship between two domains
One domain allows another domain to authenticate its
users
Active Directory supports two trust relationship types
Two-way transitive trusts
Explicit one-way trusts
Naming Conventions
Active Directory naming (addressing)
conventions
Based on LDAP naming Internet
namespace
Complete hierarchical names database
Used to map IP addresses to hosts’
names Active Directory
namespace
Collection of object names, associated places in Windows Server 2003, Server 2008 network Two namespaces
are compatible
Windows Server 2008 network object
Three different names
DN (distinguished
name): DC
(domain component) and CN
(common name) – long and
complete name
RDN (relative
distinguished name) – unique within
a container
UPN (user principal
name) – like an email address
GUID (globally unique identifier)
128-bit number
Ensures no two objects have
duplicate names
Server Management Page 21 of 16
Chapter 2: Network Operating Systems
UNIX and Linux
Popular NOSs
Provide resource sharing
Older
UNIX developed in 1969
UNIX preceded, led to TCP/IP protocol suite development
Most Internet servers run UNIX
Efficient and flexible
Some difficulty to master UNIX
Not controlled, distributed by single
manufacturer
Some version nonproprietary and freely
distributed
A Brief History of UNIX
Late 1960s: UNIX operating system 1970s
Antitrust laws and AT&T
Anyone could purchase the source
code
New versions of UNIX appeared
System V, BSD
1980s
Rights changes hands, now owned by Novell Open
Group owns UNIX trademark
Varieties of UNIX
Many varieties (flavors, distributions)
Share several features UNIX
operating system
Divided into two main categories
Proprietary
Open source
Proprietary UNIX
Source code unavailable
Available only by purchasing licensed copy from Novell Vendors
Apple Computer: Mac OS X Server Page 22 of 16
Chapter 2: Network Operating Systems
Open source software (freely distributable software)
UNIX GNU, BSD, and Linux
Variety of implementations
Run on wider range of systems
Key difference from proprietary implementations
Software license Two Flavors of
UNIX Solaris
Sun Microsystems
Runs on SPARC-based servers
All commercially supported
operating system benefits
Use: Runs intensive applications
Examples: large, multiterabyte databases, weather prediction systems, and large economic
modeling applications
Linux follows standard UNIX conventions
Highly stable, free
Developed by Linus Torvalds (1991) All UNIX and
Linux versions
Offer host of features
TCP/IP protocol suite
Applications to support networking
infrastructure
Support non-IP protocols like SLIP
and Appletalk
Programs necessary for routing, firewall protection, DNS services, DHCP services Operates over
many different network topologies, physical media
Efficiently and securely handle growth, change, stability
Source code used, thoroughly debugged
Solaris Hardware Requirements
Similar to Windows Server 2003, Server 2008
Key differences
UNIX, Linux operating system can act as workstation or server operating system GUI (graphical
user interface) remains optional
No single “right” server configuration exists
Solaris Hardware Requirements Page 23 of 16
Chapter 2: Network Operating Systems
Linux Hardware Requirements
Linux servers adhere to certain minimum requirements
UNIX Multiprocessing
UNIX and Linux
Support processes and threads
Allocate separate resources (memory space) to each process
When created
Manage access to resources
Advantage: prevents one program from disrupting system
Support symmetric multiprocessing
Different versions support different number of processors
The UNIX Memory Model
Use physical, virtual memory efficiently Allocate
memory area for each application
Share memory between programs when possible Use 32-bit
addressing scheme
Programs access 4 GB memory
Most systems also run on CPUs employing 64-bit addresses
18 exabytes (264 bytes) memory Virtual
memory
Disk partition or file
The UNIX Kernel
Kernel
Core of all UNIX and Linux systems Kernel Page 24 of 16
Chapter 2: Network Operating Systems
UNIX System File and Directory Structure
Hierarchical file system
Disk directories may contain
files, other directories
/boot directory: kernel, system
initialization files
/sbin directory: applications,
services
/var directory: variable data
/home directory: created for new users
UNIX File Systems
Two broad categories
Disk file systems
Network file systems
Disk File Systems
Organizing, managing, accessing files
Through logical structures, software routines Linux native
file system type
ext3: “third extended” file system Solaris
native file system
UFS (UNIX file system)
Network File Systems
Analogous to Windows shares
Attach shared file systems (drives)
From Windows, other UNIX servers
Share files with users on other computers UNIX and
Linux popular remote file system type
Sun Microsystems’ NFS (Network File System)
Open source application implementing Windows SMB, CIFS file
system protocols
Samba
A UNIX and Linux Command Sampler
Many system administrators prefer command line GUI executes
commands
Responds to mouse clicks Command Page 25 of 16
Chapter 2: Network Operating Systems
Most frequently used UNIX command
ls
Provides file information
Stores in file inode (information node)
ls –l command
Access permissions field Files type
designations
Pipe
Direct one command output to input of
another command
Unix: vertical bar ( | )
Figure 9-18 Anatomy of ls –l output
Disadvantages & Advantages of NetworkOperating Systems
Network operating systems diverge into two categories: peer-to-peer networks and client-to-server operating systems. Each of
these methods of tying multiple devices into a given system has its unique advantages from the flexibility of adding new software
and ease of expansion that is the hallmark of client-to-server operating systems, to the ease of setup and inexpensive operating
cost that is main attractor to peer-to-peer connections. Disadvantages arise when networks require troubleshooting as client-to-
server networks often have a dedicated IT staff to handle the potentially expensive problems whereas peer-to-peer networks have
only each other to solve problems large and small
1. Cost Versus Maintenance
Of the two main networking operating systems, a peer-to-peer network is the lowest cost in terms of initial start
up. Users do not need to purchase a centralized server to store data as all information is stored on and
accessed from computers connected to the network. A client-to- server network operating system is of course the
more expensive route as a centralized server is required when the network is first established and will require
Page 26 of 16
a staff or some form of information technology personnel to adequately service it. Cost (an initial
Chapter 2: Network Operating Systems
2. Dependency on the System
Client-to-Server network operating systems depend on the operating system to function. Should the
centralized server go down or malfunction, operations will cease across the entire network. Peer-to-peer systems
have the advantage of an existing operating system for each computer linked into the network to depend on so each
computer can function easily as a separate unit. As information can only be stored on systems linked into the
network in peer-to-peer systems, if a computer does go down the information stored there will not be accessible for the
rest of the network until it is repaired.
3. Versatility
New technology is easily integrated into client-to-server network connections as the operating system is controlled
centrally. Of course when this new technology is integrated into the system, a given staff must then be trained to use the
new technology which can be time consuming and have a few pitfalls as workers integrate the new system into existing
protocols. Peer-to-peer systems depend largely on existing software platforms installed on computers linked to the
network and while systems for the entire network cannot be changed, each user is able to customize a work station to
optimize personal efficiency.
Type of NOS:
Novell Netware
Netware is a Novell network operating system (NOS) providing transparent remote file access, printer sharing and
support for electronic mail and database systems. NetWare virtually runs on any kind of computer system, from PCs to
mainframes. Novell Netware uses five layers of the Open Interconnection model. Layer one is the physical layer,
two is the data link layer and three is the network layer. These are designated as the network layers, addressing the
physical aspects of moving data from one device to another. Layer four is the transport layer, which links the two
subgroups and guarantees that what the network layers have transmitted is in the proper form and usable. Layer five is the
session layer, referred to as the network dialog controller. If at times the network layers do not suffice, layer five
establishes, maintains and synchronizes the interaction among communicative systems.
WIndows NT
Windows NT is actually two products: Windows NT Workstation and Windows NT Server. Our focus is on the
Server, which provides network services designated for business systems. Windows NT Server is the second most
installed network server operating system after its competitor Novell NetWare. Windows NT Server 5.0, renamed as
Windows 2000 Server, appeals to small-to-medium- sized businesses. Windows 2000 Advanced Server is geared to
functioning as a network operating system server and/or an application server.
Page 27 of 16
Chapter 2: Network Operating Systems
Differences in Network Operating Systems
Centralized Management vs. Non-Centralized Management
A peer-to-peer network operating system has no centralized server. Computers connected via a peer-to- peer network share
resources that reside on their individual systems. No extant centralized management system authenticates users or manages
file sharing and storing.
A client/server network operating system involves dedicated clients and servers. The server workstation
acts as a centralized management system, which stores files and processes requests from client workstations. The
server manages client requests and determines which request to allow and when to apply restrictions.
Usability and Expense
Administrator typically install peer-to-peer networks in small businesses or at homes, where users need to
interact with one another. Less expensive to set up than non-centralized options, they do not require the installation of
dedicated server hardware or expensive server security software. However, peer-to-peer networks offer no data security or
protection from external threats (such as viruses and hackers).
Client/server networks can support anywhere from a few dozen to a few hundred thousand users. They offer
intricate security measures, ensuring the data residing on their terminals remains protected from both internal and
external threats. Client/server networks are expensive to set up and manage, as they require high-end hardware and
software systems and one or more qualified network operators to ensure the smooth functioning of processes.
Power and Flexibility
Peer-to-peer networks offer limited scope and performance as compared with client/server networks, although they can
prove useful in tying together users and resources on a local area network (LAN) as quickly and easily as possible. A
client/server network provides increased performance and powerful data management. It allows centralized security
checks, recovery options, expensive peripherals, improved data integrity and file management systems. The server
has enough flexibility to support various types of platforms, systems and client operating software, such as UNIX,
NetWare, Macintosh, Windows NT and Windows 98. A client/server network enables users to access the server
remotely, unlike a peer-to-peer network, which requires access within an office or a home.
Page 28 of 16