Network Installation Guide - ACL V9.1.0/ACL91... · writing from the publisher, except by a reviewer who may quote brief passages in a review. ACL 9 December 2007 ... Before you install

nETWORK InSTALLATIOn GUIDE

nETWORK InSTALLATIOn GUIDE

Copyright © 2007 ACL Services Ltd.

All rights reserved.

No part of these materials may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means (photocopying, electronic, mechanical, recording, or otherwise), without permission in writing from the publisher, except by a reviewer who may quote brief passages in a review.

ACL 9

December 2007

ACL Services Ltd.1550 Alberni StreetVancouver, BCCanada V6G 1A5

Telephone: +1-604-669-4225E-mail: [email protected]: www.acl.com

Printed in Canada

ACL, the ACL logo, the ACL logo with the text, "ACL Data you can trust. Results you can see." and Audit Command Language are trademarks or registered trademarks of ACL Services Ltd.

Microsoft, Windows and Windows Server are trademarks or registered trademarks of Microsoft Corpo-ration. z/OS is a registered trademark of IBM Corporation. SAP, R/2 and R/3 are trademarks or registered trademarks of SAP AG. Crystal Reports is a trademark or registered trademark of Business Objects SA. All other trademarks are the property of their respective owners.

CONTENTS

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Elements of a network installation ................................................... 2Contacting us .................................................................................... 3

Chapter 2: Installing ACL Network Edition . . . . . . . . . . . . . . . . 5Installing the ACL Main Application ............................................... 6Installing the ACL Security Manager ............................................... 7Installing the ACL Workstation ..................................................... 10Upgrading ACL Network Edition .................................................. 15Using the ACL Network Edition .................................................... 16

Chapter 3: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17General HASP checklist ................................................................. 18HASP error codes ........................................................................... 24

Chapter 4: Custom keyless Novell . . . . . . . . . . . . . . . . . . . . . . . . 29Custom keyless Novell ................................................................... 30

ii

CHAPTER 1INTRODUCTION 1

Before you install ACL Network Edition

This guide provides instructions and troubleshooting advice for installations of ACL. Many of the procedures require full rights to the network and are best handled by a network or system administrator.

ACL documentation CDACL Network Edition software CD

In this chapter...

Elements of a network installation

Contacting us

1

Chapter 1: Introduction

■ Elements of a network installationThere are three components to ACL Network Edition. We recommend that you install the components in this order:

1 ACL Main Application

2 ACL Security Manager

Aladdin Monitor is available on the ACL Network Edition CD-ROM or from the Utilities section, under Downloads, at the ACL Support Center website.

■ For Windows users:- HASP License Manager- HASP HL Device Driver- HASP HL Net key- Aladdin Monitor (optional)

■ For Novell HASP users:- HASPserv.nlm- nethasp.ini

3 ACL Workstation (end user)

ACL Network Edition uses the HASP copy-protection scheme, but other copy-protection options exist for special circumstances. Contact the ACL Global Help Desk for details.

2 Network Edition Installation Guide

Contacting us

■ Contacting usIf you cannot find the solution to your problem and you are a supported user, you can contact ACL for assistance.

When contacting ACL, be sure to have the following information on hand:

■ Your ACL serial number. You can find this on the back of your CD case, or in ACL Workstation, select Help from the menu bar and choose About ACL.

■ The type of hardware key you are using, and whether it is connected to a Local Area Network (LAN).

■ A description of what happened, and what you were doing when the problem occurred.

■ The error message, if any, displayed by ACL.

Contact the ACL Global Help Desk

The Americas+1-604-669-4997

Asia and Pacific Rim+1-604-669-4997

Europe, Middle East, and Africa+32-2-642-22-95

Germany0800-187-3672

United Kingdom+44-845-351-0077

or e-mail us at [email protected].

Network Edition Installation Guide 3

Chapter 1: Introduction


CHAPTER 2INSTALLING ACL NETWORK EDITION 2

Install the ACL Main Application, ACL Security Manager, and ACL Workstation

Before you install ACL Network Edition, make sure you have:

■ An ACL Network Edition CD-ROM

■ A network hardware key or dongle - For a Windows implementation, use a HASP HL Net key (USB key only) or a HASP4 Net key (USB or parallel key)- For a Novell implementation, use a HASP4 Net key (parallel key only)

■ The ACL Network Edition Installation Guide

Note: The default installation of the ACL Security Manager applies only to Windows users. If you are a Novell user, refer to “Completing the installation with the Novell NLM option”.

Remove all HASP USB hardware before you install ACL Security Manager.

In this chapter...

Installing the ACL Main Application

Installing the ACL Security Manager

Installing the ACL Workstation

Upgrading ACL Network Edition

Using the ACL Network Edition

5

Chapter 2: Installing ACL Network Edition

■ Installing the ACL Main ApplicationYou require full administrative

rights to the directory in which you install this software.

Whether you install ACL Network Edition from a CD or from the ACL Support Center website, the procedures are the same except for how the installation wizard is launched.

Launch the Installation WizardEvery end user must have access

to the ACL Main Application.■ In a CD installation, the installer launches automatically.

If the installer does not launch, browse the CD and double-click setup.exe.

■ If you are installing ACL Main Application from the ACL Support Center website, follow the instructions from the website.



■ Installing the ACL Security ManagerYou can use almost any machine on the network as the ACL Security Manager provided the hardware key is installed in the parallel or USB port of this machine. The ACL Security Manager monitors the number of concurrent users on a network and restricts the use of ACL to the number of licensed users at one time.

The designated ACL Security Manager must be active and the HASP License Manager must be running at all times.

The HASP License Manager functions as a link between the protected application, in this case, the ACL Main Application, and the key. You must run the HASP License Manager whenever you use ACL Network Edition.

The ACL Security Manager installation installs the HASP License Manager for Windows 2000, Windows XP, Windows Vista, and Windows 2003 Server. It also automatically installs the HASP device driver if the system does not already have one.

The installer requires full administrative rights.

PrerequisitesMake sure that you know:

■ The network protocol that you are using, such as UDP, NetBIOS, or IPX.

UDP is the preferred choice because it is adaptable to a variety of network configurations. If you use UDP, you also need to know your IP address or computer name of the server machine.

■ The operating system of the computer that acts as ACL License Manager machine.

■ The path of the installed ACL win.exe program.



The ACL Network Edition versions 9.0 and up support these operating systems and protocols.

Installing the HASP License ManagerTo install the HASP License Manager program, you must start the installation on a machine that runs Windows. This will be the ACL Security Manager itself if the HASP License Manager is a Windows machine.

To install the HASP License Manager program:

1 Insert the CD-ROM into the CD-ROM drive.

2 If the installation program starts automatically, follow the prompts.

If the installation program does not start automatically, click Start and select Run, then in the Open: text box, enter d:\setup. Click OK and follow the prompts.

3 When you are asked to select the action that you would like to perform, select the Install one of ACL’s products option, and then select ACL Security Manager.

4 Now proceed to the section that applies to the operating system of the ACL Security Manager machine.

Operating System Protocol

IPX UDP NetBIOS

Windows 2000, Windows XP, Windows Vista, and Windows 2003 Server

X X X

Novell (NLM) X



Completing the installation with the Novell NLM optionYou must use a Network Load Module (NLM) if you use a Novell server as the ACL Security Manager.

Before you install any NLMs on a Novell file server, make sure that you understand how NLMs can affect the network.

You require full administrative rights to complete the installation.

To complete the ACL Security Manager for Novell installation, follow these steps:

1 ACL will prompt for the desired operating system on which the ACL Security Manager will reside. Select Novell to continue.

2 Follow the instructions to complete the installation.

3 Obtain the ACL Security Manager for Novell from the CD or from the ACL Support Center website.

On the CD, ACL Security Manager is located in the ACLNovell_LM folder.

From the ACL Support Center website, in the Utilities section, under Downloads, select ACLNovell_LM.exe. Extract the file to the default location or to the desired location.

The following two files are extracted: HASPserv.nlm and nethasp.ini.

4 Copy the nethasp.ini file created in Step 3 to the ACL Main Application program directory.

5 Copy the HASPserv.nlm created in Step 3 to a location on the Novell server where you can load the NLM.

The HASP hardware key must be attached to the Novell server that is running the ACL Security Manager.

6 On the Novell server, load the HASPserv.nlm as you would load any other NLM. However, you will need to append the following parameter:

-ipxnosap

7 After the HASPserv.nlm is loaded, two files are created on the system root. The files appear as NEWHADDR.dat and HASPADDR.dat. Copy these files to the ACL Main Application program directory.



■ Installing the ACL WorkstationOnce you install the ACL Main Application, you can install ACL on the workstations of each user that requires access to ACL.

The Workstation installation program installs shortcuts and sample data files that you use to run ACL on your machine from the network. The installation program is on the machine in the root folder or directory where you placed the ACL Main Application files.

System requirementsThe system requirements for the installation of ACL are as follows:

If you are using SMS distribution to install the workstation, Microsoft System Management Server (SMS) 2003 is also required.

■ Windows Installer Version 2 or later

■ Microsoft Internet Explorer 6 or later

■ MDAC 2.8 - Microsoft Data Access Component 2.8 or later

■ MsJet 4 SP3 - Microsoft Jet database engine 4.0 Service Pack 3

Workstations must run Windows 2000 or Windows XP at a minimum.

■ MSXML 4.0 - Microsoft XML Parser 4.0

Standard installation of ACL WorkstationTo set up individual workstations:

1 Click Start and select Run, then Open: text box, enter the path to the workstation installation program, setupws.exe. For example, if you installed the root folder on f:\ drive, enter f:\acl\ws\setupws.

Alternatively, in the root folder, you can double-click setupws.exe, in the WS folder.

The installation program prompts you for a personal data directory, which provides private access to the preference file and to unshared documents. Select a directory or folder that is accessible the end user. Use other directories for shared data.

2 Click OK to start the installation.

3 The installation program informs you of its progress and prompts for information as required. Follow the instructions to complete the installation.



Silent installation of ACL WorkstationSilent installation of the ACL

Main Application and ACL Security Manager components is not supported.

You can use the silent installation method to install the ACL Workstation component of ACL Network Edition. Please consult your system administrator before using this method.

Using the command line

To run the silent installation from the command line, you use the Msiexec command with the appropriate command-line options.

Command-line syntaxThis is the command-line syntax for the silent installation of ACL:

msiexec /i <.msi> /q[n][b][r][f] ACLEXEPATH=<Path> [INSTALLDIR=<Path>] [ALLUSERS=<NULL>]

Example:

msiexec /i "C:\WS\ACL9.msi" /qn ACLEXEPATH="C:\ACL Software" ALLUSERS=1

Command-line parameter

/i Installs or configures a product

/q Quiet mode, no user interaction

/q[n|b|r|f ] Sets user interface level:

n - No UI (default)

b - Basic UI

r - Reduced UI

f - Full UI



Installation properties

Your system administrator can consult the Windows Installer SDK for additional documentation on the command-line syntax.

Property Name

Required Acceptable value

Default Value

Explanation

ACLEXEPATH Y Valid path NULL A network location of ACLWin.exe. See the system administrator for location.

ALLUSERS N NULL or 1 Determines where the configuration information of the installed application is stored.

NULL - Per-user installation using folders in user’s personal profile. (NULL is programmatically represented by an empty string, for example, "".)

1 - Per machine installation using folders in “All Users” profile.

NSTALLDIR N Valid path C:\ACL Data\Sample Data Files

Destination directory for Workstation data files. (Because this is the default working directory, read/write access is required.)



Using SMS distributionConsult your system

administrator for information on SMS settings and protocols.

Microsoft Server Management System (SMS) 2003 must be installed if you are using SMS distribution to install the workstation.

Editing the product definition fileA sample product definition file is provided with the workstation installation image (located in the WS directory). For example:

[PDF]Version = 2.0

[Package Definition]Name = ACL9WSVersion = 9.0.0.232Publisher = ACL SoftwareLanguage = EnglishPrograms = SetupMifFileName = ACL9WS.mifMifName = ACL9WSMifVersion = 9.0.0.232MifPublisher = ACL Software

[Setup]Name = Automated Minimum InstallationCommandLine = msiexec /m "ACL9WS.mif" /qn /I "ACL9WS.msi" ACLEXEPATH=<Path>SupportedClients = Win NT (i386)UserInputRequired = FalseRemoveProgram = TrueUnInstallKey = {DD28C9DA-64D2-4A15-A47D-4C9F2CB9BAAD}

You must edit the ACLEXEPATH=<Path> parameter of the CommandLine in the ACL9WS.sms file above:

CommandLine = msiexec /m "ACL9WS.mif" /qn /I "ACL9WS.msi" ACLEXEPATH=<Path>

<Path> must be replaced with a valid path of ACLWin.exe on the network. For example:

CommandLine = msiexec /m "ACL9WS.mif" /qn /I "ACL9WS.msi" ACLEXEPATH="C:\ACL Software"

Option/m of the CommandLine causes the installer to generate an SMS Management Information Format (.mif) file. The



ISMIF32.DLL is installed as part of SMS and must be on the PATH.

If you require additional information, contact the ACL Global Help Desk.

You can add any additional properties from the Command-line properties table in the previous section as appropriate.

It is recommended that you add ALLUSER=1 to the CommandLine to perform per-machine installation (default is per-user, installing the application to the current user).


Upgrading ACL Network Edition

■ Upgrading ACL Network EditionYou can upgrade your current version of ACL Network Edition from a CD or from the ACL Support Center website.

Upgrade the ACL main applicationTo upgrade ACL Network Edition:

1 Launch the installation wizard. The installation wizard is launched automatically when you open the CD or download ACL from the website. If the wizard does not launch from the CD, browse the contents and double-click setup.exe.

2 Follow the instructions of the wizard. During the installation process, the wizard removes the existing version of ACL Network Edition and installs the new version.

If upgrading ACL from a Unicode to a non-Unicode version, remove the software manually by using the Add or Remove Programs feature in Windows.

Upgrade ACL WorkstationAfter installing the server portion of ACL Network Edition, you must upgrade ACL Workstation. To do so, click on setupws.exe, located in the WS subfolder under the newly installed ACL directory.

In some ACL versions, the workstation update file is update.exe, located in the Update subfolder, under WS in the ACL directory.



■ Using the ACL Network EditionTo use ACL on the network, do the following:

1 Start the HASP License Manager. You must always run the ACL Security Manager when you use ACL.

2 To run ACL on a workstation, click Start, select Programs » then navigate to the ACL program icon.


CHAPTER 3TROUBLESHOOTING 3

Resolve common installation issues

This chapter provides a checklist for both HASP and Novell installations. It also describes the error codes that you can encounter during a HASP installation.

For more detailed information about HASP software protection, go to http://www.aladdin.com.

In this chapter...

General HASP checklist

HASP error codes

Novell checklist

17

Chapter 3: Troubleshooting

■ General HASP checklist

Here are items that you can check if you experience problems with a HASP installation.

ACL Security Manager

If changes occur at the ACL Security Manager level, users may not be able to run ACL. Confirm that the ACL Security Manager is a workstation that runs a file server with a Novell, Windows 2000, Windows XP, Windows Vista, or Windows 2003 Server operating system.

Network Type

Confirm that the network type is either Windows or Novell.

ProtocolsEarlier versions of ACL support

TCP/IP.Confirm that the protocol is either UDP, IPX, or NetBIOS. If the ACL Security Manager is Novell, you must use IPX protocol.

Location of NetHASP.ini

The NetHASP.ini file must be in the same directory as the aclwin.exe file.

Key attached

Make sure that the hardware key is attached to the port of the ACL Security Manager.

Server software running

Make sure that the license manager software is running when ACL Network Edition is in use.

Protocols loaded

To confirm which protocols are loaded, check the HASP License Manager.



Autoload HASP License Manager

Check the NLM to make sure it is launching with -ipxnosap.

Automatically load server software

The HASP License Manager launches before logon and continues to run after logout.

ACL Security Manager Disk Setup (Novell)

Confirm that the HASP Licence Manager software is installed on the ACL Security Manager. You can install the License Manager software (Version 8.3.1 or later) on a workstation. It is also possible that the user loaded the NLM without running setup to install the software. This means there would be no NetHASP.ini. This applies only if the ACL Security Manager is a Novell operating system.

Maximum number of users

If all users can log on to ACL, the “error code 3.4” message may be valid. If some users can log on and some not, make sure the protocol is set up correctly on each machine. If the protocol is UDP, make sure that all users can ping the ACL Security Manager. If there are communication problems on the network, some workstations may be able to access ACL, while others get the “error code 3” message.

NH_SESSION=30 Added and NH_SEND_RCV=15 Added

The HASP License Manager can serve only one request at a time. The timeout setting determines how long a protected application



repeatedly tries to access the HASP License Manager before giving up. In almost all networks, the default timeout values are sufficient, so you need to change only the default values in networks that have a HASP connected to a slow or busy server.

To change the timeout length, edit these lines in the NetHASP.ini file, set:

NH_SESSION=<m>NH_SEND_RCV=<n>

where m and n are measured in seconds. m sets the maximum length of time during which the ACL application attempts to communicate with the HASP License Manager. n sets the maximum length of time for the HASP License Manager to either send or receive a package. If these lines are missing, the default m is 2 seconds and n is 1 second. ACL places these lines in the NetHASP.ini at m=30 and n=15.

Setting the NH_SESSION keyword in the NH_COMMON section applies to all protocols. To set the session value for each protocol independently, set the value of NH_SESSION in each protocol section separately.

Monitor found server

If the Aladdin Monitor finds the HASP License Manager, the setup is correct. The askmon.exe file must be in the ACL software directory in the Monitor subdirectory, as it needs to find NetHASP.ini and the two .dat files in the case of IPX. The NetHASP.ini file is required if you are running the HASP version of ACL. You need the .dat files if you are using the IPX Protocol.

Monitor shows which workstations are logged on to ACL.

Note: Contact ACL Global Help Desk to obtain the askmon.exe file.



Administrative Rights on the ACL Security Manager (Novell)

You must have full administrative rights to install the NLM on a Novell ACL Security Manager.

Command-line parameters

Confirm that you used the correct syntax for the switches so that the NLM loads with the right switch.



IPX (Novell HASP)Load the HASP License Manager with the -ipxnosap switch and check the following as required.

HAPADDR.dat and NEWHADDR.dat

The HAPADDR.dat and NEWHADDR.dat files are created in the root directory. Confirm that they have been copied into the ACL Software directory. They contain the IP address of the ACL Security Manager. If the NLM is loaded with the -ipxnosap switch or no switch at all, only the HASPADDR.dat file is created.

NH_IPX=Enabled

Make sure this line is in the NH_COMMON section of NetHASP.ini.

On the same segment

Confirm that the ACL users and the ACL Security Manager are on the same network segment. IPX is not as good as TCP/IP at crossing segments.

Server Trying to Run ACL

The ACL Security Manager cannot run ACL if IPX is the protocol.

IP address for ACL Security Manager is correct

The correct IP address or machine name must be in the NH_TCPIP section of the NetHASP.ini file.

NH_TCPIP=Enabled

Check NetHASP.ini for this line in the NH_COMMON section.

Address static or dynamic

If the IP address of the ACL Security Manager is dynamically allocated use the machine name or list multiple IP addresses in the NetHASP.ini.



NH_TCPIP_METHOD=UDP ? For more information on HASP HL visit www.aladdin.com.

UDP uses the broadcast mechanism to search for the HASP License Manager.

NH_USE_BROADCAST=Enabled

This NetHASP.ini entry enables the UDP broadcast mechanism to search for the HASP License Manager.

Port setting changed (only if through firewall)

The default port setting is 475. To change it, add the following command to NetHASP.ini so ACL talks to a different port and the ACL Security Manager listens to a different port.

[NH_TCPIP]NH_PORT_NUMBER=<number>

NetBIOS The NetBEUI (Microsoft’s version of NetBIOS) protocol does not cross segments. If you activate the protected application in a NetBEUI environment in which the HASP License Manager and the HASP clients are on separate segments, the HASP clients cannot find the HASP License Manager. In this case, you need to load the “IPX/SPX compatible transport with NetBIOS” and set it to the default protocol, enabling the communication to cross segments.

Server Name checked

The machine name is stored in a NetBIOS table.

NH_NETBIOS=Enabled

Check NetHASP.ini for this line in the NH_COMMON section.



■ HASP error codesHASP error messages use the form “Copy type X Error Code YY”. The system type for HASP keys is 0, 1, or 2. That value, combined with the error code, comprises the HASP code. For example, if the system type is 1 and the code is 29, the HASP error code is 129.

Code numbers up to 129 represent communication errors, and those from 129 and up represent HASP License Manager errors.

You can also obtain this list from the Nhsrvw32.hlp file.

Error Code Description

0 Operation successful.

1 Request exceeds the HASP HL memory range.

2 Request unknown.

3 System is out of memory.

4 Too many open handles.

5 Access to feature is denied.

6 Legacy decryption function does not work on the feature.

7 HASP HL key is no longer available.

8 Decrypted data length is too short to execute the function call.

9 You have passed an invalid handle to the function.

10 API does not recognize the specified file ID.

11 Installed driver is too old to execute the function.

12 A real-time clock (rtc) is not available.

13 Generic error from host system call.

14 Required driver is not installed.

15 Unrecognized file format for update.


HASP error codes

16 Function cannot be executed in this context.

17 Binary data passed to the function does not contain an update.

18 HASP HL license you requested to update has not been found.

19 Required XML tags not found. Contents in the binary data are missing or invalid.

20 HASP HL key does not support the update request.

21 Update counter is not set properly.

22 You have passed an invalid vendor code.

23 Used hardware does not support the encryption type.

24 Passed time value is beyond the supported value range.

25 Real-time clock battery has run out of power.

26 Acknowledge data requested by the update ack_data parameter is NULL.

27 Program is running remotely on a Terminal Server.

28 Type of feature requested is not implemented.

29 Unknown algorithm used in V2C file.

30 Signature verification operation has failed.

31 Requested feature is no longer available.

500 Object not initialized correctly.

501 Parsed parameter is incorrect.

502 Logging in twice to the same object.

503 Logging out twice from the same object.

525 Error related to incorrect use of system or platform.

698 Requested type of feature is not implemented.




Copy type 0 error code 7 and Copy type 1 error code 29

These error codes indicate that a HASP TCP/IP connection error has occurred. The following is a list of the most common connection problems and their solution.

Problem Solution

The red hardware key was removed from the security server or is not plugged properly.

Make sure that the hardware key is properly attached to the port of the ACL Security Manager.

The hardware key is plugged in a parallel port but the port is disabled in the BIOS.

Enable the parallel port in the BIOS.

The HASP License Manager is installed but it is not running on the ACL Security Manager.

If the ACL License Manager is installed as a service, ensure that the HASP LOADER service is started.

If the ACL License Manager is installed as an application, run nhsrvw32.exe.

The ACL License Manager is running but the TCP/IP protocol is not loaded.

Open the ACL License Manager application and select Load > TCP/IP.

The ACL Security Manager requires Windows 2003 Server operating system.

The ACL License Manager must be version 8.2 or higher. If an earlier version is installed, download version 8.2 from the ACL website.

The ACL Security Manager cannot be pinged successfully from the user’s workstation.

To test whether you can ping the ACL Security Manager, look up the IP address in NETHASP.ini. In Windows, click Start > Run. In the Open box, enter PING <IP address>. Click OK. You must receive a reply to use ACL. If the attempt to ping the Security Manager times out, your IS department may be able to resolve the issue.

The user’s workstation has Windows XP SP2 operating system installed.

Turn off Windows firewall in the Control Panel. To keep Windows firewall enabled, add the ACL program or port 475 to the Exceptions list.


HASP error codes

A text file called NETHASP.ini cannot be found in the ACL Program Files directory.

Create the NETHASP.ini file by one of these methods:

- If a previous version of ACL Network Edition is installed, copy NETHASP.ini from the old ACL Program Files directory to the current one. You may need to update the IP address of the ACL Security Manager as shown below.

- Create a new text file in Notepad and enter the following:[NH_COMMON]NH_TCPIP=EnabledNH_SESSION=30NH_SEND_RCV=15

[NH_TCPIP]NH_SERVER_ADDR=000.000.000.000NH_TCPIP_METHOD=TCPNH_USE_BROADCAST=Disabled

Replace 000.000.000.000 with the IP address or the DNS (full domain name) computer name of the ACL Security Manager. If the ACL License Manager is on the same computer as the ACL executable and you are using the “loopback” address of 127.0.0.1, make sure the loopback feature on your workstation is enabled. In Notepad, change the Save As Type setting from Text Documents to All Files. Save this file as NETHASP.ini in the ACL Program Files directory.

NETHASP.ini exists but the IP address in the NH_SERVER_ADDR section is incorrect.

Open NETHASP.ini in Notepad and correct the IP address or computer name in NH_SERVER_ADDR. Save the file in the ACL Program Files directory.

Problem Solution




CHAPTER 4CUSTOM KEYLESS NOVELL 4

Resolve common installation issues

This chapter provides instructions for keyless Novell installations, and only applies if you have licensed the Custom keyless Novell product.

For more detailed information about Novell software, go to http://www.novell.com.

In this chapter...

Obtaining the serial number

ACL.ini settings

Error messages

29

Chapter 4: Custom keyless Novell

■ Custom keyless NovellThe Novell version is a solution for those who wish to have their central system within their Novell network. The serial number must be ascertained at the time of installation, and if the server is subsequently upgraded, a new ACL.ini file will be required.

Obtaining the serial numberContact the ACL Global Help Desk

and get WINSERNO.exe to return the serial number.

There are a number of ways to find the eight-digit Novell serial number, which is hard-coded into the ACL.ini file.

There are two other approaches depending on which version of Novell you are running. However, both methods require supervisory access to the Novell server.

Novell 3.x

1 Invoke Syscon.

2 Select Fileserver Information.

Novell 4.x or 5.x

1 Run NetAdmin on the desired server.

2 Select Manage Objects.

3 Select NetWare Server Objects, Class.

4 Select View or Edit Properties of this Object.

5 Select View Server Information.

The server serial number is listed here.

ACL.ini settingsHere is a sample Novell version ACL.ini file.

[ACL User Info]UserName=ACLDefName=ACLSerialNo=1234567[Network]Type=NovellNovellNo=98765432Userscnt=1Security=6465-4748-0024-2283


Custom keyless Novell

Error messagesNovell returns error messages that are a copy type 4. For example, “Copy type 4, error message 25”, means an incorrect Novell serial number.The following are the possible error codes:

Error Codes

Code 25

Code 25 indicates an incorrect serial number. ACL’s request for the serial number goes to the drive of ACL’s working directory. If that directory is located on a Novell server, the right serial number is returned. However, if the working directory is on a local drive, the serial number that will be returned is the first server the user logs on to.

To test for this, run ACL from the server directory in Explorer. If ACL starts, this confirms that the starting directory is the problem.

To correct the problem, set up the ACL shortcut with the working directory on the proper server. This working directory must be unique and the user must have full rights to the preference file.


1 Security code does not match that generated by ACL.

2 ACL Serial number is missing from ACL.ini.

8 Novell Serial number missing from ACL.ini.

9 ACLNOV.DLL, or one of the required Novell DLLs is missing.

16 Number of LAN users missing from ACL.ini.

25 Novell serial number wrong.

64 Security code missing from ACL.ini.


Chapter 4: Custom keyless Novell


© 2

007

AC

L S

ervi

ces

Ltd.