Project Report On

Network Operating System

Strength to Client/Server Architecture

Submitted To Submitted By
Mr. Ashish B.Khare Kavita Karki
Asst. Professor MCA Vth Sem (24)

[Colloquium]
Amrapali Institute of Management and Computer Application
Haldwani
 CONTENT SHEET

(1). Introduction

(1.1). Project Introduction

(1.2). Types of Network Operating System
(1.3). Why Client/Server Architecture is Important

(2). Evolution

(2.1). First-Generation
(2.2). Second-Generation
(2.3). Third-Generation

(3). Different Types of NOS

• Artisoft's LANtastic
• Banyan Vines
• Novell's NetWare
• Microsoft's LAN Manager
• Unix
• OS/2

(4). Market Scenario

• Novell Netware
• Current Netware Situation

(5). Services Provided by NOS

(6). NOS Performance in Client/Server Architecture

(7). Conclusion

(8). Reference
(1). Introduction:
Client/server architecture is an application design approach that results in the decomposition
of an information system into a small number of server functions, executing one or
more hardware platforms, that provides commonly used services to a large number of
client functions, executing on one or more different but interconnected hardware
platforms.

Client/server is a computational architecture that involves client processes requesting service

from server processes Client/server computing is the logical extension of modular
programming. In basic client-server architecture, a personal or centralized
application is split into two parts: a client part on a personal platform, and a server
part on a server platform. The terms client and server are used to refer to the
hardware platforms and the application software components. Basic client-server
architecture are normally organized around a local area network (LAN). The whole
assembly is usually described as a PC-LAN, and consists of many PCs for personal
use (personal platforms), plus one or more shared PCs (server platforms). The local
server platforms on these PC-LANs usually provide gateways into enterprise-wide
and external networks, and to the servers on them.

Network Operating System:

A network operating system is a computer operating system that is designed primarily to

support workstation, personal computer, and in some instance, older terminal that
are connected on a local area network. NOS is an operating system that includes
special functions for connecting computers and devices into a local area network
(LAN) or internetworking. Network Operating Systems (NOS) typically are used to
run computers that act as servers. They provide the capabilities required for
network operation.

(1.2). Types Of Network Operating System:

Unlike operating systems, such as Windows that are designed for single users to control one
computer network operating systems (NOS) coordinate the activities of multiple
computers across a network. The network operating system acts as a director to
keep the network running smoothly.

The two major types of network operating systems are:

Peer-to-Peer

Client/Server
Peer-to-Peer Network Operating System:

Peer-to-peer network operating systems allow users to share resources and files located on
their computers and to access shared resources found on other computers. However,
they do not have a file server or a centralized management source. In a peer-to-peer
network, all computers are considered equal; they all have the same abilities to use the
resources available on the network. Peer-to-peer networks are designed primarily for
small to medium local area networks.

In a wired peer-to-peer network the NOS is installed on every networked computer so that
any networked computer can provide resources and services to all other networked
computers. For example, each networked computer can allow other computers to access
its files and use connected printers while it is in use as a workstation. In a wireless peer-
to-peer network, each networked device contains a short-range transceiver that
interfaces with the transceivers of nearby devices or with APs. Like their wired
counterparts, wireless peer-to-peer networks offer file and resource sharing.

AppleShare and Windows for Workgroups are examples of programs that can function as
peer-to-peer network operating systems.

Fig: peer-to-peer network

Advantages of a peer-to-peer network:

Less initial expense - No need for a dedicated server.

Setup - An operating system (such as Windows XP) already in place may only need to be
reconfigured for peer-to-peer operations.

Disadvantages of a peer-to-peer network:

Decentralized - No central repository for files and applications.

Security - Does not provide the security available on a client/server network.

Maintenance is also often more difficult. Because there is no method of centralized
management, there can be many servers to manage (rather than one centralized server), and
many people may have the rights to change the configuration of different server computers. In
the case of wireless peer-to-peer networks, however, an AP may be one node in the network,
allowing users both to share files directly from their hard drives and to access resources from
the servers on the LAN.

2. Client/Server Network Operating System:

Client/server network operating systems allow the network to centralize functions and
applications in one or more dedicated file servers. Individual workstations (clients) have
access to the resources available on the file servers. The network operating system provides
the mechanism to integrate all the components of the network and allow multiple users to
simultaneously share the same resources irrespective of physical location. Novell Netware
and Windows 2000 Server are examples of client/server network operating systems.
A System software of a local area network (LAN) that integrates the network hardware
components, usually adequate for connecting up to 50 workstations. Controls a network and
its message (e.g., packet) traffic and queues, control access by multiple users to network
resources such as files and provides for certain administrative functions, including security.
To keep networks running at optimal performance. Network operating system allows large
businesses to function as a single Unix.

Advantages of a client/server network:

• Centralized - Resources and data security are controlled through the server.

Scalability - Any or all elements can be replaced individually as needs increase.

Flexibility - New technology can be easily integrated into system.

Interoperability - All components (client/network/server) work together.

Accessibility - Server can be accessed remotely and across multiple platforms.

Disadvantages of a client/server network:

Expense - Requires initial investment in dedicated server.

Maintenance - Large networks will require a staff to ensure efficient operation.

Dependence - When server goes down, operations will cease across the network.
(1.3): Client-Server Architecture Importance: To understand why Client/Server
architecture is so important, let us have a look on some traditional computing
architectures:

Centralized Multiuser Architecture (Not a Client/Server Architecture):With mainframe

software architecture all intelligence is within the central host computer. Users interact
with the host through a terminal that captures keystrokes and sends that information to
the host. Mainframe software architectures are not tied to the hardware platform. User
interaction can be done using PCs and UNIX workstations.

This traditional architecture have several advantages such as it is stable, reliable, cost
effective for large number of users, single vendor system, etc. But also have several
disadvantages such as such as its proprietary (incompatible) expensive, license free etc.

File Sharing Architecture (Not Client/Server Architecture): The original PC networks

were based on file sharing architectures, where the server downloads file from the
shared location to the desktop environment. The requested user job then runs in the
desktop environment. This architecture work if shared usage is low, and the volume of
data to be transferred is low.

Client/Server Architecture: This architecture was developed to overcome limitations of file

sharing architecture. In this approach a database server is used to replace file server.
Using a relational database management system (RDBMS), User queries could be
answered easily and directly. Network traffic can also be reduced as query response is
provided rather than total file transfer as in file/server architecture.

Fig: Client/Server Architecture

The basic characteristics of client/server architectures are:

Combination of a client or front-end portion that interacts with the user, and a server or back-
end portion that interacts with the shared resource. The client process contains solution-
specific logic and provides the interface between the user and the rest of the application
system. The server process acts as a software engine that manages shared resources
such as databases, printers, modems, or high-powered processors.

The front-end task and back-end task have fundamentally different requirements for
computing resources such as processor speeds, memory, disk speeds and capacities, and
input/output devices.

The environment is typically heterogeneous and multi Finder. The hardware platform and
operating system of client and server are not usually the same. Client and server
processes communicate through a well-defined set of standard application program
interfaces (API's) and RPC's.

An important characteristic of client-server systems is scalability. They can be scaled

horizontally or vertically. Horizontal scaling means adding or removing client
workstations with only a slight performance impact. Vertical scaling means migrating
to a larger and faster server machine or multi servers.
(2). Evolution:

In this section, review networking products that have been through several generations of
software releases to help provide the best examples of the differences seen with different
generations of network operating systems. Within various environments, it is not uncommon
to find routers or switches that started life under older, monolithic software and later migrated
to more contemporary later generation designs. By reviewing these generations, the positive
effect on stability and operational efficiency is easy to notice and appreciate.

In general, network operating systems can be traced back to three generations of

development, each with distinctively different architectural and design goals.

(2.1). First-Generation Network OS: Monolithic Architecture:

Most of the first-generation network operating systems for routers and switches were
proprietary images running in a flat memory space, often directly from flash memory or
ROM. While supporting multiple processes for protocols, packet handling, and management,
they operated using a cooperative, multitasking model in which each process would run to
completion or until it voluntarily relinquished the CPU.

All of these first-generation network operating systems shared one trait: They eliminated
the risks of running full-size commercial operating systems on embedded hardware. The
primary goal of these early network operating systems were to operate in a small footprint
and to provide speed of operation, while additional features like memory management,
protection, and context switching were either rudimentary or nonexistent. These first-
generation network operating systems helped make networking commercially viable and
were deployed on a wide range of products. The downside was that these systems were
plagued with a host of problems associated with resource management and fault isolation;
a single runaway process could easily consume the processor or cause the entire system to
fail. Such failures were not uncommon in the data networks controlled by older software
and could be triggered by software errors, rogue traffic, and operator errors.
Legacy platforms of the first generation are still seen in networks worldwide, although
they are gradually being pushed into the lowest end of the telecom product lines.

(2.2). Second-Generation Network OS: Control Plane Modularity:

By the mid-1990s, there was a significant increase in the use of data networks worldwide,
which quickly challenged the capacity of existing networks and routers. By this time, it
was becoming evident that embedded platforms could actually run full-size commercial
operating systems, at least on high-end hardware, but with one catch—they could not
sustain packet forwarding with satisfactory data rates. To help solve this issue, a
breakthrough solution was introduced through implementation of a hard separation
between the networking devices control and forwarding planes—an approach that
occurred in the industry's first ASIC-driven routing platform. Forwarding packets entirely
in silicon proved to be viable, clearing the path for next-generation network operating
systems.

Since second-generation network operating systems were now free from handling packet
switching functions, they were able to focus entirely on control plane functions. Unlike
their first-generation counterparts, a second-generation OS could now fully use the
potential of multitasking, multithreading, memory management, and context manipulation
—all making system-wide failures less common. Most core and edge routers installed in
the past few years are running second-generation operating systems, and it is these
systems that are currently responsible for moving the bulk of traffic on the Internet and in
corporate enterprise networks.
(2.3). Third-Generation Network OS: Flexibility, Scalability, and Continuous
Operation:

Although second-generation designs were very successful, the past 10 years have brought
new challenges. Organizations are constantly pressured to deliver high-performance
networks that are flexible, scalable, and reliable, while also lowering operating expenses.
Running multiple "best-in-class" operating systems in multiple terabit routers, Layer 2
switches, and even security appliances across an organization's network, produced a
splintered operational experience where there is no true "network" operating system.
Third-generation network OS are designed to provide a single network operating system
that is flexible enough to be deployed into multiple types and sizes of network and
security devices across an organization's network infrastructure. This single OS must also
achieve continuous operation, so that software failures in the routing code will not affect
the state of the operational network. Meeting this challenge requires availability and
convergence characteristics that go far beyond the hardware redundancy available in
second-generation routers.

Another key goal of third-generation operating systems is the capability to run with zero
downtime during both planned and unplanned events. Drawing on the lesson learned from
previous designs regarding the difficulty of moving from one OS to another, third-
generation operating systems should make the migration path completely transparent to
customers. They should offer an evolutionary, rather than a revolutionary upgrade
experience typical of the retirement process of legacy software designs.
(3). Different Types of Network Operating System:
The client process sends a request to the server. The server interprets the message and then
attempts to fulfill the request. In order to fulfill the request, the server may have to refer
to a knowledge source (database), process data (perform calculations), control a
peripheral, or make an additional request of another server. In much architecture, a
client can make requests of multiple servers and a server can service multiple clients.

The list of network operating systems includes Artisoft's LANtastic, Banyan VINES, Novell's
NetWare and Microsoft's LAN Manager. Some of the main functions of a network
operating system are printer sharing, common file systems, database sharing,
application sharing, managing network name directory and the ability to do
housekeeping for the network's system.

Artisoft's LANtastic:
LANtastic supports a wide variety of PC operating systems like Windows NT 4.0/2000/2003
(Workstation and/or Server), and Windows XP. It comes with an enhanced multi-platform
support. The installation and operation of the system is fast and user friendly, along with an
improved interface that allows all networked PCs to be able to communicate by just using the
Chat feature. Users are not required to employ a dedicated server or a full-time network
manager because the system is simple and easy to maintain.

Banyan VINES:
Banyan Virtual Integrated Network Service (VINES) is a network operating system based on
proprietary protocol family. The protocol is basically derived from Xerox Network Systems
(XNS) protocols, where it uses a client-server architecture that enables clients to request
specified services like file and printer access from servers.

Novell's NetWare:
This network operating system is a protocol suite designed based on the XNS protocol
architecture. It provides comprehensive support to most of the desktop operating systems in
the market, including DOS, Windows, Macintosh, OS/2 and UNIX. Novell also supports the
local area networks and asynchronous wide area communications.

Microsoft's LAN Manager: LAN Manager is a

network operating system by Microsoft that works as a server application. It runs under
Microsoft OS/2, and was developed in conjunction with 3Com. The file server may
concurrently be used for other tasks like database services. In other words, the system
provides a good multi-tasking function. It also supports most desktop operating systems
like DOS, Windows and OS/2 clients. Currently, the LAN Manager feature has been
superseded by Microsoft Windows NT Server and most parts of the LAN Manager are
being used in the Windows NT and Windows 2000.

UNIX: is an operating system that was developed by some of the members of the Multics
team at the bell labs starting in the late 1960's, many of who also helped create the C
programming language. Today, Unix is not just the work of a couple of programmers, many
other organizations, institutes, and various other individuals have contributed significant
additions to Unix and its variants, making it a widely used and popular operating system
today.
LINUX:

LINUX refers to the family of Unix-like computer operating systems using the Linux kernel.
Linux can be installed on a wide variety of computer hardware, ranging from mobile phones,
tablet computers and video game consoles, to mainframes and supercomputers. Linux is the
leading server OS, accounting for more than 50% of installations and runs the top 10 fastest
supercomputers in the world. Desktop use of Linux has increased in recent years, partly
owing to the popular Ubuntu, Fedora, and openSUSE distributions and the emergence of
netbooks and smartphones running an embedded Linux.

The development of Linux is one of the most prominent examples of free and open source
software collaboration; typically all the underlying source code can be used, freely modified,
and redistributed, both commercially and non-commercially, by anyone under licenses such
as the GNU General Public License. Typically Linux is packaged in a format known as a
Linux distribution for desktop and server use. Linux distributions include the Linux kernel
and all of the supporting software required to run a complete system, such as utilities and
libraries, the X Window System, the GNOME and KDE desktop environments, and the
Apache HTTP Server. Commonly used applications with desktop Linux systems include the
Mozilla Firefox web-browser, the OpenOffice.org office application suite and the GIMP
image editor.

OS/2:

Jointly developed by Microsoft Corp. and IBM to operate with Intel Corp.'s microprocessors,
OS/2 was originally a 16-bit operating system that was designed to work with 286 processors
and first introduced in 1987. OS/2 later became a graphical interface similar to Windows but
also supported a command line. In fact, many OS/2 and DOS commands are the same.

In 1992, a new 32-bit version was released to operate with 386 and above PCs and at this time
was now solely an IBM product. Later in 1994, IBM released a version it called OS/2 Warp
that included Internet access and additional features. At the same time Microsoft was working
on OS/2 version 3.0; however, it later became Microsoft Windows NT.

OS/2 never became as popular as the other Microsoft operating systems, and software
developers never created a substantial number of programs to run primarily under OS/2.
Although some computer experts say later versions of OS/2 are superior to Windows,
Windows and the number of products created for it still greatly outnumber OS/2 programs.

IBM officially announces on July 14, 2005 that all sales of OS/2 will end on December 23,
2005 and that all support from IBM for OS/2 will end on December 16, 2005.

Windows NT:

Windows NT is a family of operating systems produced by Microsoft, the first version of

which was released in July 1993. It was a powerful high-level-language-based, processor-
independent, multiprocessing, multiuser operating system with features comparable to Unix.
It was intended to complement consumer versions of Windows that were based on MS-DOS.
NT was the first fully 32-bit version of Windows, whereas its consumer-oriented
counterparts, Windows 3.1x and Windows 9x, were 16-bit/32-bit hybrids. Windows 2000,
Windows XP, Windows Server 2003, Windows Vista, Windows Home Server, Windows
Server 2008 and Windows 7 are based on Windows NT, although they are not branded as
Windows NT.

A main design goal of NT was hardware and software portability. Various versions of NT
family operating systems have been released for a variety of processor architectures, initially
Intel IA-32, MIPS R3000/R4000 and Alpha, with PowerPC, Itanium and AMD64 supported
in later releases. The idea was to have a common code base with a custom Hardware
Abstraction Layer (HAL) for each platform.

The table shows a short list of some of the server OSes available today. Most of these are
based on a Unix core.

Server Operating Systems

Hardware
Operating System Company No. of processors Appropriate for:
Platform

4 (Server)
Windows 2000 Server/Advanced Small, medium and
Microsoft Intel/AMD 8 (Advanced)
Server/Datacentre large servers
32 (Datacentre)

4 (Standard)
Intel/AMD & IA-
Up to 8
Windows Server 2003 R2 64, Opteron for 64-
(Enterprise) Small, medium and
Standard/Enterprise/Datacentre/Web Microsoft bit versions of
Minimum 8, large servers
Server/Small Business Windows Server
Maximum 64
2003
(Datacentre)

32 (Linux is
Linux (Red Hat, Mandrake, Debian, Many (esp. Small to large
Open Source readily used on
SuSE, etc.) Intel/AMD) servers
more than 4 CPUs)

x86, Alpha, IA-64,

Small to large
FreeBSD 7.0 Open Source PC-98 and 4
servers
UltraSPARC

PowerPC with a
2 (4 available Small to medium
Mac OSX Server v10.4 Apple G3, G4, or G5
later) servers
processor (Apple)

Medium to large
NetWare 6.5 Novell Intel/AMD 32
servers

Sparc, Intel x64 or Medium to

Solaris 10 Sun Microsystems 128
x86 enterprise servers

PA-RISC, Intel
HP-UX 11i v1.6 & HP-UX 11i v2 Hewlett-Packard 64 Enterprise servers
Itanium

IRIX 6.5 SGI MIPS 64 Enterprise servers

PowerPC
AIX 5L 5.2 IBM 32 Enterprise servers
(RS/6000)
(4). Market Scenario:
Each operating system has its strengths and weaknesses, and its use may depend on your level
of technical competence.

Windows 2000 Professional, Server and Advanced Server can be readily used as small
business servers. The strength of Windows lies in the familiarity of the interface; wide
support – there is a mass of third party development for the platform, a reasonable price tag
and a plentiful supply of available expertise.

The weaknesses of these OSes is the need for user-based licensing. Additionally, significant
maintenance for security resources is required (there is a history of viruses infecting IIS in
particular).

Linux and FreeBSD actually cover a large range of products. The purchase price ranges from
freely downloadable to packaged and supported corporate products costing hundreds of
dollars. Linux, in particular, comes in a huge variety of distributions; some act and look much
like Windows; others can be used to build an appliance server (see below) that are totally
administered through a Web or other interfaces. The core, or Kernel, of the operating systems
are the same, however (although there may be variations in the version of the kernel used in a
given distribution).

Mac OS X shares origins with FreeBSD, and has many of the same features and stability. The
interface is very Macintosh, and you need to buy Apple hardware to use it. There aren't many
third party applications for it as yet. It comes with an unlimited user license.

In contrast to Mac OS X, Novell NetWare 6 is a very mature server OS. It was long sidelined
as purely a 'file and print server', and missed out on picking up on a lot of the application
server business. It still makes a very capable workgroup or enterprise server. Its file and Web
services are first-rate, and it has a wide range of management interfaces, including a Web
interface. Unfortunately, there are few third-party applications for it, installation is quite
technical and it's not cheap.

NetWare is a network operating system developed by Novell, Inc. It initially used

cooperative multitasking to run various services on a personal computer, with network
protocols based on the archetypal Xerox Network Systems stack. Novell superseded NetWare
with Open Enterprise Server (OES) from 2005. The latest version of NetWare is v6.5 Support
Pack 8, which is identical to OES 2 SP1, NetWare Kernel.

NetWare provides transparent remote file access and numerous other distributed network
services, including printer sharing and support for various applications such as electronic mail
transfer and database access. NetWare specifies the upper five layers of the OSI reference
model and, and runs on any media-access protocol (Layer 2). In addition, NetWare runs on
virtually any kind of computer system, from PCs to mainframes. NetWare and its supporting
protocols often coexist on the same physical channel with many other popular protocols,
including TCP/IP and AppleTalk .

Novell NetWare, introduced in the early 1980s based on Xerox Network Systems (XNS), is
based on a client-server architecture. Clients (sometimes called workstations) request
services, such as file and printer access, from servers. NetWare's client/server architecture
supports remote access that is transparent to users through remote procedure calls. A remote
procedure call begins when the local computer program running on the client sends a
procedure call to the remote server. The server then executes the remote procedure call and
returns the requested information to the local client.

The most popular protocols in the Novell NetWare suite are:

IPX: Internetwork Packet Exchange protocol- Routing and networking protocol at layer 3.
When a device to be communicated with is located on a different network, IPX routes the
information to the destination through any intermediate networks . IPX is similar to IP
(Internet Protocol) in the TCP/IP suite.

SPX: Sequenced Packet Exchange protocol - Control protocol at the transport layer (layer 3)
for reliable, connection-oriented datagram transmission. SPX is similar to TCP in the TCP/IP
suite.

NCP: Network Core Protocol is a series of server routines designed to satisfy application
requests coming from, for example, the NetWare shell. Services provided by NCP include file
access, printer access, name management, accounting, security, and file synchronization.

NetBIOS: Network Basic Input/output System(NetBIOS) session-layer interface

specification from IBM and Microsoft. NetWare's NetBIOS emulation software allows
programs written to the industry-standard NetBIOS interface to run within the NetWare
system .

NetWare application-layer services: NetWare Message Handling Service(NetWare MHS),

Btrieve, NetWare Loadable Modules (NLMs), and various IBM connectivity features.
NetWare MHS is a message delivery system that provides electronic mail transport. Btrieve is
Novell's implementation of the binary tree database access mechanism. NLMs are
implemented as add-on modules that attach into the NetWare system. NLMs for alternate
protocol stacks, communication services, database services, and many other services are
currently available from Novell and third parties.

Since the NetWare 5.0 (the current version of NetWare is 6.5), all Novell network services
can be run on top of TCP/IP. There, IPS and SPX became Novell legacy network and
transport layer protocols.
Current NetWare situation:

As of 2010 some organizations still use Novell NetWare, but its ongoing decline in popularity
began in the mid-1990s. Modern (2009) NetWare and OES installations are used by larger
organizations that may need the added flexibility they provide.

Microsoft successfully shifted market share away from NetWare products toward their own in
the late-1990s. Microsoft's more aggressive marketing was aimed directly to management
through major magazines; Novell NetWare's was through IT specialist magazines with
distribution limited to select IT personnel.

Novell did not adapt their pricing structure accordingly and NetWare sales suffered at the
hands of those corporate decision makers whose valuation was based on initial licensing fees.
As a result organizations that still use NetWare, eDirectory, and Novell software often have a
hybrid infrastructure of NetWare, Linux, and Windows servers.

NetWare dominated the network operating system (NOS) market from the mid-80s through
the mid- to late-90s due to its extremely high performance relative to other NOS technologies.
Most benchmarks during this period demonstrated a 5:1 to 10:1 performance advantage over
products from Microsoft, Banyan, and others.

Many quantitative studies of free / open source software focus on topics including market
share and reliability, with numerous studies specifically examining Linux. The Linux market
is growing rapidly, and the revenue of servers, desktops, and packaged software running
Linux was expected to exceed $35.7 billion by 2008.

IDC’s Q1 2007 report indicated that Linux held 12.7% of the overall server market at that
time. This estimate was based on the number of Linux servers sold by various companies and
did not include server hardware purchased separately and had Linux installed on it later. In
September 2008 Microsoft CEO Steve Ballmer admitted that 60% of web-servers run Linux
versus 40% that run Windows Server.
 Fig: OS Shipments With PC Systems Worldwide – Market Share

The Microsoft Disk Operating System (DOS) and the windowing system that runs on top of
it, Microsoft Windows 3.x, are very nearly ubiquitous in the PC environment. Almost every
PC ever made has been bundled with some flavor of DOS (including some compatible non-
Microsoft versions such as products from IBM and Digital Research). Since the introduction
of Microsoft Windows 3.0, almost all PC’s are also bundled with Windows. Windows 9x and
Windows NT have replaced DOS and Windows 3.x see Figure in recent years in bundles
with new machines.
(5). Services Provided by Network Operating System:

The NOS is the "brain" of the entire network, acting as the command center and enabling the
network hardware and software to function as one cohesive system.

In a client-server network the NOS runs on a computer called the network server. The server
must be a specific type of computer. For example, the most commonly used client-server
version of the NetWare NOS runs on Intel-based computers.

The client part of a client-server network is any other network device or process that makes
requests to use server resources and services. For example, network users at workstations
request the use of services and resources though client software, which runs in the
workstation and communicates with the NOS in the server by means of a common protocol.

Fig: Services Provided by NOS in Client Site.

"Resources" generally refers to physical devices that an application may need to access:
hardware such as hard disks, random access memory (RAM), printers, and modems. The
network file system is also a server resource. The NOS manages access to all these server
resources.

A client-server NOS is responsible for coordinating the use of all resources and services
available from the server on which it is running. NOS is generally reserved for software that
enhances a basic operating system by adding networking features.
A server-based network operating system provides networking support for multiple
simultaneous users, each with the ability to access network resources, as well as security and
other administrative functions.

Fig: Services Provided by NOS in Server Site.

The NOS also provides many "services," which are tasks performed or offered by a server
such as coordinating file access and file sharing (including file and record locking), managing
server memory, managing data security, scheduling tasks for processing, coordinating printer
access, and managing internetwork communications.

Among the most important functions performed by a client-server NOS are ensuring the
reliability of data stored on the server and managing server security.
Network Operating System Functions are defined below.

(5.1). File and print sharing: File sharing involves setting up a common storage point for a
company's documents - a network drive, as it were. Print sharing allows multiple computers
to use a single printer. Windows 95, 98 and ME do have file and print sharing, but are not
recommended for use as server OSes.

(5.2). Web site services: A hypertext transfer protocol (HTTP) server is included with many
server OSes, either via an integrated application, or other HTTP applications such as the
Apache open source server. Some OSes also come with more advanced features, such as
database integration (so you can dynamically build Web pages based on information in a
database), personalization and scripting. The world's most popular HTTP server application,
Apache, comes with just about every version of UNIX and also runs on Windows. Microsoft
provides Internet Information Server (IIS) for Windows platforms.

(5.3). Account administration for users: User management and support for Logon and
Logoff.

(5.4). Security: Security features such as authentication, authorization, logon restriction and
access control. On a NetWare client-server network, you "log on" to the network server from
the workstation. To log on, you provide your user name and password—also known as a login
—to the server. If your user name and password are valid, the server authenticates you and
allows you access to all network services and resources to which you have been granted
rights. As long as you have proper network rights, the client-server NOS provides the services
or resources requested by the applications running on your workstation.

(5.5). Installed Components:

• Client functionality
• Server functionality
(6). Network Operating System Performance in Client/Server Architecture:

A network operating system (NOS) is a computer operating system that is designed for
network use.
Usually a NOS is a complete operating system with file, task and job management. However,
with some earlier operating systems, it was a separate component that enhanced a basic non-
networking operating system by adding networking capabilities. Examples include Novell's
Netware and Artisoft's LANtastic.
A variation on the client-server network is the server-based network or thin client-server
network. This kind of network also consists of servers and clients, but the relationship
between client and server is different. Thin clients are similar to terminals connected to
mainframes: the bulk of the processing is performed by the server and the client presents the
interface. Unlike mainframe terminals, however, thin clients are connected to a network, not
directly to the server, which means the client does not have to be physically near the server.

The term "thin client" usually refers to a specialized PC that possesses little computing power
and is optimized for network connections. Windows-based terminal (WBT) and network
computer (NC) are two terms often used interchangeably with thin client. These machines are
usually devoid of floppy drives, expansion slots, and hard disks; consequently, the "box" or
central processing unit is much smaller than that of a conventional PC.

The "thin" in thin client refers both to the client's reduced processing capabilities and to the
amount of traffic generated between client and server. In a typical thin-client environment,
only the keystrokes, mouse movements, and screen updates travel across the connection. (The
term "thin" is also used generically to describe any computing process or component that uses
minimal resources.)
Fig: Thin clients range from complete dependence on the server to the autonomous PC,
which can both run on its own applications and act as a terminal.

Figure shows where clients fall on the "thinness" continuum: mainframe terminals are the
thinnest of all, followed by thin clients and conventional PCs. Thin clients are "fatter" than
mainframe terminals because they run some software locally a scaled-back operating system,
a browser, and a network client but they do not store files or run any other applications. PCs,
on the other hand, can either be fully autonomous—running all applications and storing all
files locally or they can run browser or terminal-emulation software to function as thin clients.

Unlike mainframe terminals, which show text-only, platform-specific screens, thin clients
display the familiar Windows desktop and icons. Furthermore, the Windows display remains
consistent even when using non-Windows applications, so you do not have to learn new
interfaces in heterogeneous network environments.

Server-based computing usually involves "server farms," which are groups of interconnected
servers that function as one. Thin clients link to the farm instead of a particular server. If a
single server fails, the other servers in the farm automatically take over the functions of the
failed server so that work is not interrupted and data is not lost.

The two primary protocols for thin-client computing are remote display protocol (RDP) and
independent computing architecture (ICA). RDP was developed by Microsoft for its Terminal
Server and ICA is Citrix technology. Both protocols separate the application logic from the
user interface; that is, they pick out the part of the application that interacts with you such as
keyboard and mouse input and screens. Only the user interface is sent to the client, leaving the
rest of the application to run on the server. This method drastically reduces network traffic
and client hardware requirements. ICA clients, for example, can have processors as slow as an
Intel 286 and connection speeds as low as 14.4 kilobits per second (Kbps).

Although RDP is the older protocol, ICA has become the de facto standard for server-based
computing. ICA presents some distinct advantages over RDP, not the least of which is ICA's
platform independence. ICA transmits the user interface over all standard networking
protocols—TCP/IP, IPX, SPX, PPP, NetBEUI, and NetBIOS—whereas RDP supports only
TCP/IP. ICA also supports all standard clients from Windows to UNIX to Macintosh, but
RDP can be used only with Windows 3.11 and later. Furthermore, RDP is a streaming
protocol that continuously uses bandwidth while the client is connected, whereas ICA sends
packets over the network only when the mouse or keyboard is in use. As a result, most
network administrators run ICA on top of RDP to obtain the best functionality.

Server-based computing is best used in environments where only a few applications are
needed or when many people will be using the same machine, such as in shift work. For
example, if you use only a spreadsheet, a word processor, and e-mail, a thin client may be an
ideal solution. Likewise, if the applications rely on databases and directories that are already
server-based, such as with airline reservations or patient charts, thin-client computing might
be a good choice. Networks with many different platforms can also benefit from server-based
computing: you can directly access UNIX, Macintosh, mainframe, or other non-Windows
applications via ICA without the mediation of cumbersome translation applications. If,
however, you need to use high-end applications such as desktop publishing, graphics, or
computer-aided design, the conventional PC with its local computing power provides the only
viable option.

Thin-client computing has several other advantages. Because of their simplicity, thin clients
are easier for an IT staff to maintain: users cannot tamper with the settings or introduce
flawed or virus-infected software into the system. The server-centric model also allows
upgrades to be performed at the server level instead of the client level, which is much less
time consuming and costly than updating individual PCs. Thin clients typically do not
become obsolete as quickly as their fatter counterparts—the servers will, but they are fewer in
number and therefore easier to upgrade or replace. Furthermore, thin clients are less likely to
be stolen: because they cannot function without a server, they are useless in a home
environment.

Disadvantages of thin clients include reduced computing power, which makes them practical
only in limited circumstances, and absolute reliance on the network. With conventional PCs
users can run applications locally, so when the network goes down, they do not necessarily
experience work stoppage. On the other hand, the slightest power outage can cripple a thin-
client network for long time: after power is restored, all the clients request the initial kernel
from the server at the same time. Also, it is difficult if not impossible to customize a thin
client. If you need to install a scanner or other peripheral device, a thin client cannot
accommodate it (printers are supported). Furthermore, you cannot customize the look and feel
of your desktop, which for some may be disheartening or frustrating.
(7). Conclusion:
Today, almost every consumer operating system qualifies as a NOS. This is in large part due
to the popularity of the Internet and the consequent need to support the Internet protocol suite.
Developing a flexible, long lasting, and high quality network OS takes time, significant
investment, and in-depth expertise. Developers of modern network operating systems have
firsthand knowledge of what has worked well in older network OS and what could be
improved on, providing a foundation that can gracefully evolve to support new needs in
scaling, adoption across many platforms, and rich integration of new features and functions.

In a peer-to-peer network, such as Microsoft Windows 98 or XP, in which each host can also
be a server, the operating system might still be considered a network operating system, but it is
more light weight than a full-blown NOS.

The Microsoft Windows operating systems did not initially support networking. Thus, Novell
NetWare was introduced and became the first popular network operating system for personal
computers. Windows 95 and Windows for Workgroups were Microsoft's first network
operating system products.

To ensure that organizations can meet their business imperatives, today's third-generation
network OS includes operationally critical features like flexibility, the ability to power a wide
range of platforms, nonstop operation capabilities, and an open software platform.

(8). Reference:
[1]. www.eHOW.com
[2]. About,Com:Wireless/Networking.
[3]. www.computerhope.com/jagron/n/nos.htm, [4].
en.wikipedia.org/wiki/Network_Operating_System.
[4]. Fcit.usf.edu/network/chap6/chap6.html, Produced by the Florida Center for Instructional
Technology College of Education, University of South Florida ©1997-2009, Server Operating
Systems - PC World.htm
[5]. www.amswers.com/topic/network-operating-system.
[6]. Network Operating System Evolution: Juniper Network JUNOS:
whitepapers.techrepublic,com.com/abstract.aspx?docid=1855341.
[7]. f.netline.junipermarketing.com/netline000s/?msg=featured…