Network Operating Systems - NOS Architecture

Introduction

A Network Operating System (NOS) is an operating system designed to manage network resources and provide services to multiple computers connected over a network. Unlike a standalone OS that manages only local resources, a NOS coordinates file sharing, printer access, user authentication, and communication across the network.

Think of a NOS as the manager of an office building. Individual offices (computers) function independently, but the building manager (NOS) handles shared resources — the conference rooms (shared printers), the document archive (file server), the security desk (authentication), and the mail room (email services). Each computer retains its own local OS but relies on the NOS for networked services.

NOS vs. Distributed OS vs. Standalone OS

Understanding the distinction is important:

In a NOS, users explicitly access remote resources (map a network drive, connect to a print server). In a distributed OS, the system hides the network — users see a single unified system.

NOS Architecture

Client-Server Model

The dominant NOS architecture. Dedicated servers provide services; client machines request them.

Server types:

• File Server: Stores and manages shared files (permissions, locking, versioning)
• Print Server: Manages print queues and distributes jobs to printers
• Authentication Server: Validates user credentials (Active Directory, LDAP)
• Application Server: Runs shared applications (databases, email)
• DNS Server: Resolves hostnames to IP addresses
• DHCP Server: Assigns IP addresses to clients automatically

Peer-to-Peer Model

Every machine is both client and server. Resources are shared directly between peers without centralized servers.

Advantages: No single point of failure, easy setup, no dedicated server cost Disadvantages: Difficult to manage at scale, security inconsistencies, no centralized administration

Typical use: Small offices (under 10 machines), home networks, file-sharing applications.

Core NOS Services

1. File Sharing and Management

The most fundamental NOS service. Allows users on different machines to access shared files as if they were local.

Implementation details:

• Server exports directories (shares) with specified permissions
• Clients mount/map network shares to local drive letters or mount points
• File locking prevents simultaneous writes that could corrupt data
• Caching at client side improves performance for frequently accessed files

2. User Authentication and Directory Services

Centralized authentication means users have one account that works across all network resources.

Active Directory (Windows):

• Hierarchical database of users, computers, and policies
• Kerberos-based authentication (ticket-based, no passwords sent over network)
• Group Policy Objects (GPO) enforce configurations across all machines
• Organizational Units (OU) structure for departmental management

LDAP (Lightweight Directory Access Protocol):

• Protocol for accessing directory services
• Used by both Windows (AD) and Linux (OpenLDAP) environments
• Stores user info: username, password hash, email, group memberships

3. Print Services

Centralized print management eliminates the need to install printer drivers on every client:

• Print jobs queued at server
• Priority and quota management
• Automatic driver distribution to clients
• Print accounting (who printed what, when, how much)

4. Network Security

• Firewall management: Control traffic between network segments
• VPN services: Secure remote access for off-site users
• Intrusion Detection: Monitor for suspicious network activity
• Certificate services: Issue and manage SSL/TLS certificates

Major NOS Examples

Windows Server

The most widely deployed NOS in enterprise environments.

Key components:

• Active Directory Domain Services (AD DS)
• Group Policy for centralized management
• NTFS permissions + Share permissions (two-layer security)
• Hyper-V for virtualization
• Remote Desktop Services for thin-client access
• IIS for web hosting

Linux-based NOS

Linux servers provide equivalent services using open-source software:

• Samba: File/print sharing compatible with Windows clients (SMB protocol)
• OpenLDAP: Directory services
• NFS: Native Linux file sharing
• CUPS: Print server
• FreeRADIUS: Network authentication

Historical: Novell NetWare

Dominated enterprise networking in the 1980s-90s. Introduced many concepts now standard:

• Novell Directory Services (NDS) — precursor to Active Directory
• Superior file service performance (dedicated file server OS)
• Declined as Windows Server and Linux matured

NOS Protocols

NOS Administration Tasks

A network administrator managing a NOS handles:

1. User management: Creating accounts, setting passwords, assigning groups
2. Permission management: Controlling who accesses what resources
3. Backup and recovery: Ensuring data survives hardware failures
4. Performance monitoring: Tracking server load, network bandwidth, storage usage
5. Security updates: Patching vulnerabilities before exploitation
6. Capacity planning: Predicting when hardware upgrades are needed

Modern Evolution

Traditional NOS concepts have evolved:

• Cloud directories: Azure AD, Google Workspace replace on-premise directory servers
• Zero-trust networking: Every access verified, no implicit trust from being "on the network"
• Software-defined networking: Network configuration managed as code
• Identity-as-a-Service: Okta, Auth0 replace on-premise authentication servers

Key Takeaways

• A NOS extends standalone OS capabilities to manage shared network resources
• Client-server is the dominant model for enterprise networks (centralized control)
• Core services: file sharing, authentication, printing, security
• Users explicitly access remote resources (unlike distributed OS which hides the network)
• Windows Server with Active Directory dominates enterprise NOS deployments
• Modern cloud services are replacing many traditional NOS functions