Overview

The Novell Client is a powerful and feature rich service that is necessary to gain the full functionality of a Novell NetWare system. The Novell 4.91 client runs on a Windows 2000 or Windows XP workstations and allows your workstation to authenticate to eDirectory, login to Open Enterprise Servers (NetWare AND Linux Kernels), connect to server file systems, access Novell printers, and more.

Who Needs the Novell Client

The Novell client is not specifically required, but most network services are severly crippled without it. As a rule of thumb, the Novell Client is what makes NetWare and Open Enterprise Server stand tall above other Network systems. Once you have used the Novell Client, working without it seems like you've taken a trip back into the dark ages.

As a standard practice, Marvin Huffaker Consulting recommends the Novell Client be installed and used on enterprise workstations. Exceptions to this rule are rare.

About Marvin Huffaker Consulting, Inc.

Marvin Huffaker Consulting, Inc. is a professional services firm specializing in enterprise level network and security based solutions. We have a reputation for quality, expertise, service, and the ability to get things done. We have clients across the United States and can provide projects and support nearly anywhere in the world. We can be reached at 480-988-7215 or 1-888-690-0013 (US Only) or at our website at http://www.redjuju.com.

Downloading and Extracting the Novell Client

Note: You may have received a Novell Client CD with your Novell Open Enterprise Server purchase. While this will work, it's generally best to download the most recent version from Novell's website.

1. Go to http://download.novell.com

2. Find "Novell Client 4.91 SP2 for Windows 2000/XP/2003, Full Product, English" (Or whatever language you need. This guide covers English Only). Note: The most recent client is generally on the top 10 most popular downloaded files.

3. You should end up with a file called "Novell Client 4.91 SP2 English.exe." The file is a self-extracting executable. Run it and extract the files to a location on your workstation. A good place is C:\Novell\ClientInstall, but it really doesn't matter.

4. When you are done extracting the client, you should have a folder structure that looks similar to this picture below.

5. Note that at this point, the client is NOT installed. It is simply downloaded, extracted, and ready to be installed. The SETUPNW.EXE file is used to actually launch the installation.

   Illustration 1: Novell Client Installation Directory

Installing the Novell Client

The actual installation of the Novell Client is easy. The following steps walk you through it as well as explain any things you may be wondering about.

Step 1 - Launch the Installation

To launch the Novell Client installation, run the SETUPNW.EXE file as depicted in Illustration 1.

Step 2 - Choose the Installation Type

The first thing you do is choose whether you want a Typical Installation or Custom installation. You should choose Custom Installation. A "Typical" installation will not allow you to choose certain options, and it's critical to have control of the process. Some of the default options may not be what you need.

Illustration 2: Installation Option Screen. Choose 'CUSTOM INSTALLATION' for better control of the installation process.

Step 3 - Component Selection Screen

On the Component Selection screen, there are only two options. However, it's important to make sure that both are checked.

Novell Client for Windows

This is the actual Novell client. It's not optional and it cannot be deselected.

Novell Distributed Print Services

You definitely want this. Installing this component, abbreviated NDPS, gives you the ability to automatically deliver printers, drivers, and configurations to the workstations. Policies can be set to remove printers and add new printers with no end user interaction. NDPS saves an incredible amount of time on end user support and administration. It's an enterprise level solution that works better than any competitors products or services.

If you have NDPS configured on the server already, the NDPS component will immediately enable network printing. If you still need to install NDPS on the server, it's nice to have the pieces already in place on the workstations.

Illustration 3: Component Selection Screen. Select both "Novell Client for Windows" and "Novell Distributed Print Services."

Step 4 - Add on Product Selection

All of the components on this screen are optional. However, they add functionality that you probably want, so it's best to install them. You should choose the first two options, Novell Modular Authentication Service and Novell International Cryptographic Infrastructure. The third option, NetIdentity, is not necessary.

Novell Modular Authentication Service

This needs to be installed to allow enhanced security and stronger password policies and capabilities.

In some cases, NMAS has caused problems with certain workstation functions. This is not typical,and with a properly configured server there should not be any issues. Besides, it can be disabled on the workstation if any problems do arise.

Novell International Cryptographic Infrastructure

This must be installed if NMAS is installed and helps provide support to some of the NMAS functions.

NetIdentity Agent

This does not need to be installed in most cases. Only install this if you know of a specific reason to do so. Otherwise don't.

Illustration 4: Additional Product Screen. Choose '"Novell Modular Authentication Services (NMAS) and "Novell International Cryptographic Infrastructure (NICI)"

Step 5 - Protocol Selection Screen

The Protocol Selection Screen is a critical step. This is what determines how the workstation communicates to the server(s). While to some this is obvious, other people may not know what they should choose. Without the right protocol installed, the workstation will not be able to login to the server.

The protocol you should use is largely determined by how the servers in your environment are configured. However, with NetWare 6.5 and Open Enterprise Server, IP is the protocol of choice.

IP Only (Choose This Option)

All NetWare servers since NetWare 5.0 have had the capability of using TCP/IP as the core network protocol. It is very unusual to find a server in the year 2006 that does not have TCP/IP configured. For this reason, choosing IP only is a safe bet. Furthermore, you should allow the installation to remove IPX from the workstation, in case it was ever previously configured.

IP with IPX Compatibility

Without providing a long drawn out explanation, this option should NEVER be used unless a highly trained Novell consultant tells you to use it. Some people mistakenly choose this thinking it is required to run both the IP and IPX protocol.

IP and IPX

You should not need this, and it may slow down certain network functions. Only select this option if you have older servers mixed with newer servers. For example, a tree with both NetWare 4.11 and NetWare 6.5 in it.

IPX

IPX (only) is for systems running legacy NetWare systems that are version 3.1x or 4.1x. These versions of NetWare require IPX to communicate. If you don't have these versions, you don't need IPX. IPX causes extra LAN traffic and is considered obsolete.

Illustration 5: Protocol Selection Screen. Choose '"IP Only" and "Remove IPX if present.

Step 6 - Login Authenticator Screen

This is a no-brainer. You want to choose NDS. There is no reason to choose Bindery, and if you do, your network functionality will be severely crippled.

NDS(NetWare 4.x or Later)

All NetWare servers since NetWare 4.x, including Open Enterprise Server, utilize NDS for authentication and user management. NDS has since been renamed to eDirectory, but sometimes the terms are interchangeable.

Bindery (NetWare 3.1x)

You should not use this option unless you actually have a NetWare 3.1x server, and you don't have any NetWare 4.x or higher servers in your network.

Illustration 6: Login Authenticator Screen. Choose "NDS (NetWare 4.x or later)"

Step 7 - Finish Screen

At this point, just select "Finish" and the client installation will proceed. All options have been chosen and now some files are copied and other misc. tasks completed.

Illustration 7: File Copy Process.

Step 8 - Reboot Screen

Once all files are copied, you are prompted to reboot. Don't attempt to use the client until you have rebooted.

Illustration 8: Reboot

Step 9: What You Should See After the Reboot

After your system reboots, you should get a "Novell Client Login Dialog." The Novell Client login dialog replaces the standard Windows login.

Illustration 9: Login Dialog after the Novell Client is Installed and System Rebooted

Step 10 - What's Next

There are numerous things you need to know about using the Novell Client. These tasks are not within the scope of this document. Please refer to our other tutorials for information on the following:

• Logging into a Novell eDirectory Tree / Server

• Configuring and Optimizing the Novell Client

• Automating the Novell Client Deployment Process

• Automating Printer Deployment with NDPS

• More...