HP 9000 Networking NetWare 4.1/9000 NetWare Client for DOS and MS Windows User Guide ® HP Part No. J2771-90015 Printed in U.S.A.
Notice Notice Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. This product is based in whole or in part on technology developed by Novell, Inc.
Printing History Printing History The manual printing date and part number indicate its current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes.
Preface Preface Introduction NetWare® Client™ for DOS and MS Windows User Guide has three purposes: to help you set up and install your client software, to help you set up and connect your client workstations to the network, and to introduce client User Tools for managing access and connections on a NetWare network. This manual is for users and supervisors new to NetWare client networking and for network supervisors responsible for setting up and managing NetWare client workstations.
Preface print queues, etc. Contents This section is divided into seven chapters as shown below. Purpose Chapter To help prepare the hardware, determine your network board settings, and prepare the client workstation software for installation of the NetWare Client software Chapter 4, “Preparing to Install or Upgrade the NetWare Client Software” To guide you through the steps for installing the NetWare Client software for DOS and MS Windows workstations.
Preface and client-server solutions for your client workstations. Contents This section contains one chapter. Purpose To learn how to use the Source Routing driver Chapter Chapter 10, “Setting Up Source Routing Support for a Token-Ring Network” Management Services Overview The Novell® system management technology provides advanced solutions to centrally manage and control your corporate computing environment.
Preface Contents This section includes the chapter shown below.
Preface Purpose To learn how to use the WSUPGRD utility for upgrading client workstations with the most current ODI-based NetWare Client software Chapter Appendix B, “Using the WSUPGRD Utility” Documentation Conventions This manual uses the following Novell® conventions: Asterisk ( * ) An asterisk denotes a trademarked name belonging to a third-party company. Novell trademarks are denoted with specific trademark symbols (®, ™, etc.).
Preface uppercase or lowercase letters. DOS Filenames, Directory Names, and Pathnames DOS filenames, directory names, and pathnames are shown in uppercase letters. For example, AUTOEXEC.BAT. Because DOS is not case-sensitive, you can type these names in uppercase or lowercase letters. Ellipses Ellipses in syntax examples indicate that parameters, options, or settings can be repeated. For example, in the command LOGIN SERVER1/SUPERVISOR /option...
Preface with the “Warning” icon to the left of this text. Key Names Angle brackets surround the name of a key. For example, corresponds to the Enter key on your keyboard. + means hold down the Ctrl key and simultaneously type the letter c (in lowercase, in this case). NET.CFG File Section Headings and Parameter Settings NET.CFG section headings and parameter settings are shown in uppercase when used as a reference item and lower case when used in syntax or working examples.
Preface contents in uppercase or lowercase letters. Options In syntax examples, braces indicate that you are required to choose one of the enclosed options. For example, the following notation means that you must include a 0 or a 1 in the command: {0, 1} Square Brackets In syntax examples, boldface type enclosed in square brackets indicates command options that you can type as needed.
Preface you type the name of a computer on your network in place of remote_host. Supplemental Documentation The following publications provide supplemental information specifically related to the NetWare Client for DOS and MS Windows technology and software: • “The Functions and Operations of the NetWare DOS Requester 1.1,” Novell Application Notes, May 94, Vol. 5, No. 5 (Novell part no.
Preface 93 (Novell part no. 164-000032-004) • “Understanding Token-Ring Source Routing,” NetWare Application Notes, May 91 (Novell part no. 164-000030-005) • “Workstation Memory Management: Using QEMM386, 386 To The Max, and MS-DOS 6,” NetWare Application Notes, Dec 93 (Novell part no.
Preface xiv
Contents 1 Understanding Networking Basics Overview 1-2 Introduction 1-3 Network Types 1-4 Peer-to-Peer Networks 1-4 Client-Server Networks 1-4 Network Connections 1-5 Physical Connection 1-5 Logical Connection 1-6 Network Resources 1-7 Resources for NetWare 2 and NetWare 3 Resources for NetWare 4 1-7 1-7 The Structure of the File System 1-10 The File Structure for NetWare 2 and NetWare 3 The File Structure for NetWare 4 1-11 1-10 Network Users 1-13 NetWare 2 and NetWare 3 Users 1-13 NetWare 4 Users
Contents Network Printing 1-20 Where to Go from Here 1-22 Additional Information 1-23 For NetWare 2.2, NetWare 3.11, and NetWare 3.
Contents Receiving Broadcast Messages 2-18 Printing to Network Queues 2-19 Where to Go from Here 2-21 Additional Information 2-22 For NetWare 2 and NetWare 3 For NetWare 4 2-22 2-22 3 Understanding Client Tools Overview 3-2 Introduction 3-3 Prerequisites 3-4 Starting NetWare User Tools for DOS (NETUSER) 3-5 Prerequisites 3-5 Procedure 3-5 Using NetWare User Tools for DOS (NETUSER) 3-7 Accessing Online Help 3-7 Using NetWare User Tools for DOS (NETUSER) Options 3-7 Exiting NetWare User Tools for DOS (
Contents Using the Menu Bar 3-12 Accessing Online Help 3-13 Using NetWare User Tools for MS Windows Options 3-13 Accessing and Changing Directory and File Attributes 3-24 Procedure 3-24 Optimizing the NetWare Client Software for MS Windows 3-25 Exiting NetWare User Tools for MS Windows 3-27 Additional Information 3-28 For NetWare 2 and NetWare 3 For NetWare 4 3-28 3-28 4 Preparing to Install or Upgrade the NetWare Client Software Overview 4-2 Introduction 4-3 Preparing Client Workstations 4-4 Setting Up
Contents Using a Third-Party ODI LAN Driver 4-17 Upgrading Your IPX Driver to ODI 4-18 Where to Go from Here 4-19 5 Installing or Upgrading NetWare Client Software Overview 5-2 Introduction 5-3 Running the NetWare Client Installation Program 5-4 Prerequisites 5-4 Loading the Installation Program 5-4 Selecting a Destination Directory for the NetWare Client Files Updating System Files on Your Workstation 5-7 Installing Support for MS Windows 5-8 Installing LAN Drivers 5-12 Copying Files 5-15 5-6 What Happ
Contents Setting Up Network Directories and Files 5-25 Setting Up Individual Client Workstations and User Directories 5-26 Loading the NetWare Client Software 5-28 Using Two Network Boards 5-29 Reasons for Having Two Network Boards 5-29 Modifying Client Workstation Files for Two Network Boards 5-30 Where to Go from Here 5-35 6 Setting Up NetWare Client Workstations to Log In Overview 6-2 Introduction 6-3 Modifying the NET.
Contents Additional Information 6-11 7 Logging In from a NetWare Client Workstation Overview 7-2 Introduction 7-3 Prerequisites 7-4 Logging In from the DOS Prompt 7-5 Logging In to a NetWare 2 or NetWare 3 Network 7-5 Logging In to a NetWare 4 Network 7-6 Logging In to NetWare 4 with a NetWare Bindery Connection 7-6 Logging In from MS Windows 7-8 Logging Out of a NetWare Server or Network 7-9 Logging Out from DOS 7-9 Logging Out from MS Windows 7-9 Where to Go from Here 7-11 8 Setting Up and Managing
Contents The NetWare User Tools for DOS (the NETUSER Utility) 8-10 The NetWare User Tools for MS Windows (the NWUSER.EXE Program) 8-11 Using Universal Naming Convention (UNC) Paths in MS Windows 8-14 Program Group (.
Contents Introduction 10-3 Installing Source Routing on the Server 10-6 Installing the ROUTE.COM and NetWare Client Files 10-8 Copying the Files to the NetWare Client Directory Automatically 10-8 Copying the Files to the NetWare Client Directory Manually 10-8 Modifying the DOS System and NetWare Client Configuration Files 10-10 Modifying the CONFIG.SYS File 10-10 Procedure 10-10 Modifying the STARTNET.
Contents Modifying the STARTNET.BAT File 11-8 Modifying the NET.CFG File 11-10 Sample NET.CFG File for Desktop SNMP Services 11-11 Configuring the HRMIB.INI File 11-12 Sample Configuration File (HRMIB.INI) for the HRMIB.
Contents Introduction B-3 Prerequisites B-4 Using the WSUPGRD /I Option B-5 Using WSUPGRDE to Upgrade Network Board Drivers B-6 Upgrading IPX LAN Drivers from the Command Line B-6 Upgrading IPX LAN Drivers from a Login Script or Profile B-6 Additional Information B-12 xxv
Contents xxvi
1 Understanding Networking Basics 1-1
Understanding Networking Basics Overview Overview This chapter provides a basic overview of the concepts for adding a client workstation to your network and for using the workstation.
Understanding Networking Basics Introduction Introduction In order to take advantage of your NetWare® client workstations, you need to understand how your client workstations relate to the NetWare operating system they are connecting to and to review basic networking concepts. Users connecting to NetWare 2 and NetWare 3™ need to understand how their client workstations relate to NetWare bindery server networks.
Understanding Networking Basics Network Types Network Types A network links two or more computers together to share resources and peripherals (such as disk drives, printers, and data). There are two categories of networks: peer-to-peer and client-server. Peer-to-Peer Networks The simplest peer-to-peer network has two workstations connected together, each able to use the resources of the other. All workstations on a peer-to-peer network are (or can be) equal.
Understanding Networking Basics Network Connections Network Connections You must make two types of connections to use shared network resources: • A physical connection • A logical connection Physical Connection In order for resources and information to be shared on a network, servers, client workstations, and other network devices must be physically connected. Each device on the network must have a network board.
Understanding Networking Basics Network Connections Logical Connection After the physical connection to the network is made, you must make a logical connection to access the network services. To make the logical connection on a NetWare network, you must prove that you are an authorized user. This is done when you log in to the network and provide the NetWare operating system your user identification and a valid password. By logging in to a network or attaching to a server, you make a logical connection.
Understanding Networking Basics Network Resources Network Resources After connecting to a NetWare network, you have access to physical and logical resources across the network. A definition for each resource is maintained in a database used by the NetWare operating system. An example of this is a print queue or group name. How you interact with the resource database depends greatly on which version of the NetWare operating system you are running.
Understanding Networking Basics Network Resources Users can access any network service, such as file services or print services, without having to know the physical location of the server that provides the service. Components of a Directory Tree NetWare Directory Services operates in a logical organization called the Directory tree. It is called a Directory tree because objects are stored in a hierarchical tree structure, starting with the root object and branching out.
Understanding Networking Basics Network Resources Container object Leaf object Container object Leaf object Leaf object Leaf object Leaf object Container object Leaf object Leaf object Leaf object Figure 1-3 Example of a Directory Tree To refer to where an object is in the Directory tree, the term context is used. The position of the object within its container is its context. For example, in the previous figure, the context of User object Jody is Jody.Development.MedTech.
Understanding Networking Basics The Structure of the File System The Structure of the File System The bindery and NetWare Directory Services help you manage network resources such as NetWare servers and printers, but they do not provide control over the file system (volumes, directories, and files). Graphical and text utilities help you manage both network resources and the file system. The file system structure is separate from the bindery or NetWare Directory Services structure.
Understanding Networking Basics The Structure of the File System Identify volume by server and volume name. Separate directory, subdirectory, and file with a backslash. Separate volume and directory with a colon. Directory path name TSERVER\SYS : Products \ Domestics \ Sales.
Understanding Networking Basics The Structure of the File System Identify Volume object by its context. Separate directory, subdirectory, and file with a backslash. Separate volume and directory with a colon. Directory path name TSERVER_SYS.Test.MedTec : Products \ Domestics \ Sales.rpt File File system structure Subdirectory Directory Server volume Figure 1-5 NetWare 4 File System Structure and Directory Path The position of a file within the file system is its directory path.
Understanding Networking Basics Network Users Network Users Access to a NetWare network is possible only if you are identified to the NetWare operating system as a network user. NetWare 2 and NetWare 3 Users NetWare 2 and NetWare 3 allow for four types of network users, which have varying levels of responsibility on the network: Regular network users are the people who work on the network. They can run applications and work with files according to the rights assigned to them.
Understanding Networking Basics Network Users When User ADMIN is created on the first NetWare 4 server installed, it can manage all objects because it has the Supervisor right to every object. Initially, ADMIN can also manage all directories and files on every volume in the Directory tree. User ADMIN does not have any special significance like the user SUPERVISOR did in previous versions of NetWare.
Understanding Networking Basics Login Login Before you can use any of the network services, you must attach to and log in to the network. Bindery users log in to or attach to individual servers. Therefore, they need a password for each server they are logging in to. NetWare Directory Services users log in to the network. Therefore, they need only one password to gain access to all network resources that they have the right to use.
Understanding Networking Basics Login LOGIN is usually executed from the AUTOEXEC.BAT or another batch file. There is some difference in the command line syntax for the particular NetWare versions. If you are using NetWare 3.12, see NetWare 3.12 Utilities Reference for a complete description of the utility. If you are using NetWare 4, see NetWare 4 Utilities Reference for a complete description of the utility.
Understanding Networking Basics Network Security Network Security Security is vital in maintaining a productive network environment. NetWare provides an extensive security system to protect the data on the network. Network Security Levels NetWare 2, 3, and 4 have three levels of security that can be used separately or in various combinations. File System Security File system security consists of rights security and attributes security.
Understanding Networking Basics Network Security changes are made when a file is modified Login and Password Security Login and password security controls who can access the network. The network supervisor uses login and password security to • Assign usernames to users of the network • Require passwords Additional password restrictions include a minimum password length, periodic password changes, unique passwords, and a number of grace logins after password expiration.
Understanding Networking Basics Network Security Object rights control what a trustee can do with an object. These rights control the object as a single piece in the Directory tree, but they don’t allow access to information stored within that object—unless the Supervisor object right or property rights are granted. Property rights control a trustee’s access to information stored within the object—that is, the information stored in the object’s properties.
Understanding Networking Basics Network Printing Network Printing Non-Networked Printing A standalone workstation can only print to a printer attached to one of its ports. Print jobs are sent directly to the attached printer. As shown in the following figure, a printer connected to a standalone workstation allows print jobs from only that workstation to access the printer.
Understanding Networking Basics Network Printing Client Workstations NetWare server Print queue Figure 1-7 Printer Print server Network Printing If you are using NetWare 3.12, see NetWare 3.12 Print Server for more information on network printing. If you are using NetWare 4, see NetWare 4 Print Services for a complete description of the process.
Understanding Networking Basics Where to Go from Here Where to Go from Here With a basic understanding of networking and NetWare network functions, you are ready to upgrade or install your NetWare client workstation.
Understanding Networking Basics Additional Information Additional Information For NetWare 2.2, NetWare 3.11, and NetWare 3.12 Topic Reference NetWare bindery “Bindery” in NetWare 3.12 Concepts NetWare file system (directory structure) “Directory structure” in NetWare 3.12 Concepts NetWare drives “Drive mapping” in NetWare 3.12 Concepts NetWare volumes “Volume” in NetWare 3.12 Concepts Network printing “Printing” in NetWare 3.12 Print Server Print queues “Print queue” in NetWare 3.
Understanding Networking Basics Additional Information Topic Reference Network printing NetWare 4 Print Services Print queues “Print queue” in NetWare 4 Concepts Print servers “Print server” in NetWare 4 Concepts Printers “Printer” in NetWare 4 Concepts 1-24
2 Understanding the NetWare Client Software 2-1
Understanding the NetWare Client Software Overview Overview This chapter introduces and describes the NetWare® DOS Requester™ and other NetWare Client™ software that provides the interface between the network and your DOS and Microsoft (MS) Windows client workstations. The following topics are covered in this chapter. Topic The NetWare DOS Requester Architecture The NetWare Protocols and Transports The Link Support Layer Interface The ODI LAN Driver The NET.
Understanding the NetWare Client Software Introduction Introduction The core components of the NetWare DOS and MS Windows environment are four terminate-and stay-resident (TSR) programs, listed and described in the following table.
Understanding the NetWare Client Software Introduction When the NetWare Client components are loaded, each component uses a file called NET.CFG to determine the specific software settings it should use. See Chapter 2, “NET.CFG Options Reference,” in NetWare Client for DOS and MS Windows Technical Reference for information.
Understanding the NetWare Client Software The NetWare DOS Requester Architecture The NetWare DOS Requester Architecture The NetWare DOS Requester consists of a group of files that provide NetWare support for DOS and MS Windows client workstations. These files consist of a number of Virtual Loadable Module™ (VLM) files and a single executable file (VLM.EXE) which manages operation of the .VLM files.
Understanding the NetWare Client Software The NetWare DOS Requester Architecture DOS NETX DOS NetWare DOS Requester VLM.EXE VLM.
Understanding the NetWare Client Software The NetWare DOS Requester Architecture Table 2-2 Key Components of the NetWare DOS Requester Protocol Layer Service and Module NetWare Services NWP.VLM Description NWP, the NetWare protocol multiplexor, handles each particular network implementation through these child VLM programs: • BIND.VLM for NetWare 2 and NetWare 3™ bindery servers • NDS.VLM for NetWare 4™ NetWare Directory Services™ servers • PNW.
Understanding the NetWare Client Software The NetWare DOS Requester Architecture Transport Protocol Layer This layer is responsible for maintaining connections, providing packet transmissions between connections and performing other transport-specific functions. The IPXNCP module uses the IPX™ protocol as a transport mechanism. The AUTO.
Understanding the NetWare Client Software The NetWare DOS Requester Architecture Backwards Compatibility with NETX Applications The NETX.VLM program provides backwards compatibility with NETX and other older versions of the shell. Therefore, you do not need to run NETX or other versions of the shell with the NetWare DOS Requester. Nevertheless, because the NetWare DOS Requester is a redirector on the back end of DOS, it performs differently than the NetWare Shell software under specific conditions.
Understanding the NetWare Client Software The NetWare DOS Requester Architecture applications. • Takes advantage of memory-swapping technology and DOS redirection capability. • Includes the Packet Burst protocol and Large Internet Packet (LIP) support. • Supports the installed base of NetWare users by providing backward compatibility with NETX. • Supports the NetWare Directory Services architecture in NetWare 4 software.
Understanding the NetWare Client Software The NetWare Protocols and Transports The NetWare Protocols and Transports The NetWare software that allows client workstations to communicate and be understood on the network is separated into two components, consisting of a protocol, which manages data, and a transport, which manages application messages. This can be provided by one piece of software or by many.
Understanding the NetWare Client Software The NetWare Protocols and Transports The targeting ability of IPXODI is important but, by itself, does not guarantee successful delivery of a data transmission. IPXODI transmits data packets as datagrams (self-contained packages that move independently from source to destination) and, therefore, can deliver the packets only on a best-effort basis. Delivery is guaranteed only when using the SPX protocol.
Understanding the NetWare Client Software The NetWare Protocols and Transports Streams Transport Layer Interface (TLI), MS Windows Sockets, and NetBIOS interface using the RFC-1001/1002 compliant B-node (broadcast) type of the NetBIOS protocol. NetWare TCP/IP supports ODI LAN drivers for the following frame types: • Ethernet 802.2 • Token-ring 802.5 • FDDI • Ethernet 802.
Understanding the NetWare Client Software The ODI LAN Driver The ODI LAN Driver Every transmission prepared by the NetWare DOS Requester must pass through the network board connecting the workstation to the network. The LAN driver, often referred to as a Multiple Link Interface Driver™ (MLID™), makes the connection between the physical network board and the logical routines and programs that use it. A LAN driver is linked both to the specific network board and to the network protocol.
Understanding the NetWare Client Software The NET.CFG File The NET.CFG File NET.CFG is a specialized text file that you create with any ASCII text editor and include on a workstation boot diskette with any other necessary boot files. The NET.CFG file replaces the SHELL.CFG file. Like the DOS CONFIG.SYS file, the NET.CFG file contains configuration values of the LAN drivers and NetWare DOS Requester that are read and interpreted when your client workstation starts up.
Understanding the NetWare Client Software Novell MS Windows Support Novell MS Windows Support The following sections explain the integration of MS Windows with the NetWare client software: • Accessing the Network from an MS Windows Application • Running DOS Applications in Real or Standard Mode • Running DOS Applications in Enhanced Mode • Receiving Broadcast Messages • Printing to Network Queues Accessing the Network from an MS Windows Application In addition to the core NetWare client software—
Understanding the NetWare Client Software Novell MS Windows Support MS Windows DOS NetWare MS Windows application NETWARE.DRV DOS Requester IPXODI LSL MLID Network board Network Figure 2-4 Accessing the Network from an MS Windows Application For example, when you use the NetWare User Tools “NetWare Drives Connections” to connect to a network drive, your client workstation uses this driver.
Understanding the NetWare Client Software Novell MS Windows Support MS Windows DOS NetWare MS Windows application DOS application NETWARE.DRV VIPX.386 DOS Requester IPXODI LSL MLID Network board Network Figure 2-5 Running a DOS Application in Enhanced Mode For example, if you are running MS Windows in enhanced mode and you choose the DOS prompt icon to go to a DOS window and check your email, your client workstation uses this file.
Understanding the NetWare Client Software Novell MS Windows Support MS Windows DOS NetWare MS Windows application Display message dialog. NWPOPUP.EXE Coordinate message reception. NETWARE.DRV VNETWARE.386 DOS Requester IPXODI Notify MS Windows of message. LSL MLID Network board Network Figure 2-6 Broadcast message Receiving a Broadcast Message For example, if the secretary sends a message informing you that paychecks have arrived, your client workstation uses this driver.
Understanding the NetWare Client Software Novell MS Windows Support Formats application information. Creates files containing formatted print job. Stores print jobs until printer is ready. Print driver Network print queue Accepts and prints jobs. GDI MS Windows application Figure 2-7 Graphics Device Interface Printer Printing to a Network Queue For example, if you print a text file from the MS Windows Notepad application, your client workstation uses these components.
Understanding the NetWare Client Software Where to Go from Here Where to Go from Here With a basic understanding of the NetWare Client software, you are ready to prepare for upgrading or installing your NetWare client.
Understanding the NetWare Client Software Additional Information Additional Information For NetWare 2 and NetWare 3 Topic Reference IPXODI “IPXODI.COM” in NetWare 3.12 Concepts Link Support Layer (LSL) “Link Support Layer” in NetWare 3.12 Concepts Network board drivers “LAN driver” in NetWare 3.12 Concepts NETX “NetWare Shell Files” in NetWare 3.
3 Understanding Client Tools 3-1
Understanding Client Tools Overview Overview This chapter briefly explains how you can use the NetWare® User Tools to perform common network tasks.
Understanding Client Tools Introduction Introduction Use the NetWare User Tools to display and modify the current status of your client workstation, drive mappings, servers, printers, queues, volumes, and other necessary information. NetWare User Tools are compatible with NetWare 2, NetWare 3™, and NetWare 4™ networks. NetWare User Tools are available for both DOS and Microsoft (MS) Windows.
Understanding Client Tools Prerequisites Prerequisites Before you start using the NetWare User Tools, you should complete these tasks: • Install or upgrade your client software • Complete the procedures in Chapter 5, “Installing or Upgrading NetWare Client Software.
Understanding Client Tools Starting NetWare User Tools for DOS (NETUSER) Starting NetWare User Tools for DOS (NETUSER) The NetWare User Tools for DOS are found in the NETUSER utility. This utility is available only in NetWare 4 packages. It is not included in the NetWare Client Kit or other versions of NetWare. Because NETUSER is a NetWare 4 utility, you need to already have a connection to the network and be logged in to a NetWare 4 network. The utility files are found in the SYS:PUBLIC directory.
Understanding Client Tools Starting NetWare User Tools for DOS (NETUSER) For example, if you mapped network drive G: to PUBLIC, type G: 3 Start NETUSER by typing NETUSER 3-6
Understanding Client Tools Using NetWare User Tools for DOS (NETUSER) Using NetWare User Tools for DOS (NETUSER) The NetWare User Tools for DOS provides you with a graphical way of accessing network resources, such as volumes, directories, printers, and users. The following figure shows an example of the NETUSER utility screen.
Understanding Client Tools Using NetWare User Tools for DOS (NETUSER) Messages Use “Messages” to • Send a brief message from your client workstation to one or more users or groups on the network • Disable or enable incoming messages sent from other clients Drives Use “Drives” to • View current drive mappings • Create or change network drive mappings • Map a drive to a fake root directory • Map the next available drive Attachments Use “Attachments” to • Create or delete network attachments
Understanding Client Tools Exiting NetWare User Tools for DOS (NETUSER) Exiting NetWare User Tools for DOS (NETUSER) You exit NETUSER through the “Exit?” confirmation prompt. You can display this prompt in two ways: • Press until the “Exit?” confirmation prompt appears. • Press + anywhere within NETUSER to display the “Exit?” confirmation prompt. To exit NETUSER, choose “Yes” when prompted.
Understanding Client Tools Starting NetWare User Tools for MS Windows Starting NetWare User Tools for MS Windows The NetWare User Tools for MS Windows are found in the NETWARE.DRV file. These tools are available in NetWare 3.12, NetWare 4, and NetWare Client Kits for DOS and MS Windows packages. This version of the NETWARE.DRV (3.01 or later) is compatible only with the NetWare DOS Requester. For MS Windows support of NetWare Shell files, such as NETX, use version 2.02 of the NETWARE.DRV.
Understanding Client Tools Using NetWare User Tools for MS Windows Using NetWare User Tools for MS Windows The NetWare User Tools for MS Windows provides you with graphical access to network resources and allows you to configure and customize your client workstation connections.
Understanding Client Tools Using NetWare User Tools for MS Windows Table 3-1 Quick Keys Tool Quick Key User-Defined Button 1 +<1> User-Defined Button 2 +<2> Using the Menu Bar The menu bar (see Figure 3-2) shows menu options you can use. To complete a task, first choose the button that corresponds with the task or connection you are performing.
Understanding Client Tools Using NetWare User Tools for MS Windows Accessing Online Help To see a list of commands and the procedures you can perform with NetWare User Tools for MS Windows, choose the “Help” button from the menu bar. Using NetWare User Tools for MS Windows Options NetWare Drive Connections Use the “NetWare Drive Connections” window (see Figure 3-3) to map network resources in the Directory tree and file system to your client workstation drives.
Understanding Client Tools Using NetWare User Tools for MS Windows Using the “NetWare Drive Connections” Window When using this window, remember • Before using “NetWare Drive Connections,” you must first log in to a Directory Services tree or server that contains the object you want to connect to. • NetWare User Tools for MS Windows recognizes all drive mappings that existed before MS Windows was started.
Understanding Client Tools Using NetWare User Tools for MS Windows Figure 3-4 “NetWare Printer Connections” Window Using the “NetWare Printer Connections” Window When using this window, remember • Before using “NetWare Printer Connections,” you must first log in to a server or Directory tree that contains the object you want to connect to. • NetWare User Tools for MS Windows recognizes all print queue captures that existed before MS Windows was started.
Understanding Client Tools Using NetWare User Tools for MS Windows Setting LPT Options Choose the “LPT Settings” button at the bottom of the “NetWare Printer Connections” window to access the “Printer Options for LPT” window. The following table lists and explains the setting options that you can assign. Table 3-2 LPT Setting Options Option Explanation Notify Provides a confirmation of print job completion. Formfeed Places a page break between print jobs.
Understanding Client Tools Using NetWare User Tools for MS Windows NetWare Connections Use the “NetWare Connections” window (see Figure 3-5) to connect to Directory trees and network servers. Select the resource you want to connect to in the “Resources” list, and then choose the “Login” button at the bottom of the window.
Understanding Client Tools Using NetWare User Tools for MS Windows To attach to more than eight servers, you should add the CONNECTIONS parameter to the NetWare DOS Requester section in your NET.CFG file. See “CONNECTIONS=number” under “NetWare DOS Requester Option,” in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for more information. • If you are connected to a NetWare 4 network, log out of one Directory tree before logging in to another one.
Understanding Client Tools Using NetWare User Tools for MS Windows Figure 3-6 “NetWare Set Password” Dialog NetWare Send Message Use the “NetWare Send Message” window (see Figure 3-7) to send a message to a user or group of users on the network. Select the resource you want to send a message to from the “Resources” list, type your message in the “Message” field, and then choose the “Send” button at the bottom of the window.
Understanding Client Tools Using NetWare User Tools for MS Windows Using the “NetWare Send Message” Window When using this window, remember that you must first log in to a Directory Services tree or server that contains the object that you want to send a message to. Viewing the “Resources” List This list within the “NetWare Send Message” window contains users and groups. Use the show or hide features (the buttons at the bottom of the window) to control the displayed resources in the “Resources” list.
Understanding Client Tools Using NetWare User Tools for MS Windows Windows. These settings are retained in your NETWARE.INI, WIN.INI, and SYSTEM.INI files. • NetWare User Tools for MS Windows recognizes the previous settings each time you start MS Windows.
Understanding Client Tools Using NetWare User Tools for MS Windows Table 3-3 “NetWare Settings” Options Option Explanation Print Manager Display Allows you to configure the look and content of your MS Windows Print Manager display. The following option settings are available: “Maximum Jobs” allows you to set the number of print jobs that can be stored in the Print Manager queue.
Understanding Client Tools Using NetWare User Tools for MS Windows Table 3-3 “NetWare Settings” Options Option Explanation 386 Enhanced DOS Sessions “Global Drives and Paths” enables MS Windows to support global drive mappings and paths across multiple DOS box sessions. To enable global drive mapping support, add the following heading and command in the MS Windows SYSTEM.INI file: [NETWARE] NWSharehandles=true Resource Display • “Bindery” displays available bindery servers in the “Resources” list.
Understanding Client Tools Using NetWare User Tools for MS Windows 2 Type the path and program filename in the “Command Line” field. For example, to define the MS Windows File Manager to load from NetWare User Tools, you would type C:\windows\winfile.exe 3 Choose “OK.” An icon for the particular application appears in the button bar. Changing the User-Defined Path Once a path is set, you need to use the quick key to access the “User Defined Path” dialog. (Press +<1> or +<2>.
Understanding Client Tools Using NetWare User Tools for MS Windows Using the “File and Directories Property” window When using the “Properties” option, remember that you can set properties for network files and directories only. Properties for directories and files on local drives are set within the MS Windows File Manager. The following table lists the attributes that you can assign.
Understanding Client Tools Using NetWare User Tools for MS Windows Table 3-5 Optimizing the NetWare Client Software for MS Windows Condition Specifying to display parent dots in list boxes for file and directory navigation Explanation The NetWare server doesn’t have directory entries for “.” and “..” as DOS does. To see “.” and “..” in directory listings, set the value for this parameter to “on.” For example: SHOW DOTS=ON This parameter is supported only by NetWare 2.11 and later.
Understanding Client Tools Exiting NetWare User Tools for MS Windows Exiting NetWare User Tools for MS Windows To exit the NetWare User Tools for MS Windows, do one of the following: • Choose the “Exit” button from the menu bar. • Press + or +. • Choose the “System Menu” box (the box in the upper-left corner of NetWare User Tools for MS Windows). Choose “Close” from the menu that appears.
Understanding Client Tools Additional Information Additional Information For NetWare 2 and NetWare 3 Topic Reference NetWare bindery “Bindery” in NetWare 3.12 Concepts NetWare drives “Network Drive Mapping” in NetWare 3.12 Concepts NetWare file system (directory structure) “Directory Structure” in NetWare 3.12 Concepts NetWare volumes “Volume” in NetWare 3.12 Concepts Network printing “Printing” in NetWare 3.12 Concepts Print queues “Print queue” in NetWare 3.
Understanding Client Tools Additional Information Topic Reference Network printing “Printing” in NetWare 4 Concepts Print queues “Print queue” in NetWare 4 Concepts Print servers “Print server” in NetWare 4 Concepts Printers “Printer” in NetWare 4 Concepts 3-29
Understanding Client Tools Additional Information 3-30
4 Preparing to Install or Upgrade the NetWare Client Software 4-1
Preparing to Install or Upgrade the NetWare Client Software Overview Overview This chapter explains the task you need to complete before running the NetWare® Client™ installation program or manually installing the NetWare Client software. Topic Preparing Client Workstations Preparing the NetWare Client Installation Software Setting Up for Installation from a Network Directory Editing the INSTALL.
Preparing to Install or Upgrade the NetWare Client Software Introduction Introduction Proper preparation is important to the ease and success of your installation or upgrade. Preparation ensures that your hardware and software are configured properly and that you have the necessary information to successfully complete all of your client workstation installations or upgrades.
Preparing to Install or Upgrade the NetWare Client Software Preparing Client Workstations Preparing Client Workstations Preparing client workstations for installing or upgrading the NetWare Client software requires hardware and software setup on each client workstation that you want to use on the network.
Preparing to Install or Upgrade the NetWare Client Software Preparing Client Workstations settings. • • • For information on installing the network board, see the manufacturer’s documentation. Network cabling • Each type of network board requires unique cabling. See the manufacturer’s documentation packaged with your network board for requirements. • Token ring network boards require a cable connection to the MAU before installing the NetWare Client software.
Preparing to Install or Upgrade the NetWare Client Software Preparing Client Workstations If you have NOTE: Then EISA or MCA network boards Run the workstation’s setup or reference program. This program lists the values for your network board settings. ISA network boards Look at the network board itself to obtain the specific settings. The documentation provided with your network board will direct you where to find each setting value.
Preparing to Install or Upgrade the NetWare Client Software Preparing Client Workstations IRQ NOTE: Device IRQ Device 0 Timer output 0 8 Real time clock 1 Keyboard 9 Available 2 EGA/VGA 10 Available 3 COM2 11 Available 4 COM1 12 Available 5 LPT2 13 Co-processor 6 Diskette 14 Hard disk 7 LPT1 15 Available If you specify an interrupt for the network board that is already being used by another device, you can still install the network board but the network software will no
Preparing to Install or Upgrade the NetWare Client Software Preparing Client Workstations I/O Port Device I/O Port Device 1F0 AT disk controller 300 Available 200 Game controller/ joystick (200-20F) 320 XT hard disk interface 220 Novell network keycard 340 Available 240 Available 360 LPT1 (378-37F) 260 LPT2 (278-27F) 380 SLDC/Sec Bi-Sync interface (380-38C) 280 LCD display on WYSE* 2108 PC 3A0 Primary Bi-Sync interface (3A0-3A9); Monochrome display (3B0-3BB) 2A0 Available 3C0
Preparing to Install or Upgrade the NetWare Client Software Preparing Client Workstations The base memory address often available for the network board is D800 (sometimes written as D8000). NOTE: If you use a memory manager (for example, EMM386 or QEMM*), you might need to exclude this base memory address if the memory manager cannot detect automatically that the memory address is used by the network board.
Preparing to Install or Upgrade the NetWare Client Software Preparing Client Workstations If you are upgrading your client software from a previous version of the NetWare Client software, your current workstation hardware and software configuration should be sufficient. In this case, go to “Preparing the NetWare Client Installation Software” to continue preparing for installation. The following checklist can help you determine what preparations you need to make for installing the NetWare Client software.
Preparing to Install or Upgrade the NetWare Client Software Preparing the NetWare Client Installation Software Preparing the NetWare Client Installation Software Preparing the NetWare Client installation software depends greatly on the current state and condition of your client workstations and NetWare Client software packaging.
Preparing to Install or Upgrade the NetWare Client Software Setting Up for Installation from a Network Directory Setting Up for Installation from a Network Directory Setting up a NetWare server for running the installation program from a network directory requires setup on an existing NetWare server and each client workstation you want to use on the network. This section applies only to client workstations that already have a previous version of the NetWare Client software installed.
Preparing to Install or Upgrade the NetWare Client Software Setting Up for Installation from a Network Directory The volume and directory are SYS:PUBLIC\CLIENT\DOSWIN for DOS and MS Windows. The following procedure shows you how to map a drive to the appropriate volume and directory. Procedure 1 Map the next network drive to SYS:PUBLIC by typing MAP N SYS:PUBLIC NOTE: This mapping might already be set up as a search drive in a login script for your client workstation.
Preparing to Install or Upgrade the NetWare Client Software Editing the INSTALL.CFG File Editing the INSTALL.CFG File You can customize the installation program software for DOS and MS Windows to suit your particular networking environment. You should edit the [REQUESTER] section of the INSTALL.CFG file before installing the NetWare Client software on multiple client workstations with similar NET.CFG files. The NET.
Preparing to Install or Upgrade the NetWare Client Software Editing the INSTALL.CFG File Change in First Network Drive In previous versions of the NetWare Client™ software, the first network drive was always the first drive letter not reserved for local use. This setting was made with the DOS LASTDRIVE parameter in the CONFIG.SYS file. Because the NetWare DOS Requester™ software is a redirector on the back end of DOS, it requires that the LASTDRIVE=Z parameter be added to the CONFIG.SYS file.
Preparing to Install or Upgrade the NetWare Client Software Editing the INSTALL.CFG File For example, to specify the machine type for an IBM, you would place the following lines in your INSTALL.CFG file: [REQUESTER] short machine type=ibm NOTE: The maximum characters allowed in the name is four. See your hardware manufacturer for information about the short name for your hardware.
Preparing to Install or Upgrade the NetWare Client Software Using a Third-Party ODI LAN Driver Using a Third-Party ODI LAN Driver The NetWare Client installation software includes drivers for most network boards. If an Open Data-Link Interface™ (ODI) LAN driver is not included for your network board, check the network board packaging for a diskette with a copy of the correct driver. Or contact the network board manufacturer to obtain a driver compatible with NetWare.
Preparing to Install or Upgrade the NetWare Client Software Upgrading Your IPX Driver to ODI Upgrading Your IPX Driver to ODI If your client workstations are using a dedicated IPX™ driver, you should upgrade to an Open Data-Link Interface (ODI) specification version. An ODI version of IPX gives your client workstations greater functionality by supporting multiple communication protocols. You can upgrade in two ways: • Use the client installation program to upgrade during installation.
Preparing to Install or Upgrade the NetWare Client Software Where to Go from Here Where to Go from Here After your hardware and software are prepared, you are ready to begin installation. See Chapter 5, “Installing or Upgrading NetWare Client Software,” to continue.
Preparing to Install or Upgrade the NetWare Client Software Where to Go from Here 4-20
5 Installing or Upgrading NetWare Client Software 5-1
Installing or Upgrading NetWare Client Software Overview Overview This chapter explains the procedures for installing or upgrading the NetWare® Client™ software and gives a brief summary of what happens during installation.
Installing or Upgrading NetWare Client Software Introduction Introduction The NetWare Client installation program copies the NetWare DOS Requester™ and other NetWare Client software for DOS and Microsoft (MS) Windows to specified directories on each client workstation. It also provides procedures for editing configuration files for your operating environment to run on NetWare.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program Running the NetWare Client Installation Program DOS and MS Windows client workstations share the same installation program. To provide for this, the installation program runs within the DOS environment. Prerequisites Review the following checklist to make sure you are prepared to install NetWare Client software. • Close MS Windows before loading the installation program.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program For more detailed information, continue with this section, which explains the following installation tasks: NOTE: • Selecting a Destination Directory for the NetWare Client Files • Updating System Files on Your Workstation • Installing Support for MS Windows • Installing LAN Drivers • Copying Files Take advantage of the useful hints about the installation program that are provided at the bottom of th
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program Figure 5-1 Installation Program Opening Screen Selecting a Destination Directory for the NetWare Client Files The installation program searches for the path to any existing copy of the VLM.EXE file. If the VLM.EXE file does not exist, the installation program automatically assigns the default path C:\NWCLIENT.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program 1 Select the directory path field in Step 1 on the installation program opening screen and press . A blinking cursor appears at the end of the path statement in the field. 2 Edit the field for your specific target directory and press . The installation program automatically jumps to Step 2 on the screen (which is explained in the procedure).
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program For example, if your NetWare Client directory is NWCLIENT, the modification appears as follows: @CALL C:\NWCLIENT\STARTNET.BAT PATH=C:\NWCLIENT;%PATH% Changes Made to Your CONFIG.SYS File Two line are added to your client workstation’s CONFIG.SYS file to set the LASTDRIVE and FILES setting.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program See “Modifying MS Windows Configuration Files on a Network Directory” for more information. • MS Windows for Workgroups See “Installing for MS Windows for Workgroups” for more information. The NetWare Client software for MS Windows is not compatible with the client software for NetWare provided by Microsoft.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program Figure 5-2 “Customize Support for MS Windows” Screen The installation program jumps to the customize option for MS Windows. Press if you want to install multiple country codes for determining the date, time, and locale of client workstations other than the locale you currently have loaded.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program The installation program jumps to the “Enter MS Windows directory” field. Skip this option and continue unless you also want to update a personal network copy of MS Windows. 3 Select the “Highlight here and press to customize” option and press . 4 Select the “For the Network Administrator only: Do you want to set the shared MS Windows path? (Y/N)” field on the screen and press .
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program network.drv=*shared_MS_Windows_directory\netxdrv\ netware.drv For example: network.drv=*f:apps\winsys\netxdrv\netware.drv Ensure that the necessary changes to the MS Windows .INI files were made (See “MS Windows Configuration Files Are Modified” for more information). For details on where the SYSTEM directory and .
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program In NetWare 2 and NetWare 3™ software, Ethernet drivers default to the old Ethernet 802.3 frame type. In NetWare 4 and NetWare Client Kits for DOS and MS Windows, they default to the new Ethernet 802.2 frame type. Some routers on your network might not support the new Ethernet 802.2 frame type. Your client workstation cannot connect to a network expecting the old Ethernet 802.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program These procedures correspond with Step 5 on the installation program opening screen. Network Board Type Supported by NetWare and displayed in the list Procedure 1 (ODI LAN drivers only. Use an existing LAN driver for network boards with dedicated IPX™ drivers only. Select the “Other drivers” option in the “Network Board” menu and direct the installation program to the path where the driver is located.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program If you are unsure of your client workstation’s network board settings, refer to your records or accept the default settings. If your LAN driver does not load at startup, ensure that the parameter settings for the Link Driver section of the NET.CFG file match the network board hardware settings.
Installing or Upgrading NetWare Client Software Running the NetWare Client Installation Program You will be required to make these changes manually after the installation. (See “Creating or Modifying Configuration Files” for more information.) If a read-only .NEW file by that name already exists and you do not chose the allow the installation program to write over it, the installation program does not save the changes to a file.
Installing or Upgrading NetWare Client Software What Happens during Installation What Happens during Installation The following events happen when you install the NetWare Client software. A Directory Is Created A directory is created for the DOS client files according to the target directory specified during installation. If you are installing for Microsoft (MS) Windows, the MS Windows client files are copied to the specified MS Windows directory.
Installing or Upgrading NetWare Client Software What Happens during Installation DOS and NetWare Configuration Files Are Created or Modified CONFIG.SYS and AUTOEXEC.BAT If you allowed the installation program to modify your system configuration files, then the previous version of your client workstation’s CONFIG.SYS and AUTOEXEC.BAT files are automatically saved as CONFIG.BNW and AUTOEXEC.BNW. If these specific .BNW files already exist, then they are overwritten. If no previous versions of the AUTOEXEC.
Installing or Upgrading NetWare Client Software What Happens during Installation NET.CFG The installation program reads the existing NET.CFG file or creates a new one if one does not exist in order to set a configuration for the network board installed in your client workstation. Your old NET.CFG file is saved as NET.BNW. The following is an example of a NET.CFG file for a Novell® NE2000™ Ethernet board: LINK DRIVER NE2000 PORT 300 INT 3 FRAME ETHERNET_802.
Installing or Upgrading NetWare Client Software What Happens during Installation NOTE: The user interface for the NETWARE.DRV file is the NWUSER.EXE file. [boot.description] • The line network.drv= is replaced by network.drv=NetWare (vx.x). • If you are installing for Windows for Workgroups (WFWG), the following modification is made: The line secondnet.drv= is replaced by secondnet.drv=Novell NetWare (workstation shell 4.0 and above).
Installing or Upgrading NetWare Client Software What Happens during Installation This setting requires that UniqueDOSPSP=ON. • The line ReflectDOSInt2A= is replaced by ReflectDOSInt2A=True. This specifies that MS Windows will pass on INT 2A signals to the NetWare Client software. • The line UniqueDOSPSP= is replaced by UniqueDOSPSP=True. This specifies MS Windows should start every application at a new memory address. WIN.
Installing or Upgrading NetWare Client Software Installing for MS Windows for Workgroups Installing for MS Windows for Workgroups If you are running the NetWare Client software on client workstations running MS Windows for Workgroups (WFWG), you should complete this additional setup before loading the NetWare Client software. The additional setup required for MS Windows for Workgroups is notifying the WFWG software of the LAN driver type you want to use. You can use ODI LAN drivers provided in this kit.
Installing or Upgrading NetWare Client Software Installing for MS Windows for Workgroups “Networking functionality will not be available. Your network adapter or protocols may not be configured properly. Run Network Setup to check adapter and protocol settings.” 2 To continue, choose “OK.” 3 In the “Network” group, choose the “Network Setup” icon. 4 From the “Network Setup” dialog box, choose “Drivers.” The “Network Drivers” dialog box appears.
Installing or Upgrading NetWare Client Software Installing for MS Windows for Workgroups To modify any client workstations files, continue with the next section. To load the client software, reboot your client workstation and then go to “Loading the NetWare Client Software.
Installing or Upgrading NetWare Client Software Setting Up an MS Windows Shared Network Directory for NETX and VLM Client Workstations Setting Up an MS Windows Shared Network Directory for NETX and VLM Client Workstations To set up a network copy of MS Windows to support individual users that operate multiple client workstations running the current NetWare DOS Requester (VLM) or the NetWare Shell (NETX) software, you need to complete the following procedures.
Installing or Upgrading NetWare Client Software Setting Up an MS Windows Shared Network Directory for NETX and VLM Client Workstations 5 Create a NetWare group called “NETXUSERS.” 6 Add each user that uses a client workstation running the NetWare Shell (NETX) software to the “NETXUSER” group. 7 Modify the system login script or container login script to include the following IF…THEN statement: IF MEMBER OF "NETXUSER" AND %LOGIN_NAME <> SUPERVISOR THEN #C:\COMMAND /C SYS_SET.
Installing or Upgrading NetWare Client Software Setting Up an MS Windows Shared Network Directory for NETX and VLM Client Workstations 2 Add the following environment variable to the STARTNET.BAT file on each client workstation running the NetWare Shell software: SET NETDRV=NETX 3 Create two versions of the SYSTEM.INI file, one for each type of client software, and save them in each user’s individual home directory. The SYS_SET.
Installing or Upgrading NetWare Client Software Loading the NetWare Client Software Loading the NetWare Client Software Loading the NetWare Client software for DOS and MS Windows client workstations requires you to complete the following procedure. Procedure 1 Ensure that a copy of DOS or MS Windows is set up on each client workstation. See “Setting Up Workstation Software.” 2 Ensure that the NetWare Client software files are installed on each client workstation that you want to run DOS or MS Windows.
Installing or Upgrading NetWare Client Software Using Two Network Boards Using Two Network Boards In most cases the ODI (or compatible) LAN drivers provided with the NetWare Client software can share a network board with other communication packages so you do not need to purchase two network boards.
Installing or Upgrading NetWare Client Software Using Two Network Boards If you use a separate network board for each communication package that you use then here are no additional steps to set up the second network board under NetWare. This is because the network board is controlled by the other communications package. It might need to be configured under the other communication package.
Installing or Upgrading NetWare Client Software Using Two Network Boards NOTE: Include the line for MS Windows directory only if you are running MS Windows for Workgroup. Replace preferred_language with one of the following languages: ENGLISH DEUTSCH ESPANOL FRANCAIS ITALIANO Replace client directory with the directory where the NetWare Client files are found. Replace primary_lan_driver with name of the ODI LAN driver that your workstation binds to first.
Installing or Upgrading NetWare Client Software Using Two Network Boards link driver ntr2000 int 5 port a20 mem cc000 frame token-ring frame token-ring_snap Two Identical Drivers If you have two network boards using the same type of ODI LAN driver, do not load the same driver twice in the NET.CFG file and do not specify a “Protocol Stack” option. Instead, use the Link Driver option in NET.CFG to specify that the same driver is used twice. Do this by placing two Link Driver sections in the NET.
Installing or Upgrading NetWare Client Software Using Two Network Boards With two network boards of the same type, the network board which is listed first in the NET.CFG file is the one that IPX uses as primary. Also, if you do not specify two Link Driver sections, a driver will not be loaded for the second network board, and that board will be ignored. See “Link Driver Option” in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for information.
Installing or Upgrading NetWare Client Software Using Two Network Boards frame ethernet_802.3 link driver ne3200 slot 2 frame ethernet_802.2 frame ethernet_802.
Installing or Upgrading NetWare Client Software Where to Go from Here Where to Go from Here After installation of your NetWare Client software is completed, you can log in to the network. You can also begin setting up your client workstation for additional networking support.
Installing or Upgrading NetWare Client Software Where to Go from Here 5-36
6 Setting Up NetWare Client Workstations to Log In 6-1
Setting Up NetWare Client Workstations to Log In Overview Overview This chapter explains how to modify your NET.CFG file to simplify logging in to a NetWare® network. Topic Modifying the NET.CFG File for Logging In to NetWare 2 and NetWare 3 Modifying the NET.
Setting Up NetWare Client Workstations to Log In Introduction Introduction Proper client workstation setup can make logging in to the network virtually transparent.
Setting Up NetWare Client Workstations to Log In Modifying the NET.CFG File for Logging In to NetWare 2 and NetWare 3 Modifying the NET.CFG File for Logging In to NetWare 2 and NetWare 3 When logging in to a NetWare 2 or NetWare 3™ network, you attach to an individual server. Then you make additional attachments to other servers that you have a user account on. Using the Preferred Server Parameter Use the Preferred Server parameter in the NET.
Setting Up NetWare Client Workstations to Log In Modifying the NET.CFG File for Logging In to NetWare 4 Modifying the NET.CFG File for Logging In to NetWare 4 When logging in to NetWare 4™, you don’t attach to individual servers as with previous versions of NetWare, but you log in to the entire network. With your Distinguished Name (DN), you can simplify the login process by adding information to your client workstation’s NET.CFG file.
Setting Up NetWare Client Workstations to Log In Modifying the NET.CFG File for Logging In to NetWare 4 Bindery services is set by default for every NetWare Server object that is installed. Therefore, users log in directly to a server rather than to the Directory tree. Using the Preferred Tree Parameter By using the Preferred Tree parameter in the NET.CFG file, you direct the NetWare DOS Requester to the Directory tree where your name context is set.
Setting Up NetWare Client Workstations to Log In Modifying the NET.CFG File for Logging In to NetWare 4 For example, type name context=”esayers.sales.hp_us” 3 (Conditional) If your network has multiple Directory trees, type preferred tree=preferred_tree_name For example, type preferred tree=hp_us Example of the NetWare DOS Requester Section NetWare DOS Requester name context “Esayers.sales.
Setting Up NetWare Client Workstations to Log In Understanding Logging In to NetWare Directory Services Understanding Logging In to NetWare Directory Services NetWare Directory Services™ architecture makes logging in to the network convenient. User information resides in a global database. Each user is assigned a position, or context, within the global database that informs the network where the user’s User object is located in relationship to the entire network. NOTE: In the NET.
Setting Up NetWare Client Workstations to Log In Understanding Logging In to NetWare Directory Services Specifying the Name Type of an Object A name type distinguishes the class of object that you are referring to, such as a User object or an Organizational Unit object. For example, you could express ESAYERS.SALES.HP_US as CN=ESAYERS.OU=SALES.O=HP_ US where CN is the common name of the User object, OU is the Organizational Unit name, and O is the Organization name.
Setting Up NetWare Client Workstations to Log In Understanding Logging In to NetWare Directory Services Once you are logged in, use the following utilities to change the context of your User object within the Directory tree: • The CX utility at the DOS command line • The “Change Context” option in the NETUSER utility for DOS • The “Drive Connections” window in NetWare User Tools for MS Windows Logging In to Your Context 1 Type LOGIN context Replace context with your Distinguished Name.
Setting Up NetWare Client Workstations to Log In Additional Information Additional Information For more details, see Chapter 1, “Understanding NetWare Directory Services,” in Introduction to NetWare Directory Services.
Setting Up NetWare Client Workstations to Log In Additional Information 6-12
7 Logging In from a NetWare Client Workstation 7-1
Logging In from a NetWare Client Workstation Overview Overview This chapter explains how to log in to a NetWare® server or network from a NetWare client workstation in the following ways.
Logging In from a NetWare Client Workstation Introduction Introduction Logging in to a NetWare server or network is the procedure that provides your client workstation access to network resources such as network directories, printers, and applications. When you initiate a login request, the NetWare operating system looks for your specific security rights and then prompts you to enter a password.
Logging In from a NetWare Client Workstation Prerequisites Prerequisites Ensure the following before logging in: • The NetWare Client™ software is loaded • If your client workstation can use an Open Data-Link Interface™ (ODI) network board driver, load the following software: LSL.COM Network board driver (for example, NE2000.COM) IPXODI.COM VLM.EXE • If your client uses only a dedicated IPX™ driver (not an ODI™ driver), load the following programs: IPX.COM VLM.
Logging In from a NetWare Client Workstation Logging In from the DOS Prompt Logging In from the DOS Prompt The login program connects your client workstation to a server or the network. The NetWare Client software automatically maps the first network drive of your client workstation.
Logging In from a NetWare Client Workstation Logging In from the DOS Prompt LOGIN TSMKT\ESAYERS 3 Enter your password (if required). Logging In to a NetWare 4 Network 1 Change to the first network drive by typing F: The NetWare DOS Requester software automatically maps the first network drive for your client workstation. The default drive is F:. To change the default, edit the FIRST NETWORK DRIVE parameter in your NET.CFG file.
Logging In from a NetWare Client Workstation Logging In from the DOS Prompt LOGIN TSMKT/ESAYERS /B 2 Enter your password (if required).
Logging In from a NetWare Client Workstation Logging In from MS Windows Logging In from MS Windows You can use the NetWare User Tools in MS Windows to log in to NetWare 2, NetWare 3, and NetWare 4 by completing these steps. The “Login” option under NetWare User Tools for MS Windows authenticates you to NetWare Directory Services™ in NetWare 4 or to a NetWare server in NetWare 2 and NetWare 3 networks. It does not run a login script for your client workstation.
Logging In from a NetWare Client Workstation Logging Out of a NetWare Server or Network Logging Out of a NetWare Server or Network Logging out of a NetWare server or network is the procedure that breaks the network connections and deletes drive mappings and printer port captures that were made to the network. If you log out without specifying a NetWare server name in the LOGOUT command, the client workstation’s resource connections to all servers or to the network are terminated.
Logging In from a NetWare Client Workstation Logging Out of a NetWare Server or Network 2 From the menu bar, choose the “NetWare Connections” icon. The “NetWare Connections” window displays available resources. 3 Choose the resource that you want to log out from. 4 Choose “Logout.
Logging In from a NetWare Client Workstation Where to Go from Here Where to Go from Here After logging in, you can begin setting up your client workstation for additional networking support: If you want to See Modify your NET.CFG file to simplify login Chapter 6, “Setting Up NetWare Client Workstations to Log In” Set up and modify your NET.CFG file Chapter 2, “NET.
Logging In from a NetWare Client Workstation Where to Go from Here 7-12
8 Setting Up and Managing Network Drives 8-1
Setting Up and Managing Network Drives Overview Overview This chapter explains how to set up and manage network drives on your NetWare® client workstations. Topic Using NetWare Utilities to Set Up and Manage Drive Mappings The MAP Utility The NetWare User Tools for DOS (the NETUSER Utility) The NetWare User Tools for MS Windows (the NWUSER.
Setting Up and Managing Network Drives Introduction Introduction NetWare allows you to set up and manage network drives on each client workstation. This gives client workstations the ability to store and access files and applications in a central file system. This ability is provided through drive mappings which specify particular locations within volumes and directories on the network.
Setting Up and Managing Network Drives Introduction the last local drive letter. To maintain compatibility with existing batch files, you might want to add, for example, the FIRST NETWORK DRIVE = H parameter setting under the NetWare DOS Requester heading in the NET.CFG file. Otherwise, batch files assuming drive H: as the first drive must be altered. • Search drives Point to specific volumes or directories on a network and add the network volumes or directories to the DOS path.
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings Using NetWare Utilities to Set Up and Manage Drive Mappings NetWare provides you with the following three utilities to set up and manage network drives and search drives for each client workstation in your network: • The MAP Utility A DOS text utility available in all version of NetWare. • The NetWare User Tools for DOS (the NETUSER Utility) A DOS menu utility available only in NetWare 4 software.
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings The MAP Utility MAP allows you to assign drives to network directories. Use MAP to • View drive mappings • Create or change network or search drive mappings • Assign a drive to a fake root directory (for applications that must use a root directory) MAP is a NetWare workstation utility located in the SYS:PUBLIC directory.
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings Assigning Drive Mappings for Diverse Environments Instead of specifying drive letters such as H or G, it can be useful to use an asterisk followed by a number n to represent the nth network drive. For example, if your first network drive is F: and you use “MAP *3:=”, then that drive is assigned as H: (because MAP *1:=F:, MAP*2:=G:, MAP*3:=H:, etc.).
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings To ensure that you can access NetWare utilities, DOS directories, and applications, you should map search drives to the following directories in the order given: • Map the first search drive (S1:) to the SYS:PUBLIC directory, which contains the NetWare utilities for DOS and MS Windows client workstations. • Map the second search drive (S2:) to the DOS directory if you access DOS from the network.
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings Instead, you would type MAP S2:=APPL NOTE: It is best to use Map objects in your current context. Don’t use Distinguished Names that point to other contexts. If your map is in another context, you should create an alias that points to the real Directory Map object. See “Alias object” in Concepts for more information.
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings Version NetWare 4 Reference Chapter 3, “Creating Login Scripts,” in Supervising the Network The NetWare User Tools for DOS (the NETUSER Utility) NETUSER allows you to assign drives to network directories.
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings 6 Exit NETUSER. Press until the “Exit?” menu box appears. Then select “Yes” and press . Or press + anywhere within NETUSER to display the “Exit?” menu box. Then select “Yes” and press . The NetWare User Tools for MS Windows (the NWUSER.
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings 4 From the “Resources” list, select the resource you want to connect to, and then choose a client workstation drive. 5 Choose “Map” at the bottom of the window. If you are using keyboard entry, first type in the full path for the drive mapping inside the “Path” field, and then choose “Map.
Setting Up and Managing Network Drives Using NetWare Utilities to Set Up and Manage Drive Mappings However, when you are using a DOS Box inside MS Windows, your previous search drives are disabled. Viewing the “Resources” List The “Resources” list contains the following: • Volumes • Directories • NetWare Directory Services™ objects • NetWare Directory Services containers The volumes and directories are listed in a hierarchical structure.
Setting Up and Managing Network Drives Using Universal Naming Convention (UNC) Paths in MS Windows Using Universal Naming Convention (UNC) Paths in MS Windows NetWare supports the use of Universal Naming Convention (UNC) redirection for path statements in dialog boxes within the following MS Windows conventions: Program Group (.
Setting Up and Managing Network Drives Using Universal Naming Convention (UNC) Paths in MS Windows \\ACCOUNTING\SYS\APPS\DATABASE.GRP If you are redirecting a resource that is a NetWare Directory Services object in NetWare 4, you must specify three backslashes (\\\) before the servername. Program Items Files To have access to program items located on a network server without formally mapping to the resource, use UNC redirection in the “Program Item Properties” dialog boxes as follows.
Setting Up and Managing Network Drives Using Universal Naming Convention (UNC) Paths in MS Windows UNC redirection can work even if the executable file relies on another file to run. For example, if the MS-DOS 5.0 EDIT.COM and QBASIC.EXE files (the latter is needed to run the former) are both copied onto the network share, UNC redirection works properly.
Setting Up and Managing Network Drives Using Universal Naming Convention (UNC) Paths in MS Windows Referencing Files and Directories in the “File” or “Move” Text Box 1 Run File Manager. 2 Select the file you want to copy or move. 3 From the “File” menu, choose “Move” or “Copy.” 4 In the “To” text box, enter the UNC path.
Setting Up and Managing Network Drives Additional Information Additional Information Topic Reference NetWare drives “Drive mapping” in NetWare 4 Concepts NetWare file system (directory structure) “Directory structure” in NetWare 4 Concepts NetWare volumes “Volume” in NetWare 4 Concepts 8-18
9 Setting Up Client Workstation Printing 9-1
Setting Up Client Workstation Printing Overview Overview This chapter explains how to set up network printing on your NetWare® client workstation. Topic Using NetWare Utilities to Set Up Network Printing The CAPTURE Utility The NetWare User Tools for DOS (the NETUSER Utility) The NetWare User Tools for MS Windows (the NWUSER.
Setting Up Client Workstation Printing Introduction Introduction NetWare uses a print queue, a print server, and often a print driver to allow several network client workstations to print to a network printer. The print server takes print jobs from the print queue and sends them to the printer.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing Using NetWare Utilities to Set Up Network Printing NetWare provides you with the following three utilities to set up printing for client workstations in your network: • The CAPTURE Utility A DOS text utility available in all version of NetWare. • The NetWare User Tools for DOS (the NETUSER Utility) A DOS menu utility available in NetWare 4™ only. • The NetWare User Tools for MS Windows (the NWUSER.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing The CAPTURE Utility Use CAPTURE to • Set up connection to print queues • Control network printing • View information about network printing • Redirect a printer port to the network Using CAPTURE at the Command Line Use CAPTURE at the command line to set up printing by completing the following procedure.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing This command indicates the following: • Capture to print queue LaserJet4 • The server connection is to Sales • Capture to network printer P1 • Timeout in 5 seconds Using CAPTURE Login Scripts or Profiles You can use login scripts or profiles to automatically set up port captures when you log in to the network.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing 2 Add the following lines to the file: NetWare DOS Requester network printers = number Replace number with the number of printer connections. Maximum = 9 Default = 3 For example, to allow for the maximum number of printer connections, you would type NetWare DOS Requester network printers = 9 3 Save your changes and exit the ASCII text editor.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing NETUSER The NETUSER utility menu appears. 3 Choose “Printing.” The “Available Ports” window appears. 4 Choose a port from the list. The “Available Options” window appears. 5 Choose “Change Printers.” The “Printer/Print Queues” window appears. NOTE: If the print queue you want to capture is not listed, make sure that you chose the correct server containing this print queue.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing The NETWARE.DRV file provides the port capturing function for the NetWare User Tools for MS Windows. It resides in the SYSTEM directory of your MS Windows directory (The default is C:\WINDOWS\SYSTEM). NOTE: The NetWare User Tools program is available in NetWare 3.12 and NetWare 4 software, and in NetWare Client Kits for DOS and MS Windows packages.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing If the printer you want is not listed: • Choose “Add” to display the list of available printers. • Select the printer you want from the “List of Printers.” • Choose “Install.” MS Windows prompts you to insert an MS Windows diskette and then copies the print driver for the selected printer to the MS Windows directory. 4 Assign printing ports to network print queues.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing Figure 9-3 “NetWare Printer Connections” Window d Choose the same port from the “Ports” list that you selected in Step 4b. e Choose a print queue name from the “Resources” list. If you don’t know the queue name, use the browser to see available print queues. f Choose “Capture.” g Exit the “NetWare Printer Connections” window by choosing the “Exit” button (the left-most button of the upper menu bar).
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing 6 Choose the “Print Manager” icon. 7 From the “Print Manager” window, select “Options.” 8 From the “Options” menu, choose “Network Settings.” The “Network Options” dialog appears. Direct print jobs to a network print queue. Figure 9-4 “Network Options” Dialog 9 Mark the “Print Net Jobs Direct” checkbox.
Setting Up Client Workstation Printing Using NetWare Utilities to Set Up Network Printing 2 Add the following lines to the file: NetWare DOS Requester network printers = number Replace number with the number of printer connections. Maximum = 9 Default = 3 For example, to allow for the maximum number of printer connections, you would type NetWare DOS Requester network printers = 9 3 Save the changes and then close the NET.CFG file. 4 Open the MS Windows WIN.INI file in an ASCII text editor.
Setting Up Client Workstation Printing Using Universal Naming Convention (UNC) Port Redirection in MS Windows Using Universal Naming Convention (UNC) Port Redirection in MS Windows NetWare supports the use of Universal Naming Convention (UNC) redirection for entries in the [ports] section of the WIN.INI file. UNC port redirection provides you with the ability to use a network print resource without formally capturing a port to it.
Setting Up Client Workstation Printing Using Universal Naming Convention (UNC) Port Redirection in MS Windows lpt1:= lpt2:= \\servername\queuename= For example, to set up a UNC port redirection for the print queue LASERJET4 on server MARKETING, you would add the following lines: [ports] lpt1:= lpt2:= \\marketing\laserjet4= If you are redirecting a resource that is a NetWare Directory Services™ object in NetWare 4, you must specify three backslashes (\\\) before the servername.
Setting Up Client Workstation Printing Additional Information Additional Information Topic Reference Setting up printing functionality in the NET.
10 Setting Up Source Routing Support for a Token-Ring Network 10-1
Setting Up Source Routing Support for a Token-Ring Network Overview Overview This chapter explains how to use and install the NetWare® source routing driver for token-ring networks. The following topics are covered in this chapter. Topic Installing Source Routing on the Server Installing the ROUTE.
Setting Up Source Routing Support for a Token-Ring Network Introduction Introduction The NetWare source routing driver (the ROUTE.COM file) enables communication across IBM token-ring network bridges. Any type of DOS ODI™ protocol stack can use this source routing functionality. The following figure shows an example of a network configuration using IBM source routing bridges.
Setting Up Source Routing Support for a Token-Ring Network Introduction File server Client workstation (WS) Client WS WS Client WS Ring 1 Client WS Ring 3 IBM token ring source routing bridges Client WS Client WS Client WS File server Client WS Client WS File server Ring 2 Client WS Client WS Figure 10-1 Network Configuration Using Source Routing Bridges NOTE: The NetWare source routing software can route only IPX packets. NetWare Client support for the source routing driver (the ROUTE.
Setting Up Source Routing Support for a Token-Ring Network Introduction The complete setup for client workstations using the ROUTE.COM file requires you to complete the following tasks: 1 Installing Source Routing on the Server 2 Installing the ROUTE.
Setting Up Source Routing Support for a Token-Ring Network Installing Source Routing on the Server Installing Source Routing on the Server 1 Use the lanscan command to identify the Physical Point of Attachment (PPA) of the interface you wish to enable for Token Ring Source Routing. # lanscan Hardware Station Crd Hardware Net-Interface Path Address In# State NameUnit State 8/20/5/1 0x08000995DEDD 0 UP lan0 UP 8/20/5/8 0x555555555555 1 UP lan1 UP NM MAC ID Type 4 ETHER 5 802.
Setting Up Source Routing Support for a Token-Ring Network Installing Source Routing on the Server lan_2_trsr_on=on Note that this configuration change will not take effect until you restart NetWare/9000.
Setting Up Source Routing Support for a Token-Ring Network Installing the ROUTE.COM and NetWare Client Files Installing the ROUTE.COM and NetWare Client Files Copying the Files to the NetWare Client Directory Automatically ROUTE.COM and the other client files are automatically copied to the NetWare Client™ directory when you run the NetWare Client installation software. See Chapter 5, “Installing or Upgrading NetWare Client Software,” for more information.
Setting Up Source Routing Support for a Token-Ring Network Installing the ROUTE.COM and NetWare Client Files Diskette Name NetWare Client for DOS and MS Windows ODI LAN Drivers or NetWare Client for DOS and MS Windows Disk 1 Directory \DOS Filename lan_driver.CO_ NTR2000.CO_ LANSUP.CO_ To expand a file, type NWUNPACK source_drive:path\filename destination_drive:path\filename For example, to expand the ROUTE.COM file, you could type NWUNPACK A:ROUTE.CO_ C:\NWCLIENT\ROUTE.
Setting Up Source Routing Support for a Token-Ring Network Modifying the DOS System and NetWare Client Configuration Files Modifying the DOS System and NetWare Client Configuration Files Modifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with an ASCII text editor. Modifying the CONFIG.SYS File Modify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS Requester™ software.
Setting Up Source Routing Support for a Token-Ring Network Modifying the DOS System and NetWare Client Configuration Files odi_lan_driver route ipxodi vlm Replace path with the directory where the ROUTE.COM and NET.CFG files are found. The ROUTE.COM file cannot execute unless it can access the NET.CFG file in the proper directory path. Replace odi_lan_driver with the name of the ODI LAN driver that your workstation is using. For example, Novell provides the NTR2000.COM file or the LANSUP.COM file.
Setting Up Source Routing Support for a Token-Ring Network Loading the Source Routing Driver Loading the Source Routing Driver Loading the ROUTE.COM file requires you to complete the following procedure. Procedure 1 Ensure that the ROUTE.COM and NetWare Client software files are installed on each client workstation that you want to connect to a token-ring network. See “Installing the ROUTE.COM and NetWare Client Files” for more information.
Setting Up Source Routing Support for a Token-Ring Network Unloading the Source Routing Driver Unloading the Source Routing Driver 1 Unload all VLM™ files by typing VLM /U 2 Unload ROUTE.COM by typing ROUTE /U NOTE: Always unload the files in reverse order from the order in which you loaded them. Unloading the files in any order other than reverse order in impossible.
Setting Up Source Routing Support for a Token-Ring Network Additional Information Additional Information Topic Understanding more about source routing Reference “Source routing” in Concepts “Understanding Token-Ring Source Routing,” NetWare Application Notes, May 91 (Novell part # 164-000030-005) IBM Token-Ring Network Architecture Reference 10-14
11 Configuring Client Workstations for Desktop SNMP Services 11-1
Configuring Client Workstations for Desktop SNMP Services Overview Overview This chapter explains how to enable desktop SNMP services on your client workstation and how to modify the NET.CFG file to implement additional SNMP options. This section is primarily for network supervisors who administer SNMPbased network management systems. The following topics are covered in this chapter.
Configuring Client Workstations for Desktop SNMP Services Introduction Introduction Simple Network Management Protocol (SNMP) is an industry-standard protocol that specifies a format for collecting network management data. With the Novell® Desktop SNMP services, NetWare client workstations are able to send status information to an SNMP management program running on an IPX™ or TCP/IP network.
Configuring Client Workstations for Desktop SNMP Services Installing an SNMP Management System Console Installing an SNMP Management System Console The Desktop SNMP services provided with the NetWare Client™ for DOS and MS Windows supports the Novell NetWare Management System software (NMS), other industry-standard SNMP management consoles, or other third-party management systems. See the documentation provided with these managements systems for information on installation and setup.
Configuring Client Workstations for Desktop SNMP Services Installing the Desktop SNMP Software Installing the Desktop SNMP Software The Desktop SNMP software includes a collection of files that support the Simple Network Management Protocol (SNMP) using the NetWare Virtual Loadable Module™ (VLM) technology. Support for the Internet Packet Exchange™ (IPX) transport and User Datagram Protocol (UDP) transports is also provided.
Configuring Client Workstations for Desktop SNMP Services Installing the Desktop SNMP Software File Description WSDRVPRN.VLM The print information collection file for gathering information about print mappings and captured printers WSREG.VLM The registration module WSSNMP.VLM The Desktop SNMP module, which includes MIB-II System and SNMP groups support WSTRAP.VLM The trap module These files are automatically copied to the NetWare directory when you run the NetWare Client installation program.
Configuring Client Workstations for Desktop SNMP Services Installing the Desktop SNMP Software Manually If you choose to not run the NetWare Client installation program, you must manually copy the appropriate files to the NetWare Client directory. To manually copy the files from the NetWare Client for DOS and MS Windows diskettes, complete the following procedure.
Configuring Client Workstations for Desktop SNMP Services Modifying DOS System and NetWare Client Configuration Files Modifying DOS System and NetWare Client Configuration Files Modifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with an ASCII text editor. Modifying the CONFIG.SYS File Modify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS Requester™ software.
Configuring Client Workstations for Desktop SNMP Services Modifying DOS System and NetWare Client Configuration Files By default, Desktop SNMP services are not enabled when you install the NetWare Client software. To enable Desktop SNMP services, complete the following procedure. Procedure 1 Modify the C:\NWCLIENT\STARTNET.BAT file to load the Desktop SNMP transport files. Add the following commands in the STARTNET.BAT file after the line that loads the VLM.
Configuring Client Workstations for Desktop SNMP Services Modifying DOS System and NetWare Client Configuration Files If the time zone is not set in your workstation’s environment, traps for SNMP might report an incorrect time. 5 Save and exit. Modifying the NET.CFG File The following modifications to the NET.CFG file are required for each client workstation that you want to load the Desktop SNMP software on. • Add the necessary lines in the NET.CFG file to load and support the Desktop SNMP software.
Configuring Client Workstations for Desktop SNMP Services Modifying DOS System and NetWare Client Configuration Files add the following lines to the NET.CFG file in the order given: netware dos requester use defaults = off vlm = wssnmp.vlm vlm = wstrap.vlm vlm = wsreg.vlm vlm = wsasn1.vlm vlm = mib2if.vlm vlm = wsdrvprn.vlm vlm = mib2prot.
Configuring Client Workstations for Desktop SNMP Services Modifying DOS System and NetWare Client Configuration Files vlm = wsdrvprn.vlm vlm = mib2prot.vlm desktop snmp enable monitor community = any monitor community = “public” enable control community = specific control community = “public” enable trap community = specific trap community = “public” sysname = “Suzanne Morley x893” syslocation = “Building 2” syscontact = “suzanne@acompany.
Configuring Client Workstations for Desktop SNMP Services Modifying DOS System and NetWare Client Configuration Files # List of all printers connected to host [printers] HP LaserJet IIIp on LPT1: NEC P20 on LPT2: # List of all modems connected to host [modems] Hayes Optima 144 on COM1: # List of all tape drives connected to host [tapes] Colorado DJ10 HP 35480A SCSI DAT (4-8 GB) # other devices obtained via DOS APIs 11-13
Configuring Client Workstations for Desktop SNMP Services Loading the Desktop SNMP Software Loading the Desktop SNMP Software Loading the Desktop SNMP software requires you to complete the following procedure. Procedure 1 Ensure that the SNMP management system is set up and running. See “Installing an SNMP Management System Console” for more information. 2 Ensure that the Desktop SNMP software is installed on each client workstation that you want managed from the management console.
Configuring Client Workstations for Desktop SNMP Services Unloading the Desktop SNMP Software Unloading the Desktop SNMP Software 1 (Conditional) If UDP/IP support has been loaded, unload STPUDP by typing STPUDP /U 2 (Conditional) If IPX support has been loaded, unload STPIPX by typing STPIPX /U 3 Unload all VLM files by typing VLM /U The VLM /U command unloads all VLM files, not just the Desktop SNMP files.
Configuring Client Workstations for Desktop SNMP Services Configuring Client Workstations for Better Performance Configuring Client Workstations for Better Performance To improve performance of the Desktop SNMP software, you can configure your client workstation to load one or more Desktop SNMP .VLM files in conventional memory. To load all .VLM files in conventional memory, use the VLM /MC switch when running the VLM manager.
Configuring Client Workstations for Desktop SNMP Services Additional Information Additional Information Topic Reference Setting up and modifying your NET.
Configuring Client Workstations for Desktop SNMP Services Additional Information 11-18
A Using the WSUPDATE Utility A-1
Using the WSUPDATE Utility Overview Overview This appendix contains information about using the WSUPDATE utility for updating client files automatically. The following topics are covered in this appendix.
Using the WSUPDATE Utility Introduction Introduction The WSUPDATE utility allows you to copy updates of client files automatically. Use WSUPDATE to • Copy new revisions of files • Reinstall NetWare Client files • Copy updates of your own files This utility is not recommended for first-time installation of NetWare® Client™ files. WSUPDATE can update only files that exist on the workstation. Use the client installation program for first-time installations.
Using the WSUPDATE Utility Using WSUPDATE to Update Files on Client Workstations Using WSUPDATE to Update Files on Client Workstations The WSUPDATE utility allows you to copy updates of files to client workstations automatically, either at the command line or from a login script or profile.
Using the WSUPDATE Utility Using WSUPDATE to Update Files on Client Workstations Use SYSCON for NetWare 2 and NetWare 3™ workstations. Use the NetWare Administrator graphical utility or the NETADMIN text utility for NetWare 4™ workstations. All three procedures are documented in this section. Using SYSCON This utility is used only with NetWare 2 and 3 networks. For NetWare 4 networks, use the NWADMIN or NetWare Administrator utility to edit a specific container profile.
Using the WSUPDATE Utility Using WSUPDATE to Update Files on Client Workstations #WSUPDATE J: filename For example, if you mapped drive J: as shown in Step 6, add the following command after the drive mapping: #WSUPDATE J: NE2000.COM This command searches all local drives of the client workstations and replaces the NE2000.COM file with its newer version on drive J:. It renames any old NE2000.COM file on the local drives to NE2000.OLD. 8 To exit the system login script, press .
Using the WSUPDATE Utility Using WSUPDATE to Update Files on Client Workstations “User Name” field. 7 Enter a password (if needed). 8 Exit the NetWare User Tools. 9 Load NetWare Administrator by choosing the “NWADMIN” icon from the NetWare group. The “NetWare Administrator” main screen appears. 10 From the browser, select the object whose container profile you want to edit. • To modify the login script for a container, select the “Organizational Unit” icon.
Using the WSUPDATE Utility Using WSUPDATE to Update Files on Client Workstations It renames any old NE2000.COM file on the local drives to NE2000.OLD. 16 Choose “OK” and then save your changes. The “NetWare Administrator” main screen appears. 17 Log in all of the client workstations that you have modified the login scripts for. If the workstations are already logged in, log them in to the network again. This runs the WSUPDATE program and updates the files on all those client workstations.
Using the WSUPDATE Utility Using WSUPDATE to Update Files on Client Workstations 7 Choose “View or Edit Object Properties.” 8 Choose “Login Script.” 9 In the login script, map a drive to the file on the network you want copied to the client workstations. For example, if you want to copy the NE2000.
Using the WSUPDATE Utility Additional Information Additional Information For NetWare 2 and NetWare 3 Topic Reference Creating login scripts “SYSCON” in Utilities Reference Mapping network drives “MAP” in Utilities Reference For NetWare 4 Topic Reference Creating login scripts Chapter 3, “Creating Login Scripts” in Supervising the Network Mapping network drives “MAP” in Utilities Reference Using WSUPDATE “WSUPDATE” in Utilities Reference A-10
B Using the WSUPGRD Utility B-1
Using the WSUPGRD Utility Overview Overview This appendix contains information about using the WSUPGRD utility for upgrading dedicated IPX™ LAN drivers to ODI™ LAN drivers. This utility is available in NetWare® 4™ software only. The following topics are covered in this appendix.
Using the WSUPGRD Utility Introduction Introduction The WSUPGRD utility upgrades the IPX LAN drivers on your client workstation to the corresponding ODI LAN driver. If client workstations in your network are running one of the NetWare Client™ shells (NETx), they are running an IPX LAN driver or a corresponding ODI LAN driver. This utility is recommended for large installations with similar hardware and software configurations.
Using the WSUPGRD Utility Prerequisites Prerequisites A typical upgrade requires the following files in SYS:PUBLIC: • WSUPGRD.EXE • LSL.COM • IPXODI.COM • Appropriate ODI LAN drivers (for example, NE2000.COM) • Auxiliary files • The auxiliary files are optional but can make upgrading a complex network easier. • DRVRXLAT.TXT This file is in SYS:PUBLIC. It contains one line for each ODI LAN driver type in use on the network.
Using the WSUPGRD Utility Using the WSUPGRD /I Option Using the WSUPGRD /I Option The /I option in WSUPGRD lets you print out the hardware identification for your dedicated IPX LAN driver. The DRVRXLAT.TXT file contains a master configuration table. Check the master configuration table to make sure that your dedicated-IPX LAN driver identification matches a registered driver. The table lists the driver name, the company name, and the hardware identification.
Using the WSUPGRD Utility Using WSUPGRDE to Upgrade Network Board Drivers Using WSUPGRDE to Upgrade Network Board Drivers The WSUPGRD utility upgrades the IPX LAN drivers on the client workstations to the corresponding ODI LAN drivers, either at the command line or from a login script.
Using the WSUPGRD Utility Using WSUPGRDE to Upgrade Network Board Drivers Use SYSCON for NetWare 2 and NetWare 3 workstations. Use the NetWare Administrator graphical utility or the NETADMIN text utility for NetWare 4 workstations. All three procedures are documented in this section. If this utility is loaded from a system login script, all of the client workstations that log in to this server must have drivers with the same name.
Using the WSUPGRD Utility Using WSUPGRDE to Upgrade Network Board Drivers WSUPGRD NE2000 /N This command upgrades your IPX LAN driver with an NE2000.COM ODI LAN driver without deleting your IPX LAN driver. 7 To exit the system login script, press . 8 Confirm and save changes you made in the login script. 9 Modify any batch files used to load the NetWare Client software for each client workstation. The batch file should contain at least the following lines: LSL odi_lan_driver.
Using the WSUPGRD Utility Using WSUPGRDE to Upgrade Network Board Drivers The “NetWare User Tools” main screen appears. 3 From the menu bar, choose the “NetWare Connections” icon. The “NetWare Connections” window displays available resources. 4 From the “Resources” list, choose the resource that you want to log in to. 5 Choose “Login.” The “Log In to NetWare” dialog box appears. 6 Enter the name “ADMIN” or a username with ADMIN equivalency into the “User Name” field.
Using the WSUPGRD Utility Using WSUPGRDE to Upgrade Network Board Drivers 15 Choose “OK.” The “NetWare Administrator” main screen appears. 16 Modify any batch files used to load the NetWare Client software for each client workstation. The batch file should contain at least the following lines: LSL network_board_driver.COM IPXODI NETx [if using NetWare 3 or earlier] VLM [if using NetWare 4] 17 Log in all of the client workstations you have modified the login scripts for.
Using the WSUPGRD Utility Using WSUPGRDE to Upgrade Network Board Drivers 5 From the “Options” menu, choose “Manage Objects.” 6 Select the object whose login script you want to edit. • If the object you want appears on the list, select it and press . • If the object is not on the list, browse the Directory tree by selecting objects and pressing until you see the object you want. Select it and press . A login script can be a property of a container, Profile, or User object.
Using the WSUPGRD Utility Additional Information Additional Information Topic Reference Creating login scripts Chapter 3, “Creating Login Scripts” in Supervising the Network Mapping network drives MAP” in Utilities Reference Using WSUPGRD “WSUPGRD” in Utilities Reference B-12
Index Numerics 386 Enhanced DOS Sessions setting option, explained, 3-23 A Accessing files, allowing, 1-17 network from MS Windows, 2-16 network resources with NETUSER, 3-7 network resources with NetWare User Tools for MS Windows, 3-11 online help in MS Windows User Tools, 3-13 online help in NETUSER, 3-7 Address, base memory (explained), 4-8 Applications DOS (see DOS applications) non-NetWare-aware, printing from, 9-3 setting NetWare User Tools for MS Windows user-defined buttons for, 3-23 Windows (see MS
Index 19 D Dedicated IPX LAN driver, upgrading to ODI in login script, B-6 with installation program, 4-18 Delete inhibit file property, explained, 325 Desktop SNMP software configuring, for better performance, 1116 explained, 11-3 installing, 11-4 loading, 11-14 sample NET.CFG file for, 11-11 setting up, 11-3 unloading, 11-15 Desktop SNMP software, modifying files for loading CONFIG.SYS, 11-8 NET.CFG, 11-10 STARTNET.BAT, 11-8 Direct printing option for MS Windows client workstations, explained 3-16.
Index Files modified for NetWare client installation. See also Modifying files AUTOEXEC.BAT, 5-18 CONFIG.SYS, 5-18 NET.CFG, 5-19 PROGMAN.INI, 5-21 STARTNET.BAT, 5-18 SYSTEM.INI, 5-19 WIN.INI, 5-21 Files.
Index search drive mappings in, recommended order of, 8-8 search drive to MS Windows, mapping in, 8-8 WSUPDATE, using from, A-4 WSUPGRD, using from, B-6 Login. See also Logging in authentication and, 1-16 explained, 1-15 from DOS prompt, 7-5 security, explained, 1-18 simplifying, with NET.CFG parameters, 6-5 to NetWare Directory Services (NetWare 4), explained, 6-8 LPT ports. See Printer ports M Managing drive mappings for client workstations.
Index modifying, 6-6 NetWare DOS Requester software architecture, explained, 2-5 backwards compatibility with NETX, 29 DOS Redirection Layer, explained, 2-6 explained, 2-3 file groups, explained, 2-5 layers and modules, illustrated and explained, 2-6 memory use, explained, 2-10 Service Protocol Layer, explained, 2-6 Transport Protocol Layer, explained, 2-8 NetWare hotkey setting option, explained, 3-22 NetWare Management System (NMS) software installing, 11-4 managing Desktop SNMP software with, 11-3 NetWa
Index R Rename inhibit file property, explained, 325 Requester. See NetWare DOS Requester software Requirements. See also Prerequisites cabling, 4-5 memory, for client workstations, 4-4 Resource Display setting option, explained, 3-23 Rights, NetWare Directory Services (explained), 1-18 ROUTE.COM file, using to install source routing, 10-8 S Search drive mappings in login scripts, recommended order of 8-8.
Index Workstation software, setting up 4-9.
Index I-8
