NETWORK+ GUIDE TO NETWORKS, FOURTH EDITION - CHAPTER 10 pptx

Network+ Guide to Networks, Fourth Edition Chapter 10 Netware-Based Networking Objectives • Identify the advantages of using the NetWare network operating system • Describe NetWare’s server hardware requirements • Understand NetWare’s file system and directory structure • Plan for and perform a simple NetWare server installation • Explain how NetWare supports multiple clients and integrates with other network operating systems Network+ Guide to Networks, 4e Introduction to NetWare • Novell released first NetWare in 1983 – NetWare versions prior to 4.11 require IPX/SPX protocol suite – Refined to run over TCP/IP in version 4.11 • NetWare 6.5’s key features: – Support for multiple processors, multitasking, and SMP – Flexible use of virtual and physical memory – eDirectory – Simple, centralized management of multiple clients, resources, and services Network+ Guide to Networks, 4e Introduction to NetWare (continued) • NetWare 6.5’s key features (continued): – Multiple, integrated Web development and delivery services – Support for multiple modern protocols – Excellent integration with other NOSs and support for many different clients – Remote client services – Built-in clustering services – Provisions for monitoring server performance, automatic backups, and resource utilization Network+ Guide to Networks, 4e Introduction to NetWare (continued) • Noteworthy changes in NetWare 6.5: – iManager – DirXML – Capability for continuously backing up a server as it runs – Server Consolidation Utility – Popular open source Web development tools – Virtual Office – Branch Office – Nterprise Linux Services Network+ Guide to Networks, 4e NetWare Server Hardware Requirements Table 10-1: Minimum hardware requirements for NetWare 6.5 servers Network+ Guide to Networks, 4e A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel • Core of NetWare 6.5 OS – Oversees all critical server processes – Started by server.exe, which runs from server’s DOS partition • Takes advantage of SMP – Up to 32 processors • NetWare loadable modules (NLMs): Enable server to run variety of programs and services – Each consumes some of server’s memory and processor resources Network+ Guide to Networks, 4e A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) • Load or unload NLMs through server’s console – Enables network administrator to manage disks and volumes and modify server parameters – Monitor: text-based menu system – ConsoleOne: graphical menu system • X Server: NetWare 6.5 server’s graphical desktop • Remote Manager: access console commands via Web browser on another network computer Network+ Guide to Networks, 4e A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) Figure 10-1: A ConsoleOne client window Network+ Guide to Networks, 4e A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) Figure 10-2: Remote Manager Health Monitor Network+ Guide to Networks, 4e 10 Establishing Users and Groups (continued) Figure 10-8: The iManager Create User window Network+ Guide to Networks, 4e 28 Establishing Users and Groups (continued) Figure 10-9: The iManager Create Group window Network+ Guide to Networks, 4e 29 Client Services • Several ways for different types of clients to access server and its resources – Traditional client access – Native file access – Browser-based access Network+ Guide to Networks, 4e 30 Traditional Client Access • Clients running Windows, Macintosh, and UNIXtype of OSs traditionally connected via a Novell client specifically designed for that client – Client must have appropriate protocol suite installed – May require additional client software • Novell provides utilities to automatically install client software (and updates) on all clients Network+ Guide to Networks, 4e 31 Traditional Client Access (continued) Figure 10-10: Novell Login dialog box Network+ Guide to Networks, 4e 32 Native File Access • NetWare capable of providing clients with direct access to NSS using clients’ native file access protocols – Users can browse folders and directories as if connected to server running same file access protocols • All file access protocols installed by default – Network administrator must set up network share for each protocol • Via iManager Network+ Guide to Networks, 4e 33 Native File Access (continued) • Client must run same protocols and software normally used to connect to a server natively running its file access protocols • NetDrive: When installed on Windows clients, allows access to directories on NetWare 6.5 server – Uses IPs such as HTTP and FTP Network+ Guide to Networks, 4e 34 Native File Access (continued) Figure 10-11: NetDrive connection dialog box Network+ Guide to Networks, 4e 35 Browser-Based Access • Users can navigate directories and manage files via Novell’s NetStorage tool – Only need to have TCP/IP protocols installed and configured – Uses standard Internet application protocols – Users connect to URL on server • By default, server’s IP address (or host name) plus /NetStorage Network+ Guide to Networks, 4e 36 Internetworking with Other Operating Systems • Novell has adopted LDAP directory standards • DirXML: Novell’s tool for integrating eDirectory and Windows Active Directory or Windows NT domain data – Can synchronize Windows and Novell server’s directories – Can configure so that Active Directory or eDirectory is authoritative source for directory information Network+ Guide to Networks, 4e 37 Internetworking with Other Operating Systems (continued) • Nterprise Linux Services: Simplifies NetWare access for users running Linux NOS – Client tools for accessing eDirectory – Development tools for integrating Linux servers with DirXML – Browser-based file and print services • Novell purchased two companies that write and distribute Linux software – NetWare 7.0 will combine NetWare and Linux kernels • Full compatibility Network+ Guide to Networks, 4e 38 Summary • With NetWare 6.x, Novell has maintained its NOS’s traditional file- and print-sharing strengths while adding browser-based management tools; popular open source Web development tools; a fast, efficient file system; and flexible methods for managing multiple servers, volumes, and storage objects • The NetWare Integrated Kernel is responsible for overseeing all critical NetWare server processes • NLMs are routines that enable the server to run a range of programs and offer a variety of services Network+ Guide to Networks, 4e 39 Summary (continued) • Using ConsoleOne, administrators can manage servers, volumes, disks, and eDirectory objects • iManager is the primary means of managing eDirectory objects in NetWare 6.5 • NSS offers many advantages over traditional file systems, including faster access, more efficient use of memory, file compression, support of files or directories as large as TB, support for sharing a single application over multiple servers, capability to limit user directory and volume size, and browser-based management tools Network+ Guide to Networks, 4e 40 Summary (continued) • 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 • The word “schema” refers to eDirectory’s defined set of object classes and their properties • eDirectory follows a tree structure • Each object has a context that indicates where that object belongs in the eDirectory tree • NetWare recognizes two naming conventions for a user’s context: typeful and typeless Network+ Guide to Networks, 4e 41 Summary (continued) • User and Group objects can be created through ConsoleOne, Remote Manager, or iManager • Clients can connect to a NetWare 6.5 server, browse directories, and manage files in one of several different ways • NetWare 6.5 uses the DirXML tool to share data between eDirectory and Active Directory or Windows NT domains • Nterprise Linux Services integrates NetWare and Linux clients and servers Network+ Guide to Networks, 4e 42 ... typeless contexts Network+ Guide to Networks, 4e 17 eDirectory (continued) Figure 1 0-5 : A simple eDirectory tree Network+ Guide to Networks, 4e 18 eDirectory (continued) Figure 1 0-6 : Ways of grouping... other NOS and Internet directories Network+ Guide to Networks, 4e 14 eDirectory (continued) Figure 1 0-4 : eDirectory objects Network+ Guide to Networks, 4e 15 eDirectory (continued) • Schema: defined... eDirectory tree Network+ Guide to Networks, 4e 19 eDirectory (continued) Figure 1 0-6 (continued): Ways of grouping objects in an eDirectory tree Network+ Guide to Networks, 4e 20 eDirectory (continued)