Network Plus 2005 In Depth

472 Chapter 10 NETWARE-BASED NETWORKING

3.1workstation is running, the user is prompted with a Novell Login dialog box, as shown in Fig-

3.2ure 10-10. (In Figure 10-10, the Advanced option is selected so that you can see where a user’s

3.4context and server are specified.)

FIGURE 10-10 Novell Login dialog box

Client software can be installed individually on each workstation from a CD-ROM or from a file downloaded via Novell’s Web site. However, on a large network with many clients (particularly if they are located in different buildings or cities), installing software separately on each workstation becomes burdensome. To streamline the process, Novell provides utilities that automatically install client software (and updates) on all clients. This can occur directly from the NetWare server across a LAN or over the Internet. The network administrator controls how and when automated client installations proceed.

Even simpler than automatically installing client software, however, is not using client software at all. The next two client access methods do not require any special client software.

Native File Access

Earlier in this chapter, you learned that NetWare 6.5 uses NSS (Novell Storage Services), a proprietary file system, to manage its files, directories, and volumes. NetWare is capable of providing clients with direct access to NSS using the clients’ native file access protocols—that is, the type of file access protocol that the client expects to use when opening, reading, and saving files. For example, Linux clients can access and share NetWare 6.5 server resources using NFS, the native file access protocol used by UNIX-type of systems. Windows clients can use CIFS (Common Internet File System), the Windows file access protocol, and Macintosh clients can use AFP (AppleTalk Filing Protocol or Apple File Protocol), the file access protocol used on Apple Macintosh systems. Using native file access protocols means that users can browse folders and directories just as if they were connected to a server that runs the same file

3.12003 server or a Red Hat Linux client connected to a Linux server.

3.2All file access protocols are installed by default when you install NetWare 6.5. However, before

3.4clients can access the server through these protocols, the network administrator has to set up a network share for each protocol. This can be accomplished using the iManager tool. For example, suppose you have installed a NetWare 6.5 server, using the Basic File Server installation choice. Attached to your network are several Windows clients. To make a directory on the server’s hard disk appear to the client as a Windows folder, you would log on to iManager, then choose the CIFS/AFP option under the File Protocols heading. You would then specify a directory and share name and possibly change other parameters, such as whether the folder is available to an entire domain or a specific workgroup. After establishing the share, the folder would appear in the client’s My Network Places window (in the case of Windows XP).

Although this server access method does not require any special client software, it does impose some requirements on the client. The client must run the same protocols and software it would normally use to connect to a server natively running its file access protocols. For a Windows client, that means that the appropriate network protocols (such as TCP/IP) must be installed and properly configured and the client must run the Client for Microsoft Networks.

NetDrive is software that, when installed on Windows clients, allows them to access directories on a NetWare 6.5 server. Rather than using the Windows native file system access protocol, CIFS, NetDrive uses Internet protocols, such as HTTP and FTP. Before you can use NetDrive, the NetDrive client software must be installed on a workstation. After installation, NetDrive allows users to connect to the NetWare 6.5 server, navigate directories, and manage files through Windows Explorer. If you have ever used FTP client software, you might recognize the look and functioning of a NetDrive client as similar to a GUI FTP client. Figure 1011 shows the NetDrive connection dialog box.

FIGURE 10-11 NetDrive connection dialog box

474 Chapter 10 NETWARE-BASED NETWORKING

NET+ Browser-Based Access

3.1Perhaps the simplest way for users to access NetWare 6.5 files and directories is through a

3.2Web browser. Users can navigate directories and manage their files on a server through Nov-

3.4ell’s NetStorage tool. To use NetStorage, clients need only have the TCP/IP protocols installed and configured. NetStorage uses standard Internet application protocols, such as HTTP. To log on via NetStorage, users connect to a URL on the server. By default, this URL is the server’s IP address (or host name) plus /NetStorage. For example, if the server’s IP address is 10.11.11.11, a user would connect to the following URL: https://10.11.11.11/NetStorage. The NetStorage service would respond with a prompt to log on to the server. After authenticating, the user would see a list of his available folders and files on the server.

From a network administrator’s standpoint, however, NetStorage entails more work than providing client access through traditional client services or by using native file access protocols. The network administrator must have installed the optional NetStorage services and configured NetStorage on the server through iManager.

Internetworking with Other

Operating Systems

3.1it was only a few years ago. This is in part a result of Microsoft and Novell both adopting LDAP

3.4directory standards. In addition, both companies have offered user-friendly tools for integrating their directory data.

DirXML is Novell’s tool for integrating eDirectory and Windows Active Directory or Windows NT domain data. With DirXML installed and configured on both the NetWare and Windows servers in an organization, the servers can share directory data. When data in one directory is updated, DirXML synchronizes the change in the other directory or directories. A network administrator can configure DirXML so that either Active Directory or eDirectory is the authoritative source for directory information. Using DirXML allows users to log on to the network once and gain access to objects from both Active Directory and eDirectory. When DirXML is used in conjunction with the client access tools described in the previous section, users may not even know whether the programs, data, and devices they access are on a NetWare or Windows server.

To simplify NetWare access for users running the Linux NOS, Novell has packaged a group of tools and programs that are collectively known as Nterprise Linux Services. Nterprise Linux Services consist of client tools for accessing eDirectory, development tools for integrating Linux servers with DirXML, plus the browser-based file and print services discussed earlier in this chapter. Because Linux operating systems run TCP/IP by default, Linux clients can easily connect to NetWare servers through NetStorage. In addition, Novell has recently purchased two companies that write and distribute Linux software. In Novell’s next version of NetWare— NetWare 7.0—the NetWare and Linux kernels will be combined. This means that NetWare

CHAPTER SUMMARY Chapter 10 475

3.1of running it on a DOS-based system, as described in this chapter). As you might expect, run-

3.4ning NetWare on a Linux system will eliminate the need for specialized software that enables Linux clients to access a NetWare server. NetWare and Linux servers will also be fully compatible.

Chapter Summary

With NetWare 6.x, Novell has maintained its NOS’s traditional fileand printsharing strengths while adding browser-based management tools, popular opensource Web development tools, a fast, efficient file system, and flexible methods for managing multiple servers, volumes, and storage objects.

The minimum hardware requirements necessary to run a NetWare 6.5 server are: a PC with a Pentium II or AMD K7 or better processor, 512 MB of RAM, at least 2 GB of free hard disk space, a NIC, and a CD-ROM drive. In most cases, a faster

processor and additional RAM and hard disk space are preferable. For running additional services, such as Web development or remote access services, such upgrades may be necessary.

The NetWare Integrated Kernel is responsible for overseeing all critical NetWare server processes, such as multiprocessing, multitasking, and access to the server’s interrupts, memory, and I/O functions. The kernel is started by the program server.exe, which runs from a server’s DOS partition when a server boots up.

NLMs (NetWare loadable modules) are routines that enable the server to run a range of programs and offer a variety of services, such as protocol support and administrative tools. Each NLM consumes some of the server’s memory and processor resources.

Using ConsoleOne, administrators can manage servers, volumes, disks, and eDirectory objects. The Remote Manager tool allows an administrator to accomplish the same tasks using a browser interface from any computer on the network.

iManager is the primary means of managing eDirectory objects in NetWare 6.5. iManager is a browser-based utility that runs on any computer connected to the network.

NetWare 6.x’s preferred file system is called NSS (Novell Storage Services). NSS offers many advantages over traditional file systems (such as FAT), including faster access, more efficient use of memory, file compression, support of files or directories as large as 8 TB, support for sharing a single application over multiple servers, capability to limit user directory and volume size, and browser-based management tools.

Although NSS is unique to NetWare, NetWare 6.5 allows clients and other NOSs to access NSS files directly, by supporting certain file access protocols native to different clients. For example, it supports the NFS file system access protocol for UNIX or Linux clients and CIFS for Windows clients.

476Chapter 10 NETWARE-BASED NETWORKING

eDirectory is NetWare 6.x’s system for organizing and managing multiple servers and their resources, including storage devices, users, volumes, groups, printers, and so on. (In earlier NetWare versions, NetWare Directory Services, or NDS, contained this information.)

eDirectory information is stored in a database that supports LDAP (Lightweight Directory Access Protocol), which makes it compatible with other NOS and Internet directories.

The word “schema” refers to eDirectory’s defined set of object classes and their properties. In NetWare 6.5, the simplest schema is the one installed by default with eDirectory, which is called the base schema. If changes are made to the base schema, it becomes an extended schema.

eDirectory follows a tree structure, which is represented by the tree object at the top. From there, organizations and OUs (organizational units) branch out in a hierarchical manner and may contain other OUs or leaf objects, such as users or printers.

Each object has a context that indicates where that object belongs in the eDirectory tree. A context consists of an object’s OU names, arranged from most specific to most general, plus the organization name. Periods separate the OU names within the context.

NetWare recognizes two naming conventions for a user’s context: typeful and typeless. In typeful notation, the organization and organizational units are designated with the “O=“ and “OU=“ symbols, respectively. Typeless notation eliminates these symbols. OU=Receivables.OU=Acctg.O=Sutkin is an example of typeful notation, and Receivables.Acctg.Sutkin is an example of typeless notation.

Before you insert the NetWare CD and begin installing the operating system, you should consider many factors, including how you will structure the eDirectory tree, what the server’s function will be, what optional services you need to install, what licensing model you need to follow, and what the administrator ID and password will be.

User and Group objects can be created through one of three tools: ConsoleOne, Remote Manager, or iManager. Novell recommends using the iManager tool for this task.

Clients can connect to a NetWare 6.5 server, browse directories, and manage files in one of several different ways. Traditional client software, such as the Novell Client for Windows NT/2000/XP, can be installed on each client workstation to enable logging on. Otherwise, users can connect through native file system access protocols (for example, NFS for Linux and CIFS for Windows), or they may use Novell’s browser-based NetStorage tool.

NetWare 6.5 uses the DirXML tool to share data between eDirectory and Active Directory or Windows NT domains. To integrate Linux clients and servers, NetWare 6.5 provides the Nterprise Linux Services collection of client access and development tools.

Key Terms

base schema—The standard set of object classes and attributes installed as the default schema for NetWare’s eDirectory. The base schema can be extended through NetWare utilities.

boot partition—A partition on a computer’s hard disk from which the operating system software is launched.

BorderManager—An application from Novell that provides proxy and firewall services on NetWare servers.

console—The interface to a NetWare server and its kernel operations.

ConsoleOne—The graphical interface to NetWare server administration tasks. ConsoleOne can be used at the server or from another workstation connected to the same network.

context—The characteristic that indicates where an object belongs in an eDirectory tree. A context is made up of an object’s organizational unit names, arranged from most specific to most general, plus the organization name. Periods separate the organizational unit names in context.

DirXML—A Novell tool for integrating eDirectory and Windows Active Directory or Windows NT domain data.

eDirectory—The database of objects and their attributes in NetWare 6.x.

extended schema—In NetWare, a set of object classes and attributes that is different from the base schema.

GroupWise—An application from Novell that runs on NetWare servers and provides e-mail, messaging, scheduling, and collaboration services.

home directory—A directory on a server associated with a particular user account. A user has full access privileges to files and subdirectories within his home directory.

iManager—A browser-based tool for managing eDirectory in NetWare 6.x.

intraNetWare—Another term for NetWare version 4.11, the version in which support for Internet services was first introduced.

Monitor—A NetWare NLM that provides a text-based menu for viewing and modifying server parameters, such as protocols, bindings, system resources, and loaded modules.

NDS (NetWare Directory Services)—In NetWare 4.x and 5.x, the system of managing multiple servers and their resources, including users, volumes, groups, profiles, and printers, used with NetWare versions 4.x and 5.x. The NDS model was the precursor to eDirectory.

NetDrive—The client software that enables Windows workstations to connect to a NetWare 6.5 server using standard Internet protocols, such as FTP and HTTP. After connecting through NetDrive, a user can navigate the server’s directories and manage files as if navigating a Windows hard disk.

478 Chapter 10 NETWARE-BASED NETWORKING

NetStorage—A TCP/IP-based tool from Novell that allows users to navigate directories and manage files on a NetWare 6.x server.

NetWare 3.x—The group of NetWare versions that includes versions 3.0, 3.1, and 3.2.

NetWare 4.x—The group of NetWare versions that includes versions 4.0, 4.1, and 4.11.

NetWare 5.x—The group of NetWare versions that includes versions 5.0, 5.1, and 5.11.

NetWare 6.x—The group of NetWare versions that includes versions 6.0 and 6.5.

NetWare Directory Services—See NDS.

NetWare Integrated Kernel—The core of NetWare 6.x’s operating system. The NetWare Integrated Kernel manages multiprocessing, multithreading, and access to the server’s interrupts, memory, and I/O address space.

NetWare loadable module—See NLM.

NLM (NetWare loadable module)—A routine associated with a particular NetWare application or service. Each NLM consumes some of the server’s memory and processor resources (at least temporarily). The kernel requires many NLMs to run NetWare’s core operating system.

Novell Storage Services—See NSS.

NSS (Novell Storage Services)—The 64-bit file access and storage system installed by default and preferred for use on NetWare 6.x servers. NSS offers several benefits over traditional file systems such as FAT, including faster access, more efficient use of memory, support for files or directories as large as 8 TB, and up to a trillion files in a single directory.

Nterprise Linux Services—A group of tools and programs for integrating Linux computers into a NetWare 6.5 network. Nterprise Linux Services consists of client tools for accessing eDirectory, development tools for use with DirXML, plus browser-based file and print services.

pattern—In the context of installing the NetWare NOS, a choice of server type to install (for example, Basic NetWare File Server). Based on the pattern, the installation program will include files necessary for specific services or, if the Customized NetWare Server pattern is selected, prompt the user to select which services should be installed.

pool—A collection of storage objects in NetWare 6.x.

Remote Manager—A browser-based tool that enables network administrators to perform server and object management in NetWare 6.5.

tree object—In NetWare terminology, the object that represents the root of an eDirectory tree.

typeful—A way of denoting an object’s context in which the organization and organizational unit designators (“O=“ and “OU=,” respectively) are included. For example, OU=Inv.OU= Ops.OU=Corp.O=Sutkin.

typeless—A way of denoting an object’s context in which the organization and organizational unit designators (“O=“ and “OU=,” respectively) are omitted. For example, Inv.Ops.Corp. Sutkin.

X Server—A NetWare 6.x server’s graphical desktop. X Server loads by default when the server starts.

Review Questions

1.The _________________________ tool is used to access console commands through a Web browser on another computer on the network.

a.iManager

b.Remote Manager

c.Console Monitor

d.NDS

2.A(n) _________________________ consists of the objects, classes, and properties a network typically needs.

a.base schema

b.eDirectory

c.pool

d.X Server

3.Each object in an eDirectory has a _________________________ that indicates where that object belongs in the tree.

a.pool

b.monitor

c.pattern

d.context

4._________________________ is Novell’s tool for integrating eDirectory and Windows Active Directory or Windows NT domain data.

a.Remote Manager

b.X Server

c.DirXML

d.NetDrive

480Chapter 10 NETWARE-BASED NETWORKING

5.Contexts may be expressed in two ways: _________________________.

a.typeful and typeless

b.NetDrive and intraNetWare

c.DirXML and NetDrive

d.typeful and tree object

6.True or false? IntraNetWare was the first version of NetWare to supply Internet-related services, such as Web server software, IP address management, and FTP hosting.

7.True or false? Both Active Directory and eDirectory treat every networked resource as a separate object with distinct attributes, or properties.

8.True or false? The eDirectory tree must have at least two roots.

9.True or false? A home directory is a directory on the server where a user can store files.

10.True or false? LDAP notation uses periods to separate organization and organizational unit names.

11.NetWare’s _________________________ is responsible for overseeing all critical server processes.

12._________________________ are routines that enable the server to run a range of programs that offer a variety of services, such as protocol support and Web publishing.

13._________________________ is a NetWare 6.5 server’s graphical desktop that is loaded by default when the server starts.

14.A server running NetWare 6.5 and using NSS may have up to four partitions, and one of them must be a(n) _________________________ partition.

15._________________________ is NetWare 6.5’s directory database.

Chapter 11

In-Depth TCP/IP

Networking

After reading this chapter and completing the exercises, you will be able to:

■Understand methods of network design unique to TCP/IP networks, including subnetting, CIDR, NAT, and ICS

■Explain the differences between public and private networks

■Describe protocols used between mail clients and mail servers, including SMTP, POP3, and IMAP4

■Employ multiple TCP/IP utilities for network discovery and troubleshooting