Novell Netware Operating System

  1. Functions Of Novell Netware Operating System

Novell Manual December 10, 2002 89 www.novell.com NetWare 6 Overview and Installation Guide 100-004725-001 February 25, 2003 Novell Confidential NetWare 6. Novell software is now a part of Micro Focus and all products and information previously on Novell.com is now on. To-end view of application and system.

Once a dominant force in corporate networks, company has transformed itself dramatically. 1979: Novell Data Systems is founded in Provo, Utah, as a maker of computers and disk operating systems. 1983: Safeguard Scientifics, a venture capital firm, reincorporates NDSI as Novell, Inc, with Ray Noorda becoming president and CEO.

Company introduces NetWare, a network operating system that by the early 1990s would claim a 70% market share. 1986: Introduces GroupWise messaging and collaboration software. 1993: Acquires Unix System Laboratories from AT&T, securing rights to the Unix operating system (parts of which would be transferred to the Santa Cruz operation two years later). 1994: Acquires WordPerfect and Quattro Pro from Borland, only to sell them to Corel shortly afterward.

Robert Frankenberg replaces Noorda as CEO. NetWare 4.0 is released. 1996: Announces plan to make company's products 'Internet-ready.' 1997: Eric Schmidt becomes CEO. 1999: Microsoft Windows 2000 tops NetWare for NOS market leadership position.

2001: Acquires Massachusetts-based Cambridge Technology Partners, whose CEO Jack Messman would later become CEO of Novell. 2002: Acquires SilverStream Software, which specializes in Web services-oriented application development.

2003: Acquired open source application developer Ximian, as well as SuSE, maker of a leading Linux distribution, marking the company's commitment to a future product line based on Linux. 2005: Released Open Enterprise Server, which offered a choice between a NetWare or SuSE Linux Enterprise Server kernel. 2006: Ronald Hovsepian replaces Messman as CEO. Company announces controversial joint patent agreement with Microsoft. 2009: Reorganizes into two business units called: Security, Management, and Operating Platforms; and Collaboration Solutions. March, 2010: Declines buyout offer from Elliott Associates, L.P., which owns about 8.5% of the company's stock. 22, 2010: Agrees to be for $2.2 billion, which includes the $450-million sale of certain intellectual property assets to CPTN Holdings, a technology consortium led by Microsoft.

NetWare Working state Discontinued Source model Initial release 1983 6.5 SP8 (last) / May 6, 2009; 8 years ago ( 2009-05-06) English type Default, Official website NetWare is a discontinued computer developed by It initially used to run various services on a personal computer, using the network protocol. The original NetWare product in 1983 supported clients running both and, ran over a proprietary star and was based on a Novell-built file server using the Motorola 68000 processor, but the company soon moved away from building its own hardware, and NetWare became hardware-independent, running on any suitable Intel-based system, and a wide range of network cards.

From the beginning NetWare implemented a number of features inspired by and systems that were not available in its competitors. In the early 1990s, Novell introduced separate cheaper networking products, unrelated to classic NetWare. These were NetWare Lite 1.0 (NWL), and later Personal NetWare 1.0 (PNW) in 1993. In 1993, the main product line took a dramatic turn when Version 4 introduced (NDS), a global similar to the that would release seven years later. This, along with a new e-mail system , application configuration suite , and security product were all targeted at the needs of large enterprises. By 2000, however, Microsoft was taking more of Novell's customer base and Novell increasingly looked to a future based on a. The successor to NetWare, Open Enterprise Server (OES), released in March 2005, offered all the services previously hosted by NetWare v6.5, but on a; the NetWare kernel remained an option until OES 11 in late 2011.

The final update release was version 6.5SP8 of May 2009; Netware is no longer on Novell's product list. NetWare 6.5SP8 General Support ended in 2010, with Extended Support until the end of 2015, and Self Support until the end of 2017. The replacement is. Contents.

Red rooster collection fonts. History NetWare evolved from a very simple concept: file sharing instead of disk sharing. In 1983 when the first versions of NetWare originated, all other competing products were based on the concept of providing shared direct disk access. Novell's alternative approach was validated by in 1984, which helped promote the NetWare product. Novell NetWare shared disk space in the form of NetWare volumes, comparable to DOS volumes. Clients running would run a special (TSR) program that allowed them to map a local drive letter to a NetWare volume. Clients had to log into 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. At the end of the 1990s, with Internet connectivity booming, the Internet's protocol became dominant on. Novell had introduced limited TCP/IP support in NetWare v3.x (circa 1992) and v4.x (circa 1995), consisting mainly of FTP services and UNIX-style LPR/LPD printing (available in NetWare v3.x), and a Novell-developed webserver (in NetWare v4.x). Native TCP/IP support for the client file and print services normally associated with NetWare was introduced in NetWare v5.0 (released in 1998). During the early to mid-1980s introduced their own LAN system in, based on the competing protocol. Early attempts to muscle in on NetWare failed, but this changed with the inclusion of improved networking support in, and then the hugely successful and. NT, in particular, offered services similar to those offered by NetWare, but on a system that could also be used on a desktop, and connected directly to other Windows desktops where NBF was now almost universal.

Early years NetWare originated from consulting work by, a group founded by the friends, Dale Neibaur, Kyle Powell and later Mark Hurst. This work stemmed from their classwork at in, starting in October 1981. In 1981, engaged the work by the SuperSet team. The team was originally assigned to create a system to help network the CP/M Motorola 68000 hardware that Novell sold at the time. The first S-Net was based and shared a hard disk. In 1983, the team was privately convinced that CP/M was a doomed platform and instead came up with a successful file-sharing system for the newly introduced IBM-compatible. They also wrote an application called – a text-mode game – and used it to test the new network and demonstrate its capabilities.

Snipes aka 'NSnipes' for 'Network Snipes' was the first network application ever written for a commercial personal computer, and it is recognized as one of the precursors of many popular multiplayer games such as and. First called ShareNet or S-Net, this (NOS) was later called Novell NetWare. NetWare was based on the (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 protocol, and NetWare communicated natively using only IPX/SPX. The first product to bear the NetWare name was released in 1983.

There were two distinct versions of NetWare at that time. One version was designed to run on the Intel 8086 processor and another on the Motorola processor which was called NetWare 68K (aka ); it ran on the processor on a proprietary Novell-built file server (Novell could not write an original network operating system from scratch so they licensed a Unix kernel and based NetWare on that ) and used a star. This was soon joined by NetWare 86 V4.x, which was written for the.

This was replaced in 1985 with Advanced NetWare 86 version 1.0a which allowed more than one server on the same network. In 1986, after the processor became available, Novell released Advanced NetWare 286 V1.0a. Two versions were offered for sale; the basic version was sold as ELS I and the more enhanced version was sold as ELS II. The acronym ELS was used to identify this new product line as Netware's Entry Level System. NetWare 286 2.x Advanced NetWare version 2.x, launched in 1986, was written for the then-new 80286 CPU.

What happened to novell

The 80286 CPU featured a new protected mode that provided access to up to 16 MB RAM as well as new mechanisms to aid multi-tasking. (Prior to the 80286, PC CPU servers used the Intel / /16-bit processors, which were limited to an address space of 1 MB 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 (compared to the 32 MB that MS-DOS allowed at that time) allowed the building of reliable, cost-effective server-based local area networks 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. In a significant innovation, NetWare 286 was also hardware-independent, unlike competing network server systems. Novell servers could be assembled using any brand system with an Intel 80286 CPU, any, or hard drive and any 8- or 16-bit network adapter for which NetWare drivers were available – and 18 different manufacturer's network cards were supported at launch.

A server could support up to four network cards, and these could be a mixture of technologies such as, and. The operating system was provided as a set of compiled that required configuration and linking.

Any change to the operating system required a re-linking of the. Installation also required the use of a proprietary low-level format program for hard drives called COMPSURF. The file system used by NetWare 2.x was 286, or NWFS 286, supporting volumes of up to 256 MB. NetWare 286 recognized 80286, extending NetWare's support of RAM from 1 MB to the full 16 MB addressable by the 80286. A minimum of 2 MB was required to start up the operating system; any additional RAM was used for FAT, DET and file caching.

Since 16-bit protected mode was implemented the i80286 and every subsequent Intel x86 processor, NetWare 286 version 2.x would run on any 80286 or later compatible processor. NetWare 2.x implemented a number of features inspired by and systems that were not available in other of the day. The features included standard read-after-write verification (SFT-I) with on-the-fly bad block re-mapping (at the time, disks did not have that feature built in) and software (disk mirroring, SFT-II). The (TTS) optionally protected files against incomplete updates. For single files, this required only a file attribute to be set. Transactions over multiple files and controlled roll-backs were possible by programming to the TTS. NetWare 286 2.x normally required a dedicated PC to act as the server, where the server used DOS only as a to execute the operating system file net$os.exe.

All memory was allocated to NetWare; no DOS ran on the server. However, a 'non-dedicated' version was also available for price-conscious customers. In this, DOS 3.3 or higher would remain in memory, and the processor would time-slice between the DOS and NetWare programs, allowing the server computer to be used simultaneously as a network file server and as a user workstation.

Because all (RAM above 1 MB) was allocated to NetWare, DOS was limited to only 640 KB; managers that used the MMU of 80386 and higher processors, such as EMM386, would not work; 8086-style expanded memory on dedicated plug-in cards was possible however. Time slicing was accomplished using the keyboard, which required strict compliance with the IBM PC design model, otherwise performance was affected. Server licensing on early versions of NetWare 286 was accomplished by using a key card. The key card was designed for an 8-bit ISA bus, and had a serial number encoded on a ROM chip. The serial number had to match the serial number of the NetWare software running on the server.

To broaden the hardware base, particularly to machines using the IBM MCA bus, later versions of NetWare 2.x did not require the key card; serialised license floppy disks were used in place of the key cards. Licensing was normally for 100 users, but two ELS (Entry Level System) versions were also available. First a 5-user ELS in 1987, and followed by the 8-user ELS 2.12 II in 1988. NetWare 3.x NetWare's 3.x range was a major step forward. It began with v3.0 in 1990, followed quickly by v3.10 and v3.11 in 1991. A key feature was support for, eliminating the 16 MB memory limit of NetWare 286 and therefore allowing larger hard drives to be supported (since NetWare 3.x cached the entire and into memory for improved performance).

NetWare version 3.x was also much simpler to install, with disk and network support provided by software modules called a (NLM) loaded either at start-up or when it was needed. NLMs could also add functionality such as anti-virus software, backup software, database and web servers. Support for long filenames was also provided by an NLM. A new file system was introduced by NetWare 3.x – ' 386', or NWFS 386, which significantly extended volume capacity (1 TB, 4 GB files), and could handle up to 16 volume segments spanning multiple physical disk drives. Volume segments could be added while the server was in use and the volume was mounted, allowing a server to be expanded without interruption. In NetWare 386 3.x all NLMs ran on the server at the same level of processor, known as '.

This provided the best possible performance, it sacrificed reliability because there was no memory protection, and furthermore NetWare 3.x used a model, meaning that an NLM was required to yield to the kernel regularly. For either of these reasons a badly behaved NLM could result in a fatal error. NetWare continued to be administered using console-based utilities. For a while, Novell also marketed an version of NetWare 3, called Portable NetWare, together with OEMs such as, and, who ported Novell source code to run on top of their Unix operating systems. Portable NetWare did not sell well. While NetWare 3.x was current, Novell introduced its first system, named NetWare SFT-III, which allowed a logical server to be completely mirrored to a separate physical machine. Implemented as a cluster, under SFT-III the OS was logically split into an interrupt-driven I/O engine and the event-driven OS core.

The I/O engines serialized their interrupts (disk, network etc.) into a combined event stream that was fed to two identical copies of the system engine through a fast (typically 100 Mbit/s) inter-server link. Because of its non-preemptive nature, the OS core, stripped of non-deterministic I/O, behaves deterministically, like a large. The outputs of the two system engines were compared to ensure proper operation, and two copies fed back to the I/O engines.

Using the existing SFT-II software RAID functionality present in the core, disks could be mirrored between the two machines without special hardware. The two machines could be separated as far as the server-to-server link would permit.

In case of a server or disk failure, the surviving server could take over client sessions transparently after a short pause since it had full state information. SFT-III was the first NetWare version able to make use of hardware – the I/O engine could optionally be run on its own CPU. NetWare SFT-III, ahead of its time in several ways, was a mixed success. With NetWare 3 an improved routing protocol, has been introduced which scales better than and allows building large networks. NetWare 4.x Version 4 in 1993 introduced NetWare Directory Services, later re-branded as (NDS), based on, which replaced the Bindery with a global, in which the infrastructure was described and managed in a single place. Additionally, NDS provided an extensible, allowing the introduction of new object types.

This allowed a single user authentication to NDS to govern access to any server in the directory tree structure. Users could therefore access network resources no matter on which server they resided, although user license counts were still tied to individual servers. (Large enterprises could opt for a license model giving them essentially unlimited per-server users if they let Novell audit their total user count) Version 4 also introduced a number of useful tools and features, such as transparent compression at file system level and public/private. Another new feature was the NetWare Asynchronous Services Interface (NASI). It allowed network sharing of multiple serial devices, such as. Client port redirection occurred via an or driver allowing companies to consolidate modems and lines. The upgrade was not without its flaws – initially NetWare 4 could not coexist with earlier versions on the same network because of incompatibilities.

NetWare for OS/2 Promised as early as 1988, when the Microsoft-IBM collaboration was still ongoing and 1.x was still a 16-bit product, the product didn't become commercially available until after IBM and Microsoft had parted ways and OS/2 2.0 had become a 32-bit, pre-emptive multitasking and multithreading OS. By August 1993, Novell released its first version of 'NetWare for OS/2'. This first release supported OS/2 2.1 (1993) as the base OS, and required that users first buy and install IBM OS/2, then purchase NetWare 4.01, and then install the NetWare for OS/2 product. It retailed for $200. By around 1995, and coincidental with IBM´s renewed marketing push for its 32-bit OS/2 Warp OS, both as a desktop client and as a LAN server (OS/2 Warp Server), NetWare for OS/2 began receiving some good press coverage. 'NetWare 4.1 for OS/2' allowed to run Novell´s network stack and server modules on top of IBM´s 32-bit kernel and network stack.

It was basically NetWare 4.x running as a service on top of OS/2. It was compatible with third party client and server utilities and NetWare Loadable Modules. Since IBM´s 32-bit OS/2 included Netbios, IPX/SPX and TCP/IP support, this means that sysadmins could run all three most popular network stacks on a single box, and use the OS/2 box as a workstation too.

NetWare for OS/2 shared memory on the system with OS/2 seamlessly. The book 'Client Server survival Guide with OS/2' described it as 'glue code that lets the unmodified NetWare 4.x server program think it owns all resources on a OS/2 system'. It also claimed that a NetWare server running on top of OS/2 only suffered a 5% to 10% overhead over NetWare running over the bare metal hardware, while gaining OS/2´s pre-emptive multitasking and object oriented GUI. Novell continued releasing bugfixes and updates to NetWare for OS/2 up to 1998 Strategic mistakes Novell's strategy with NetWare 286 2.x and 3.x proved very successful; before the arrival of Server, 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. As Novell used instead of, they were poorly positioned to take advantage of the Internet in 1995. This resulted in Novell servers being bypassed for routing and Internet access in favor of hardware routers, -based operating systems such as, and SOCKS and HTTP on Windows and other operating systems. NetWare 4.1x and NetWare for Small Business Novell priced NetWare 4.10 similarly to NetWare 3.12, allowing customers who resisted NDS (typically small businesses) to try it at no cost. Later Novell released NetWare version 4.11 in 1996 which included many enhancements that made the operating system easier to install, easier to operate, faster, and more stable.

It also included the first full 32-bit client for -based workstations, support and the NetWare Administrator (NWADMIN or NWADMN32), a GUI-based administration tool for NetWare. Previous administration tools used the interface, the character-based GUI tools such as SYSCON and PCONSOLE with blue text-based background.

Some of these tools survive to this day, for instance MONITOR.NLM. Novell packaged NetWare 4.11 with its Web server, TCP/IP support and the browser into a bundle dubbed IntranetWare (also written as intraNetWare). A version designed for networks of 25 or fewer users was named IntranetWare for Small Business and contained a limited version of NDS and tried to simplify NDS administration. The intranetWare name was dropped in NetWare 5. During this time Novell also began to leverage its directory service, NDS, by tying their other products into the directory. Their e-mail system, was integrated with NDS, and Novell released many other directory-enabled products such as and. NetWare still required IPX/SPX as NCP used it, but Novell started to acknowledge the demand for TCP/IP with NetWare 4.11 by including tools and utilities that made it easier to create intranets and link networks to the Internet.

Novell bundled tools, such as the IPX/IP gateway, to ease the connection between IPX workstations and IP networks. It also began integrating Internet technologies and support through features such as a natively hosted. NetWare 5.x With the release of NetWare 5 in October 1998 Novell switched its primary NCP interface from the network protocol to TCP/IP to meet market demand. Products continued to support IPX/SPX, but the emphasis shifted to TCP/IP. New features included:. a for NetWare.

(NSS), a file system to replace the traditional (which Novell continued to support). for NetWare. Novell Distributed Print Services (NDPS), an infrastructure for printing over networks. ConsoleOne, a Java-based GUI administration console. directory-enabled services (PKIS). directory-enabled and servers.

support for (SANs). Novell Cluster Services (NCS), a replacement for SFT-III. with a 5-user license The Cluster Services improved on SFT-III, as NCS did not require specialized hardware or identical server configurations. Novell released NetWare 5 during a time when NetWare's had started dropping precipitously; many companies and organizations replaced their NetWare servers with servers running 's operating system. Around this time Novell also released their last upgrade to the NetWare 4 operating system, NetWare 4.2. NetWare 5 and above supported Novell NetStorage for Internet-based access to files stored within NetWare. Novell released NetWare 5.1 in January 2000.

It introduced a number of tools, such as:. NetWare Management Portal (later called Novell Remote Manager), web-based management of the operating system., and servers. NetWare Web Search Server.

support NetWare 6.0 NetWare 6 was released in October 2001, shortly after its predecessor. This version has a simplified licensing scheme based on users, not server connections. This allows unlimited connections per user to any number of NetWare servers in the network. Novell Cluster Services was also improved to support 32-node clusters; the base NetWare 6.0 product included a two-node clustering license. NetWare 6.5 NetWare 6.5 was released in August 2003.

Some of the new features in this version included:. more open-source products such as, and. a port of the shell and a lot of traditional Unix utilities such as, and to provide additional capabilities for scripting. support (both target and initiator). Virtual Office – an 'out of the box' web portal for end users providing access to e-mail, personal file storage, company address book, etc. functionality. Universal password.

DirXML Starter Pack – synchronization of user accounts with another eDirectory tree, a or Active Directory. exteNd Application Server – a 1.3-compatible. support for customized printer driver profiles and printer usage auditing. support. support for storage devices. support for encrypted volumes The latest – and apparently last – Service Pack for NetWare 6.5 is SP8, released May 2009.

Open Enterprise Server. Main article: 1.0 In 2003, Novell announced the successor product to NetWare: (OES). First released in March 2005, OES completes the separation of the services traditionally associated with NetWare (such as Directory Services, and file-and-print) from the platform underlying the delivery of those services. OES is essentially a set of applications (eDirectory, services, iPrint, etc.) that can run atop either a or a NetWare kernel platform.

Clustered OES implementations can even migrate services from Linux to NetWare and back again, making Novell one of the very few vendors to offer a multi-platform clustering solution. Consequent to Novell's acquisitions of and, a German Linux distributor, it is widely observed that Novell is moving away from NetWare and shifting its focus towards Linux. Much recent marketing seems to be focussed on getting faithful NetWare users to move to the Linux platform in future releases.

The clearest indication of this direction is Novell's controversial decision to release Open Enterprise Server in Linux form only. Novell later watered down this decision and stated that NetWare's 90 million users would be supported until at least 2015. Meanwhile, many former NetWare customers rejected Novell's Linux efforts for other distributions like. Some of Novell's NetWare supporters have taken it upon themselves to petition Novell to keep NetWare in development. 2.0 OES 2 was released on October 8, 2007. It includes NetWare 6.5 SP7, which supports running as a paravirtualized guest inside the hypervisor and new Linux based version using SLES10.

New features include. support. Virtualization. Dynamic Storage Technology, which provide Shadow Volumes. Domain services for Windows (provided in OES 2 service pack 1) From the 1990s As of 2010 some organizations still used Novell NetWare, but it had started to lose popularity from the mid-1990s, when NetWare was the de facto standard for file- and printer-sharing software for the server platform. Microsoft successfully took market share from NetWare products from the late-1990s.

Microsoft's more aggressive marketing was aimed directly at non-technical management through major magazines, while Novell NetWare's was through more technical magazines read by IT personnel. Novell did not adapt their pricing structure to current market conditions, and NetWare sales suffered, with many existing Netware users, in addition to new users, migrating to Microsoft network operating systems. NetWare Lite / Personal NetWare In 1991, Novell introduced a radically different and cheaper product, 1.0 (NWL), in answer to Artisoft's similar.

Both were peer-to-peer systems, where no specialist server was required, but instead all PCs on the network could share their resources. The product was upgraded to NetWare Lite 1.1 and also came bundled with some issues of 6.0.

Some components of NetWare Lite were used in Novell's NetWare 1.0 in 1992. Significantly reworked, the product line became 1.0 (PNW) in 1993. The /VLM (for ) 16-bit client portion of the drivers now supported individually loadable for an improved flexibility and customizability, whereas the server portion could utilize Novell's , if loaded, to reduce its footprint and run in and. The NetWare Lite disk cache had been reworked into, which was easier to set up and could utilize DPMS as well, thereby reducing the DOS memory footprint and significantly speeding up disk performance. Personal NetWare came bundled with the network-enabled game 2.06. The Personal NetWare 1.0 product saw five maintenance upgrades as well as various comprehensive updates to the corresponding VLM client driver suite (1.0, 1.1, 1.20, 1.21) as part of the Novell Client Kit for DOS & Windows up to November 1996, which added many new drivers, including drivers for and, as well as extra and languages. A full version of Personal NetWare (save the interactive tutorials) also came bundled with 7 in 1993/1994 at a price similar to that of the stand-alone version of Personal NetWare.

Portions of Personal NetWare were incorporated into Novell's for DOS and for DOS products, and as such compatible TCP/IP drivers became available for the system as well. Later, Personal NetWare was bundled with full versions of 7.01, 7.02 and 7.03 between 1997 and 1999, however, these bundles were delivered with the same Personal NetWare files shipping with Novell DOS 7, not the upgraded files, which had been made available for download by Novell since 1994. The ODI/VLM client stack with TCP/IP drivers also found its way into the distribution. When Novell in 1996 introduced its / 32-bit DOS/Windows client , it used NLM instead of VLM modules.

While the NIOS client could reduce the conventional memory footprint down to 2 to 5 KB in total, the lack of something like a 'PNW.NLM' module (in analogy to the VLM client's PNW.VLM) made it impossible to use the new client in conjunction with a Personal NetWare server. Performance NetWare dominated the network operating system (NOS) market from the mid-1980s through the mid- to late-1990s 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. One noteworthy benchmark pitted NetWare 3.x running services over TCP/IP (not NetWare's native IPX protocol) against a dedicated Auspex NFS server and a SCO Unix server running NFS service. NetWare NFS outperformed both 'native' NFS systems and claimed a 2:1 performance advantage over SCO Unix NFS on the same hardware. The reasons for NetWare's performance advantage are given below.

File service instead of disk service When first developed, nearly all LAN storage was based on the disk server model. Novell Web site. Retrieved 20 November 2015. Retrieved 20 November 2015. Archived from on July 28, 2016. ^, June 30, 1986, p.

76, Computerworld., p. 7, Network World June 5, 1989. October 7, 2013.

February 29, 1988. Retrieved on May 23, 2014.

December 5, 2000, at the. 'The market has spoken, and TCP/IP has won,' says Novell CEO Eric Schmidt of the move to IP, a decision that was bitterly contested inside the company.' . Harris, Jeffrey (2005). Novell Press.

Pearson Education. Retrieved August 5, 2014.

OES NetWare relies on Novell Distributed Print Services (NDPS) to provide a robust network printing infrastructure. NDPS has been in use since NetWare 5. Kennard, Linda (December 9, 2004). Novell Connection Magazine. Retrieved May 25, 2010.

NetStorage ships with NetWare 6.5 and enables Internet-based access to files stored in users' iFolders and on servers running NetWare 5 and above. Johnson, David; Gaskin, James E.; Cheung, Daniel; (2003). Que Publishing. Pp. 177, 426. Retrieved May 25, 2010.

NetStorage is a bridge between a company's private, internal Novell network and the public Internet. Users can use NetStorage to securely access files from any location that has Internet access, without having to download or install additional software on the workstation. Novell NetWare 6.0 - NETWARE LICENSING FREQUENTLY ASKED QUESTIONS. Retrieved August 20, 2012. In previous versions of NetWare ®, a Server Connection License model is used, where users are granted access to network services on a per-server basis.

This means each time a user accesses services on a different server, the user consumes a license unit on that server. Printer connections also consume a connection license. In the NetWare 6 User Access License model, users consume a single User license (per tree) regardless of the number of NetWare 6 servers they log on to. Printers that connect to a NetWare 6 server do not consume a User license. The same is true for all other non-User connections. Novell NetWare 6.0 - Novell Cluster Services Overview and Installation. Provo, UT, USA: Novell Inc.

February 2002. Archived from (PDF) on November 25, 2006. Retrieved August 20, 2012. Multinode all-active cluster (up to 32 nodes). Any NetWare server in the cluster can restart resources (applications, services, IP addresses, and volumes) from a failed server in the cluster. Vaughan-Nichols, Steven J. (November 30, 2006).

Functions Of Novell Netware Operating System

Retrieved March 26, 2007. Galli, Peter (March 20, 2006). Retrieved March 26, 2007. Bray, Hiawatha (November 1, 2005). The Boston Globe. The Register. 16 July 2013.

Retrieved 20 November 2015. CBS Interactive. Galli, Peter.

(February 17, 2003). Retrieved on May 23, 2014. Retrieved on May 23, 2014.

Further reading. Harris, Jeffrey L. Novell Open Enterprise Server Administrator's Handbook, NetWare Edition.

Harris, Jeffrey L. Novell NetWare 6.5 Administrator's Handbook. Harris, Jeffrey L.; Kelley J.P. Lindberg (2002).

Novell's NetWare 6 Administrator's Handbook. Bastiaansen, Rob; Sander van Vugt (2006).

Novell Cluster Services for Linux and NetWare. Hughes, Jeffrey F.; Blair W. Thomas (2002). Novell's Guide to NetWare 6 Networks. External links. – tips & tricks, guides, tools and other resources submitted by the NetWare community.