Term Paper

Of
Network Operating
System (INT 406)

Topic – Novell Netware

Services

SUBMITTED TO:
SUBMITTED BY:
Mr. Lund
 Acknowledgement

With honestly and loyalty I acknowledge that this term paper contains my dedication and
hard work. I have worked on this every single day since it has been issued to me. I would
like to express my heartiest gratitude to all those humble souls who gave me even their
least possible effort to complete the term paper.

Firstly, I would like to thank my highly revered and experienced teacher Mr. Lund for
guiding me regarding the content of my term paper. He lighted my vision and directed me
in a right manner.
Table of Contents –

 What is Novell Netware?

 The rise of NetWare
 Strategic mistakes
 What is Services for Netware?
 How Services for Netware Works?
 Services provided by Novell Netware
 References
Novell Netware 

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

used cooperative multitasking to run various services on a personal computer.
NetWare has been superseded by Open Enterprise Server (OES). The latest version of
NetWare is v6.5 Support Pack 8, which is identical to OES 2 SP1, NetWare Kernel.
NetWare evolved from a very simple
concept file sharing instead of disk sharing. In 1983 when the first versions of NetWare
were designed, all other competing products were based on the concept of providing
shared direct disk access. Novell's alternative approach was validated by IBM in 1984
and helped promote their product.
With Novell NetWare, disk space was shared in the form of
NetWare volumes, comparable to DOS volumes. Clients running MS-DOS would run a
special terminate and stay resident (TSR) program that allowed them to map a local drive
letter to a NetWare volume. Clients had to log in to a server in order to be allowed to map
volumes, and access could be restricted according to the login name. Similarly, they
could connect to shared printers on the dedicated server, and print as if the printer was
connected locally.
NetWare was based on the NetWare Core Protocol (NCP), which is a
packet-based protocol that enables a client to send requests to and receive replies from a
NetWare server. Initially NCP was directly tied to the IPX/SPX protocol, and NetWare
communicated natively using only IPX/SPX.

The Rise of NetWare 

The popular use and growth of Novell NetWare began in 1985 with the simultaneous
release of NetWare 286 2.0a and the Intel 80286 16-bit processor. The 80286 CPU
featured a new 16-bit protected mode that provided access to up to 16 MB RAM as well
as new mechanisms to aid multi-tasking. Prior to the 80286 CPU servers were based on
the Intel 8086/8088 8/16-bit processors, which were limited to an address space of 1MB
with not more than 640 KB of directly addressable RAM.
The combination of a higher 16 MB
RAM limit, 80286 processor feature utilization, and 256 MB NetWare volume size limit
allowed reliable, cost-effective server-based local area networks to be built for the first
time. The 16 MB RAM limit was especially important, since it made enough RAM
available for disk caching to significantly improve performance. This became the key to
Novell's performance while also allowing larger networks to be built.
Strategic mistakes 

Novell's strategy with NetWare 286 2.x and 3.x was very successful before the arrival
of Windows NTServer, Novell claimed 90% of the market for PC based servers.

While the design of NetWare 3.x and later involved a DOS partition to load NetWare
server files, this feature became a liability as new users preferred the Windows graphical
interface to learning DOS commands necessary to build and control a NetWare server.
Novell could have eliminated this technical liability by retaining the design of NetWare
286, which installed the server file into a Novell partition and allowed the server to boot
from the Novell partition without creating a bootable DOS partition. Novell finally added
support for this in a Support Pack for NetWare 6.5.

What is Services for Netware 

Novell NetWare once held the greatest market share for Intel-based computers. Today, it
is no longer dominant, but it still has a presence in many network environments. Because
of this, ever since Windows NT 3.5, Microsoft has built services into the operating
system that allow the two environments to communicate.

Windows Server 2003, and its client system, Windows XP, continue to provide some
Inter-operability services for NetWare, namely Client Service for NetWare (CSNW),
which is built into the operating system. In addition, there are several add-on and third-
party solutions.

How Services for Netware Works 

Directory Synchronization Services -

Using Directory Synchronization Services (MSDSS) an organization can retain an

existing Novell directory in an environment that includes computers running Windows
Server 2003 and Active Directory. MSDSS synchronization enables you to choose-

• One-way synchronization to centralize directory management from Active

Directory.
 • Two-way synchronization to manage data from either Active Directory or a
Novell directory.

File Migration Utility

The File Migration Utility (FMU) enables you to migrate files from NetWare servers to
Windows Server 2003. FMU can copy files from multiple NetWare file servers to
multiple file servers running Windows Server 2003.

FMU is integrated with MSDSS and enables the migration of large numbers of data files
from all versions of NetWare over to Windows Server 2003, while preserving unique
file-security permissions during the migration. In addition, users can access their files
during the migration process.

Before using FMU to translate the NDS, eDirectory, or Bindery file system rights and
permissions to the equivalent rights and permissions in the NTFS file system, you must
run a one-time migration of NDS or Bindery directory objects to Active Directory. This
operation creates the mapping file used by FMU to map user rights to folders. After a
scan confirms that all files, subdirectories, and permissions will migrate successfully, you
can perform the migration process. Each source directory and file is copied to the
selected target. Each migrated trustee is translated with its associated rights to the
equivalent NTFS permissions and then added to the security descriptor for the migrated
directory or file.

For each NDS or Bindery volume, FMU calculates the effective rights, starting at the
root, and tracks inheritance and filters as the migration continues through the tree. Like
Novell NetWare, Microsoft Windows secures folders and files by controlling group and
user access. Windows security is supported through the NTFS file system. To help
preserve security on transferred NetWare files, you must transfer the NetWare files to an
NTFS volume, where the effective rights of the NetWare files are converted to
permissions.

After you have performed the one-time migration and selected the option to migrate files,
a migration log will be created that can be used later by FMU. This migration log serves
as a mapping file that maps user objects in NDS to Active Directory.

MSDSS -->
The following sections summarize the synchronization methods that are available with
Directory Synchronization Services (MSDSS):

Forward Synchronization –
The process of synchronizing data from Active Directory to Novell directories is referred
to as forward synchronization. The forward synchronization process efficiently queries
Active Directory for any new objects and alterations to existing objects. If an existing
object is modified, only its changes, not the entire object, are synchronized with NDS,
eDirectory, or Bindery directory services objects. If a new object is created, then only the
new object and its attributes are synchronized with NDS, eDirectory.

Reverse Synchronization –

The process of synchronizing data from Novell directories to Active Directory is referred
to as reverse synchronization. Reverse synchronization is less efficient than forward
synchronization. This means that network utilization during reverse synchronization is
higher than it is during forward synchronization.

Only changed objects and newly created objects in NDS are copied to Active Directory.

Because network utilization during reverse synchronization can be higher, it should be

scheduled to run less frequently than forward synchronization.

One-Way Synchronization –

Using one-way synchronization, you can deploy Active Directory in a Novell

environment without replacing existing directories or having to manage two directories.
This enables you to:

• Consolidate network management where multiple directories are required.

• Manage accounts from a single directory.

• Use directory-enabled applications, devices, and services based on Active

Directory.

Setting up a one-way synchronization session provides an administrator with a central

directory management solution and supports additions or modifications to NDS,
eDirectory, or Bindery directory services objects from Active Directory only.

Two-Way Synchronization -

Using two-way synchronization, you can create or change objects in either Active
Directory or NDS and the partner directory will be updated at the next scheduled
synchronization.

You can use two-way synchronization to enable interoperability between NDS and
Active Directory and to maintain an existing NDS directory and add Active Directory.
Scheduled Synchronization -

During a scheduled synchronization, changes from one directory are replicated to another
directory at scheduled intervals that are set by an administrator. The default
interval for forward synchronization is every 15 minutes, 24 hours a day. The
default interval for reverse synchronization is every hour, from midnight to
06:00. If a two-way synchronization session has been configured, you can define
a separate schedule for each direction of the synchronization.

Manual Synchronization -

When you manually synchronize directories, you have the option of copying recent
changes from one directory to another immediately, without waiting for the next
scheduled synchronization.

Usually, it is safe to let synchronization occur during the normally scheduled times.
However, a security-related situation might call for an immediate manual
synchronization.

Synchronization Filtering –

Using synchronization filtering, administrators can define an explicit set of object types
within a session to be read during the synchronization process. Object types are
collections of attributes. When a synchronization filter is applied, changes to a defined
object type are synchronized on the next scheduled synchronization.

Password Synchronization -

Password synchronization can occur only if passwords are changed from Active
Directory. Passwords are synchronized when an administrator performs any of the
following administrative functions:

• Initial reverse synchronization

• User creation in NDS or eDirectory

• Password changes in Active Directory

Initial Reverse Synchronization -

Users that have been copied from NDS, eDirectory, or Bindery to Active Directory
through initial reverse synchronization will be prompted to change their passwords the
first time they log on to Active Directory. This new password will then be synchronized
with the password attribute in NDS, eDirectory, or Bindery.

Services provided by Novell Netware 

(1) Integrated Installation - NetWare 5 NFS is completely integrated with the

common installation framework provided in NetWare 5. The NFS services can be
installed either together or separately. For example, if you want to install just the FTP
Server, you can install only FTP Server. You don't have to install the complete NFS
product. Another change is that DNS configuration is no longer available within the
NetWare 5 NFS Services product. DNS services are installed and configured using the
Novell DNS/DHCP Services included with NetWare 5. Only NIS server configuration is
available in NetWare 5 NFS Services.

(2) HTML Documentation - NetWare 5 NFS Services comes with HTML

documentation on the product CD-ROM. In previous NFS versions (NFS
2.3 or earlier), you had to install the complete product in order to install the
documentation. NetWare 5 NFS Services documentation can be installed
and viewed from the CD without installing the actual product.

(3) New File Access Modes - NetWare 5 NFS Services provides file sharing
between the NetWare and UNIX worlds. Whereas NetWare uses trustee rights and
attributes, UNIX uses permissions. NetWare 5 NFS Services provides several elegant
ways to map these permissions into NetWare trustee rights and attributes to maintain
excellent file and directory access security. These are called file access modes.

NetWare 5 NFS Services provides five access modes for NFS Server and four modes to
optimize access between NetWare and UNIX.

a- NetWare Mode
b- NFS Mode
c- NetWare-NFS Mode
d- NFS-NetWare Mode
e- Independent Mode

(4) NSS Integration with NFS Server - NetWare 5 is equipped with the new
Novell Storage System (NSS), a powerful, high-performance storage and
 access system that addresses the ever-growing demand for storing larger
objects and a larger number of them. NSS provides built-in support for the
DOS, LONG, MAC, and NFS name spaces.

It provides fast access to data and instantaneous volume

mounts, mounting and repairing volumes in seconds, regardless of their
size. This is achieved by the use of 64-bit interfaces everywhere in the
storage engine.

(5) FTP Server Integration with Catalog Services - It provides a method to

store Directory data in a non-partitioned format, indexed for rapid access. Through
catalog services, information about NDS objects can be stored in a catalog database,
enabling administrators to access Directory information without having to walk the NDS
tree. Catalog services also enable the development of applications which need rapid
access to Directory data in a centralized repository. These applications might include
context less login, Group Wise address books, and so on. Developers might also find it
advantageous to leverage the speed of catalog services when using SQL search
capabilities.

References 

 www.microsoft.com
 www.windowsreference.com
 www.google.com
 www.wikipedia.com