Academic OneFile - Document
`
`Page 1 of 20
`
`Title:
`Author(s):
`Source:
`Document Type:
`
`Beyond NetWare 3.12
`Elizabeth Eva , Mauri Laitinen and Rob Ward
`Into World. 16.51 (Dec. 19, 1994): p66.
`Product/service evaluation, Product/service evaluation
`
`COPYRIGHT 1994 InfoWorld Media Group, Inc.
`Copyright :
`http://www.iwsubscribe.com
`Full Text:
`
`LAN Server and NT Server are vastly improved, and NetWare 4.1 is what 4.0x should have been in the first place.
`At long last, network administrators no longer have to live in a one-NOS town.
`
`If they were computers, goes the popular analogy, cars would go faster, cost next to nothing, and get hundreds of
`miles to the gallon. Forttmately for commuters, cars are not computers. If they were, they would crash every day. If
`you wanted to change a flat tire, you would discover that the owner's manual contained a treatise on lug-nut design
`but no instructions on where to find the jack. Perhaps worst of all, you would always need a skilled mechanic
`(Certified Driving Engineer) riding shotgtm.
`
`Networking PCs is becoming an inevitable headache for more and more businesses. What's truly exciting about the
`three network operating systems reviewed here is that for the first time the right folks have the headache: the
`vendors. This is the only reasonable division of labor: NOS vendors figure out how to build a faster, more reliable
`engine, while network administrators spend more time on the information highway and less in the shop.
`
`The defining milestone in this new era is NetWare 3.x's passage from default choice to only one of several viable
`products. The reigning network operating system for years despite considerable flaws, NetWare 3.x is no longer the
`only NOS worth considering, or even the fastest, which is one of the reasons we didn't include Version 3.12 in this
`comparison except as a baseline for speed. Deciding on a NOS will be harder now that there are more choices, but
`we don't think users are going to complain too much. From installation to administration, these NOSes are simply
`better and easier than ever before.
`
`WHAT KIND OF TOOL AM I? The fimdamental architecture and design goals of these products remain much as
`they were in previous versions. Novell Inc. built NetWare 3.x from the ground up to provide file and print services
`to large numbers of users, based on a small, fast kernel. The company added a sophisticated directory-services layer
`to NetWare 4.01 for enhanced administration capabilities, which it finally brings up to full speed in Version 4.1.
`
`IBM and Microsoft Corp. designed LAN Server and Windows NT Server to be more things to more people,
`providing not only file and print services, but also including the sorts of features -- such as symmetric
`multiprocessing (SMP) support, pre-emptively scheduled threads, process protection, interprocess communication,
`and virtual memory -- that are the hallmarks of good application servers. We were impressed by how fast these
`products’ file and print services have become.
`
`Despite their inherent differences, each of the new versions of the products under review here has implemented a
`common set of features and fimctionality important to most users. Together, the improvements define a baseline for
`NOS success in contemporary business environments.
`
`* Easier installation. Whether an administrator has years of experience managing hundreds of servers or is a
`newcomer building a departmental LAN, fast and simple installation saves the company money. LAN Server 4.0
`Advanced and Windows NT Server 3.5 have both come close to the ideal of unattended installation. Even Novell,
`which in the past has seemed philosophically wedded to the notion of difficult installations, has reformed.
`
`* Easier administration. In 1844, Ralph Waldo Emerson jotted down some thoughts that seem pertinent in a world
`still dominated by NetWare 3.12. "Expecting nothing," he wrote, "I am always full of thanks for moderate goods."
`In that spirit, administrators have something to be thankfiil for, because the administrative tools in these new
`products show a marked improvement over past offerings and are often easy to learn and use. (This is particularly
`true of NetWare 4.1's NWADMIN utility and LAN Server's use of OS/2 objects.)
`
`http://go. galegroup.com.ezproxy.sfpl.org/ps/retrieve.do?sgHitCountType=None&sort=D. ..
`
`l 1/ 1 9/201 3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1020 - Page 1
`
`

`
`Academic OneFile - Document
`
`Page 2 of 20
`
`Plenty of room for improvement remains, however. With a few exceptions, the tools are not very well integrated,
`and some of them are amateurishly designed, lacking the interface features that have become commonplace in other
`commercial applications (such as default settings in dialog boxes), to say nothing of more sophisticated interface
`elements such as wizardlike helpers.
`
`On the architectural side, administrative capabilities have improved noticeably.
`
`Domain-based architecture is not exactly the wave of the fl1t1]I€, but LAN Server and NT Server have beefed it up -
`- in different ways -- to a level approaching shouting distance of centralized administration. NetWare 4.1, which
`actually does provide centralized administration, looks more like what we can expect to see of future NOS designs.
`
`* Better security. User authentication with Version 3.x and earlier of NetWare was less than adequate. Although
`Version 3.12 now has a password-encryption option, the other products employ RSA-style authentication, in which
`a random-value key is sent by the server, encrypted on the client side by the password, and sent back to the server
`for verification, so the password itself never travels over the wire.
`
`Both NetWare 4.1 and NT Server 3.5 implement C2-level security, a specification designed by the Department of
`Defense for military computers (see story, page 76). It is questionable whether anyone will ever actually sit behind
`an officially C2-certified system, because the rating applies only to specific combinations of hardware and NOS,
`and the certification period -- two years -- is just long enough to constitute a form of planned obsolescence.
`Moreover, C2 is designed with specifically military needs in mind and, although these are not necessarily
`incompatible with business needs, neither are they identical. For instance, C2 is not especially strong in addressing
`the security problems of enterprisewide networks.
`
`* Enterprise capability. Transport protocols have always been a defining aspect of NOSes. This year all three
`vendors appear to be aware of that fact and are shipping more of what their customers actually want and less of
`what they want them to want. The three new products all provide a form of multiple-protocol support.
`
`Closely related to this is the fact that, except for NetWare 3.12, vendors are positioning NOSes not as LAN products
`anymore but as enterprise products. In this context, enterprise has one meaning: routing -- the task of herding data
`reliably from point A to point B irrespective of physical location. In order that their products can be more easily
`adopted by large companies with PCs in disparate locations, all three vendors now provide a routable protocol stack
`(chiefly TCP/IP).
`
`BEST-LAID PLANS. Companies that need to expand their networks have several choices: they can remain a
`NetWare 3.12 shop; standardize on a different NOS and migrate their servers; or create a mixed network in which
`the original servers remain unchanged, but additional servers run one or more of the new products compared here.
`
`We based the test plan for this comparison on the scenario of expanding a NetWare 3.12-based network with other
`NOSes, with interesting results (see the NetWare integration scoring category on page 74).
`
`To evaluate the speed of these NOSes, we let the vendors make reasonable tuning adjustments before running our
`tests on 20 and 40 clients. Surprisingly, those tweaks, described on page 76, didn't always significantly improve
`performance over the "out-of-the-box" tests we ran.
`
`Hot off the dupe machine, NetWare 4.1 barely made our deadline; it formally shipped only two weeks ago, just as
`we were finishing testing. The copy we reviewed was one of the last gold versions of the product. No changes were
`made to the core code before the product shipped, according to the vendor.
`
`Product Overview
`
`LAN Server 4.0 Advanced
`
`IBM's LAN Server 4.0 Advanced is so much improved over previous versions that IBM should simply give it a
`new name. Its easy installation option equals Microsoft Corp. Windows NT Server's analogous express installation
`
`http://go. galegroup.com.ezproxy.sfpl.org/ps/retrieve.do?sgHitCountType=None&sort=D. ..
`
`1 1/ 1 9/201 3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1020 - Page 2
`
`

`
`Academic OneFile - Document
`
`Page 3 of 20
`
`for speed and simplicity, and the system takes advantage of OS/2's object-oriented capabilities to provide a strong
`new set of graphical administration tools.
`
`For moderate file-and-print service loads, LAN Server has revved its performance considerably. Its support of the
`new symmetric multiprocessing version of OS/2 2.11 allows it to handle CPU-intensive applications better than
`ever, assuming you're using a multiprocessor system.
`
`IBM has enhanced LAN Server's enterprisewide networking capabilities by including an improved TCP/IP protocol
`stack (easily configurable as the default) and aliasing features that allow easier management of resources across
`workgroups and domains. LAN Server is unique among the network operating systems here for including a
`scripting language, the powerfiil Rexx.
`
`We tested the Advanced version of LAN Server, which comes with the High Performance File System (HPFS).
`LAN Server also comes in a less expensive Entry version, which lacks HPFS and is intended for smaller networks
`where performance is of less concern than price.
`
`NetWare 4.1
`
`NetWare's primary design goal remains fast file-and-print services for large LANs, and as our file-and-print services
`benchmark shows, it succeeds admirably in NetWare 4.1. To this, Novell Inc. has added a second major design
`goal: easier administration. This is partly the result of a Novell customer survey that showed that 70 percent of the
`cost of ownership of NetWare 3.x was administrative.
`
`Novell's solution consists of a network structure based on a set of X.500 conventions called NetWare Directory
`Services (NDS), which made its debut in Version 4.00 to a less-than-enthusiastic reception, even among confirmed
`NetWare users. Although widely acknowledged to be a potentially powerfiil and sophisticated means of
`administering large networks, NDS lacked a crucial feature: the capability to make significant changes to the
`directory structure once it had been defined.
`
`Version 4.1 remedies this oversight; NDS now delivers the most robust administration scheme of the NOSes we
`tested. Novell significantly augments this administrative power with a new utility called NetSynch, which allows a
`NetWare 4.1 server to administer as many as 12 NetWare 3.x servers by adding them to the NDS context. Users
`can access this fiinctionality through a new GUI-based utility called NWADMIN, which presents the whole network
`visually.
`
`After you use NWADMIN, the server operator's console comes as a shock. Mysterious bulletins that you cannot
`pause or capture (until well into the start-up process) scroll up the screen. This is probably for the best, because the
`uninitiated will never be able to discern bland informational lines from critical error messages. For aging computer
`operators, it's a heady draft of nostalgia. Turn up the air conditioning, add a clacking teletype, and you'll find
`yourself transported back 20 years to the console of an old mainframe.
`
`For wide-area connectivity, Novell suggests using its IPX protocol with NetWare Link Services Protocol; Novell
`includes a coupon for NetWare Internet Protocol (IP) as well.
`
`Though it doesn't offer them in a tightly integrated suite, Version 4.1 also introduces a number of tools for
`configuring and monitoring the network, such as INETCFG and SERVMAN.
`
`NetWare 4.1 continues to support RAID Levels 0 and 1 in both mirrored and duplexed configurations, and now
`bundles Novell's own System Fault Tolerance III software, though you must pay an extra activation fee.
`
`Windows NT Server 3.5
`
`It is faster and simpler to create a functioning network with Microsoft's Windows NT Server 3.5 than with any of
`the other products we tested in this comparison.
`
`http://go. galegroup.com.ezproxy.sfpl.org/ps/retrieve.do?sgHitCountType=None&sort=D. ..
`
`1 1/ 1 9/201 3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1020 - Page 3
`
`

`
`Academic OneFile - Document
`
`Page 4 of 20
`
`NT Server also holds the title of most improved. It performed our file-and-print services benchmark nearly twice as
`fast as the disappointing NT Server 3.1 did.
`
`Microsoft bundles an improved IPX stack as NT Server's default protocol and offers an improved version of
`TCP/IP.
`
`NT Server has also taken a giant step by providing an automated IP-address pooling service that automatically
`allocates IP addresses to clients without user intervention, regardless of the user's location on the network.
`
`Also new is a migration utility that copies the bindery information and data volumes from a NetWare 3.12 server
`onto an NT Server 3.5 machine. If you don't want to go that far, you can plug into an existing NetWare server
`directly from a client machine or via a NetWare gateway located on the NT Server server.
`
`NT Server's network administrative scheme revolves around domain directory services. In order to avoid the
`administrative nightmare of maintaining separate user accounts on different servers, you can establish trust
`relationships between domain directories to allow users a single networkwide log-in.
`
`New to this version is the capability to administer the network either from a 16-bit or 32-bit client workstation or
`from a remote workstation, independent of the protocol running on the client.
`
`Installation and client configuration
`
`LAN Server 4.0 Advanced: Very Good
`
`LAN Server provides two installation options: easy and tailored. The easy option really is; it's quick and simple.
`The tailored option allows you greater flexibility in specifying the configuration but requires low-level knowledge
`of your hardware that may mean some homework. (Quick! Does your server's disk drive use 24-bit direct memory
`access?)
`
`LAN Server does not support the NE3 200 network interface card G\IIC), which prompted us to switch to Compaq
`NetFlex II EISA Ethernet cards for all the NOSes. (IBM's stated aim is to support 90 percent of Token Ring cards
`but only 70 percent of Ethernet cards.)
`
`IBM continues its obsession with acronyms. In the course of the installation we found help screens littered with
`references to MPTS, NIF, DASD, and other product-specific acronyms, which are seldom explained in context and
`often are not to be found in the on-line glossary. (MPTS, by the way, stands for multiprotocol transport service; NIF
`is network information file; and DASD, a mainframe term for hard disks that apparently no one but IBM uses,
`stands for data access storage device.)
`
`During benchmark testing, we discovered that a bug in the DOS requester prevented two of our DOS applications --
`Paradox 3.5 and Harvard Graphics 3.0 -- from launching. IBM supplied us with a new, compatible version that
`worked with our applications and is available to users through IBM's usual problem-solving channels.
`
`The interface that LAN Server provides for setting up client machines is only slightly worse than NT Server's.
`Administrators must purchase a separate product to be able to install requester software across the wire, but the
`option that creates installation disks works easily, detects hardware accurately, and creates a handy log-on screen.
`The client requester installation for Windows assumes Windows 3.1; if you're running Windows for Workgroups
`3.11, you must rename some DLLs and make some other simple but obscure changes (all of which you can
`automate with a simple batch file). You can use the requester that comes with Windows for Workgroups 3.11, but
`you must use the LAN Server requester if you want to use aliasing or public applications, two of the NOS’ stronger
`features.
`
`NetWare 4.1: Good
`
`http://go. galegroup.com.ezproxy.sfpl.org/ps/retrieve.do?sgHitCountType=None&sort=D. ..
`
`1 1/ 1 9/201 3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1020 - Page 4
`
`

`
`Academic OneFile - Document
`
`Page 5 of 20
`
`Novell has somewhat improved NetWare 4. 1's installation over that of Version 3.12. A "simple" CD-ROM
`installation assumes an existing DOS partition with at least 15MB of space and a working CD-ROM drive. It
`chooses a default volume name and IPX network number, then uses the remaining free disk space to create a single
`NetWare partition with a SYS volume that has a single-organization NetWare Directory Services tree.
`
`According to Novell, most administrators want total control of server configuration, so NetWare 4.1 offers limited
`hardware detection and the administrator must confirm every choice. Both the simple and custom installations
`require detailed knowledge of the hardware, including I/O port and interrupt request values for the disk controllers
`and NICs.
`
`By contrast, installing Version 4. 1's client software was a snap. We still had to use the downloaded EtherExpress
`driver, but otherwise the installation took little effort. Users can now configure CD-ROM-equipped client machines
`directly from the installation CD.
`
`Windows NT Server 3.5: Excellent
`
`Like any Microsoft product, NT Server offers both custom and express installation options; we found both to be
`fast, simple, and straightforward. The system had no problem recognizing our hardware, which included Adaptec
`7770 and 1542 cards, a Mylex DAC960 redundant array of inexpensive drives controller, and four NE3200 NICs
`(and later -- when we switched NICs -- four Compaq NetFlex II EISA Ethernet cards). We completed the express
`installation successfully simply by accepting the defaults. The custom option allowed us to select and configure
`many of the services we review in subsequent tasks.
`
`A utility new to Version 3.5 is the Network Client Administrator (NCA), which provides several ways to install
`client-requester software. Unforttmately, NCA's interface and help screens are ambiguous. It also presented us with
`a surprising number of error messages when we accepted defaults.
`
`The handiest option has you specify the client-side NIC, then creates a boot disk that connects the client machine to
`the server and performs an across-the-wire installation of Windows for Workgroups or Microsoft Network Client
`for MS-DOS.
`
`Redirector choices include real- and protected-mode DOS requesters in filll and basic versions (posing a tastes-
`great, less-filling trade-off), and a 32-bit TCP/IP stack originally developed for Chicago, as well as for the DOS and
`OS/2 versions of LAN Manager. The system supports a broad range of NICs. Microsoft's SMC Elite 16 Combo
`driver, however, would not work over IPX. We had to use the driver that SMC ships with the card until Microsoft
`could provide us with a fix.
`
`Administration: establishing users
`
`LAN Server 4.0 Advanced: Very Good
`
`Because virtually all aspects of the network appear as objects to LAN Server, creating and managing them is a
`quick and flexible process. If the OS/2 desktop is new to you, it may take some time to learn but will be worth the
`effort. Its drag-and-drop fimctionality makes for very fast and easy user-account management and resource sharing.
`This use of OS/2 objects and templates is one of LAN Server's greatest strengths. In addition, LAN Server satisfies
`power users who prefer a command line over a mouse and icons by granting the Rexx scripting language access to
`the LAN Server API.
`
`IBM supplies an adequate number of privilege levels in addition to user and administrator, though none is
`customizable and administrative control over password use is minimal at best. The system also lacks a way to
`restrict log-on hours from the graphical administration tools, but you can do so from the command line.
`
`We particularly liked the capability to specify limits to disk usage in users’ home directories. When the limit is
`reached, both administrator and user are notified (the system continues to allow further writes to the disk, so data is
`not at risk).
`
`http://go. galegroup.com.ezproxy.sfpl.org/ps/retrieve.do?sgHitCountType=None&sort=D. ..
`
`1 1/ 1 9/201 3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1020 - Page 5
`
`

`
`Academic OneFile - Document
`
`Page 6 of 20
`
`LAN Server gives administrators user-access profiles to grant access to and restrict usage of system resources. Just
`when administrators were getting used to objects, IBM throws them a form to fill out; forttmately, it's fairly simple.
`
`Just as we were about to give the Stupidest Error Message of the Whole Comparison award to NT Server, we tried
`saving some changes we made to a user account on LAN Server, and got this message: "The parameter is
`incorrect." Dozens of parameters for a user account are scattered through a number of pages in the tabbed dialog.
`This help screen is also worth noting: "Cause unknown; consult the documentation." As we were pondering how to
`look up an urmamed problem with an unknown cause, we suddenly realized that, contrary to myth, software
`developers do have a sense of humor.
`
`You can create a single networkwide log-on for a user, as well as centralized administration, though the process
`involves more steps than with NetWare or NT Server. A single log-on for a domain is simple to generate, but then
`you must create an identical log-on for each additional domain; this isn't ideal, but it's a big improvement on the one
`server, one log-on scenario. Separate log-ons are not necessary for each domain as long as the password and user
`ID are consistent. (An optional application, Net Signon, lets you synchronize IDs and passwords across domains.)
`LAN Server's aliasing scheme has networkwidescope, allowing servers on one domain to see resources on others.
`
`There are limits to your ability to perform centralized administration. From the graphical interface, you can
`administer a maximum of six domains; from the command line, however, you can administer all domains.
`
`NetWare 4.1: Excellent
`
`NetWare 4.l's new capabilities and GUI-based administration tools are a boon to administrators of both large and
`small networks. Full-tirne administrators receive the power they need to keep up with organizational changes, and
`part-time administrators don't have to master a plethora of obscure commands.
`
`Versions 2.x and 3.x of NetWare relied on the system's bindery database to keep track of network objects such as
`file servers, printers, routers, gateways, groups, and users. In Version 4.0, the NetWare Directory Services (NDS)
`database replaced the bindery. In its simplest form, NDS can act as a flat database, such as the bindery, or it can take
`the form of a complex tree incorporating multiple servers, locations, and even countries.
`
`You can partition the NDS database across multiple servers for fault tolerance and manageability. This means that
`different locations can administer their own areas, and the network database scales up without becoming unwieldy.
`
`One of the drawbacks in the 4.0x NDS was the incapability to move or rename subtrees or merge two separate trees.
`This meant that changing a group such as Marketing to Mktg or moving it to a different location required deleting
`and then re-creating it. Because changes were so difficult to implement, administrators had to plan the NDS
`structure carefiilly and limit subsequent alterations. NetWare 4.l removes these restrictions. For administrators of
`large networks, changing the network to reflect the corporate organization is now a quick and easy task.
`
`NWADMIN, a Windows tool, displays the NDS database as a tree, with every object type represented as a
`descriptive icon, allowing you to create and delete objects, move them, and change their properties. Double-clicking
`on an object brings up a properties dialog box. To insert a new user, for example, just highlight the new user's group
`and select the Create button. It brings up a dialog box in which you can enter the appropriate information about the
`new user.
`
`You can also define a template that defines groupwide properties. Each user created under the template
`automatically receives the properties. From the template, you can define passwords and password restrictions, hours
`of use, printers, home directories, and log-in scripts. Although the administrator can change any user's properties
`and rights to objects, the templates and NDS’ inherited-rights structure simplify the task of creating consistent user
`accounts.
`
`Multiple log-in scripts let administrators tailor each department's and each user's environment. Every organizational
`unit can have a log-in script, so a user belonging to a hierarchy of organizational units will execute all of the scripts.
`Each script can be edited from NWADMIN.
`
`http://go. galegroup.com.ezproxy.sfpl.org/ps/retrieve.do?sgHitCountType=None&sort=D. ..
`
`1 1/ 1 9/201 3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1020 - Page 6
`
`

`
`Academic OneFile - Document
`
`Page 7 of 20
`
`To move a user to a different group with NWADMIN, just highlight the user's icon and pick the Move menu, or
`drag and drop the icon. A dialog box appears listing permissible moves. Moving a whole group, a server, or any
`other object is also easy. NWADMIN allows you to combine two separate trees using DSMERGE, a separate
`server console utility.
`
`Novell has made the process of configuring network protocols, network interface cards, and interfaces significantly
`easier in NetWare 4.1 by combining the operations into a single utility, INETCFG. The company has also added
`other network monitoring and testing utilities to make the administrator's life more bearable.
`
`Windows NT Server 3.5: Good
`
`NT Server 3.5's User Manager provides quick and relatively painless access to most user account tasks. You can
`specify a home directory on the user's machine or map a drive letter to a server directory, although the inexplicable
`absence of a Browse button makes this an error-prone chore.
`
`We encountered warnings that the server could not create new directories that we specified for user home
`directories when we failed to set up the user account in precisely the (undocumented) correct order. The "invalid
`path name" error message we got when we specified "c:\users\paula" as a home directory on the server struck us as
`just plain weird. The directory of that name showed up in the File Manager, but the User Manager insisted we use
`the \\servemame\path convention. It's just as easy to tell the user what convention to use as it is to say, "Sorry, you
`can't do that," so why the secrecy? (The Help button in the user-environment profile screen under the User Manager
`does state that users need to follow the Universal Naming Convention pathname.)
`
`We also experienced difficulties with root mapping. We mapped \\....\subdir to drive X; on the client machine, drive
`X appeared as X:\subdir rather than just X:. The remedy to this problem was simple: We just established a share
`first on the parent directory, then we could map any number of directories under that share. Microsoft could make
`the interface much clearer about the order in which to proceed.
`
`The User Administrator provides an impressive number of predefined access types beyond the traditional
`administrator, user, and guest, and you can also create custom types. Administrators can easily restrict hours of
`access, limit the number of machines a user can log on from, and manage log-in scripts and user profiles. Passwords
`are also easily managed. You can specify policies such as length of a password, uniqueness, aging, how often users
`must change passwords, and the number of log-on attempts to allow. Microsoft does not, however, offer more
`advanced password administration, such as disallowing the use of a user's own name, as NetWare 4.1 does.
`
`NT Server's access scheme lets you define a share name for a set of files and directories. You can define shares with
`various names and access levels and apply them to different individuals and groups. Setting shares and permissions
`is reasonably easy, though not quite as straightforward as it is with LAN Server 4.0; integrating this fiinctionality
`into the User Administrator would further simplify administration. Microsoft could also better integrate server- and
`domain-level administration, which, though easy to carry out, resides in four separate places in the interface.
`
`Once we had created accounts, we experienced a surprising amount of trouble connecting to the server from our NT
`workstation. We got "Could not locate domain controller" messages on some accounts, logged on successfully with
`another account, and then successfiilly logged on with the original account. We saw similar behavior with an
`erroneous message that the log-on service was missing.
`
`As before, NT Server 3.5 includes the capability for administrators to establish trust relations between domain
`directories. Though it lacks the power of NDS, this capability nonetheless permits users to have a single user
`account with one password across domain directories and, just as important, allows centralized administration of the
`network. You can set the trust to be mutual or one way. For networks with many domain directories, managing the
`trust relations themselves is not trivial, but the added power this capability affords administrators is part of what
`makes this version of NT Server such a compelling product.
`
`Administration: other tasks
`
`http://go. galegroup.com.ezproxy.sfpl.org/ps/retrieve.do?sgHitCountType=None&sort=D. ..
`
`1 1/ 1 9/201 3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1020 - Page 7
`
`

`
`Academic OneFile - Document
`
`Page 8 of 20
`
`LAN Server 4.0 Advanced: Good
`
`Unlike NT Server, which forces you to choose between the faster file allocation table (FAT) and the more secure
`NT File System (NTFS), LAN Server's High Performance File System (HPFS) gives you the best of both worlds;
`it's fast and provides fine file and directory security. HPFS rims at the Intel CPU's so-called Ring 0 and attempts to
`process I/O requests within a single interrupt. HPFS is also necessary in order to perform the filll range of
`administrative tasks, such as protecting files from unauthorized access at the server itself (an important feature
`because LAN Server 111115 on top of an operating system without log-on protection).
`
`LAN Server, unlike NT Server and NetWare 4. 1, does not implement C2-level security. It does use an encrypted
`key to authenticate users, though, just as the other two NOSes do.
`
`LAN Server logs system errors and warnings and provides quick help with them. The audit log utility, however, is
`limited to events on the server. There is no auditing facility, nor does it provide transaction logging or automatic
`reboot.
`
`LAN Server adds a second meaning to the term "application server." Administrators can define DOS, Windows, or
`OS/2 applications to LAN Server; users and groups with rights can access applications without having to know
`their actual locations, allowing administrators to make changes to servers that are transparent to users. You can
`administer the server from a client workstation, though not a remote workstation.
`
`LAN Server 4.0 does not implement dynamic performance tuning. However, it does come with a utility called LS
`4.0 Tuning Assistant that gives administrators extensive access to system parameters. Using it requires a lot of LAN
`Server savvy, though, as well as expert knowledge of networking at a low level.
`
`IBM equips LAN Server with a number of utilities, including LAN Specialist, which helps track errors (client
`software is required), and a file-synchronizing utility for remote users (who must be running OS/2). An action folder
`called LAN Server Productivity Aids contains some in-house utilities included on the installation CD. They're
`worth the separate installation required, especially the Access Control Manager, which fiirther simplifies resource
`sharing.
`
`LAN Server supports only RAID Level 1, though third-party software is available to implement other levels. LAN
`Server offers uninterruptible power supply (UPS) support as well.
`
`NetWare 4.1: Very Good
`
`NetWare 4.l offers a wealth of features in both the host and client areas that provide fine basic security and allow
`network managers to decide how they want to balance security against user-fiiendliness. Novell has applied for C2
`security certification -- the so-called Department of Defense Red Book sta