INSTALLING NETHASP ON A NETWORK HASP CD Rel 4 Rev 2.

0 June 1997 =============================== This document describes the steps required to install NetHASP and adapt the stations in the network to the NetHASP system. Along with the protected application, your software vendor should supply you with: * A NetHASP key * All the NetHASP License Managers - applications that communicate with the protected application and the NetHASP * The HASP Device Driver - an interface between the NetHASP License Manager and the NetHASP key. * The NetHASP test utilities - diagnostic tools for the NetHASP system * The NetHASP Monitor - a utility that lets you monitor the NetHASP License Managers on the network and applications that are using NetHASP licenses * Nethasp.ini - the NetHASP Configuration File - lets you change the NetHASP default settings * Nethasp.txt - this file

Networks and Protocols Supported by NetHASP ------------------------------------------NetHASP D-Link, Windows and any supports the following networks: 3Com, Banyan Vines, DEC Pathworks, Netware Lite, Novell 3.x, Novell 4.x, NT network, LANtastic, LanManager, OS/2 Lan Server, other network that uses the protocols listed below.

NetHASP supports the IPX, TCP/IP, and NetBIOS network communication protocols. IPX Support ~~~~~~~~~~~ NetHASP under IPX supports the following mechanisms: * Novell SAP (Bindery) - Novell mechanism that enables registration of applications that need network advertising. * Broadcast - while stations broadcast to the network, the NetHASP License Manager constantly listens in.

* NetHASP Address File - advertising the NetHASP License Manager through a file mechanism (address file). TCP/IP Support ~~~~~~~~~~~~~~ In environments that support TCP/IP, NetHASP operates in two modes: * TCP, UDP - the address of NetHASP License Manager is specified. * UDP Broadcast - while stations broadcast to the network, the NetHASP License Manager constantly listens in. NetBIOS Support ~~~~~~~~~~~~~~~ NetHASP supports various types of NetBIOS including Microsoft NetBEUI.

######################## The NetHASP License Manager ######################## You can connect the NetHASP to any computer on the network. This computer does not necessarily have to be the network file server. NetHASP-protected applications will communicate with the NetHASP, providing you activate the correct NetHASP License Manager. The NetHASP License Manager is not dependent on the NetHASP or the protected application, but functions as a link between the two. Regardless of the environment in which the protected application is activated - DOS, Windows, Win32, or OS/2 - you can activate any one of the NetHASP License Managers to communicate with the protected application and the NetHASP. One NetHASP License Manager can communicate with up to 250 NetHASP clients. When several applications are protected with different NetHASP keys, we recommend you daisy-chain all keys to a single computer. Alternatively, you can connect the keys to different computers but then you have to activate the NetHASP License Manager on each of these computers. Note: The NetHASP License Manager must remain active as long as any network station is running a protected application. The NetHASP License Manager you use should comply with the operating system of the computer it is loaded on. The following table lists the various NetHASP License Managers, under which operating system you activate them, and which protocols they support. NetHASP License Manager Protocol Support ============================================================ NetHASP License Manager IPX TCP/IP NetBIOS ============================================================ DOS

(haspserv.exe) -----------------------------------------------------------Windows and Win32s (nhsrvwin.exe) -----------------------------------------------------------Windows 95 and Windows NT (nhsrvw32.exe) -----------------------------------------------------------Netware 386 and 486 file servers (haspserv.nlm) -----------------------------------------------------------OS/2 (nhsrvos2.exe) ============================================================ Note: By default, the NetHASP License Manager for Win32 listens to all three protocols simultaneously.

The following sections describe the activation procedure for the NetHASP License Manager on various stations and file servers in the network. ***************************************************************************** NetHASP on a DOS Station ~~~~~~~~~~~~~~~~~~~~~~~~ The NetHASP License Manager for DOS is haspserv.exe. To load the NetHASP License Manager: 1. Connect the NetHASP to a DOS station. 2. Run haspserv.exe. A message appears informing you that the NetHASP License Manager is loaded. The message also shows which protocol is being used. Note: To load the NetHASP License Manager automatically, add its filename to the autoexec.bat file. To remove the NetHASP License Manager: * Run haspserv.exe -r. * Alternatively, delete the call line from the autoexec.bat file and reboot the station. ***************************************************************************** NetHASP on a Windows or Win32s Station ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The NetHASP License Manager for Windows is nhsrvwin.exe.

To load the NetHASP License Manager: 1. Connect the NetHASP to a Windows or Win32s station. 2. Run nhsrvwin.exe. A window appears with a message informing you that the NetHASP License Manager is loaded. It also shows which protocol is being used. Note: To load the NetHASP License Manager for Windows automatically, add its icon to the StartUp group. To remove the NetHASP License Manager: * Choose Remove from the NetHASP License Manager menu bar. ***************************************************************************** NetHASP on a Novell Netware 386/486 File Server ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The NetHASP License Manager for Novell Netware file servers is haspserv.nlm. To load the NetHASP License Manager: 1. Connect the NetHASP to a Novell server. 2. Copy haspserv.nlm to the SYSTEM directory of the file server. 3. Load the NetHASP License Manager, by entering: load haspserv The NetHASP License Manager screen appears showing the protocol that is being used. Note: To load the NetHASP License Manager automatically, add the line load haspserv to the autoexec.ncf file in the sys:system directory. To remove NetHASP License Manager: * Enter unload haspserv. ***************************************************************************** NetHASP on a Windows 95 Station ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The NetHASP License Manager for Windows 95 is nhsrvw32.exe. To load the NetHASP License Manager: 1. Connect the NetHASP to a Windows 95 station. 2. Install the HASP Device Driver on the Windows 95 station by activating:

hinstall -i. 3. Activate nhsrvw32.exe. A window appears with a message informing you that the NetHASP License Manager is loaded. It also shows which protocols are being used. To remove the NetHASP License Manager: * Choose Remove from the NetHASP License Manager main menu.

***************************************************************************** NetHASP on a Windows NT Station ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The NetHASP License Manager for Windows NT is nhsrvw32.exe. To load the NetHASP License Manager: 1. Connect the NetHASP to a Windows NT station. 2. Install the HASP Device Driver on the Windows NT station by activating: hinstall -i. 3. If you are using Windows NT version 4.0, skip to step 4. With Windows NT versions prior to version 4.0, you need to optimize the NetHASP License Manager response by setting the Tasking Option. This procedure causes Windows NT to give an equal time slice to foreground and background processes, and ensures that the NetHASP License Manager functions properly even if it is a background process. a. Double-click the System icon in the Control Panel window. b. Click the Tasking button in the System window. c. In the Tasking window Foreground/Background Responsiveness frame, click: Foreground and Background Applications Equally Responsive d. Click OK to save your settings. 4. Activate nhsrvw32.exe. A window appears with a message informing you that the NetHASP License Manager is loaded. It also shows which protocols are being used. To remove the NetHASP License Manager: * Choose Remove from the NetHASP License Manager main menu.

Automatic Activation of the NetHASP License Manager ---------------------------------------------------

Under Windows NT, you can load the NetHASP License Manager automatically before user log on. You implement this with hinstall.exe. Hinstall service. Manager. interact installs a HASP NT Loader implemented as a Windows NT This loader automatically loads the NetHASP License With the HASP NT Loader, you do not have to log on or with the Windows NT system.

To install the HASP NT Loader: 1. Log on as a user with Administrator Privileges. 2. Run hinstall -is. 3. Copy the NetHASP License Manager for Win32 - nhsrvw32.exe -to the SYSTEM32 directory in the Windows NT root directory. 4. Restart the system. The HASP NT Loader will automatically load the NetHASP License Manager. Note: Since the NetHASP License Manager loads automatically before the user logs on, the HASP NT Loader and the NetHASP License Manager messages do not appear on the screen until you log on. For example, if you try to load the NetHASP License Manager without a connected HASP, you do not see the "HASP not found" error message until you log on. To remove the HASP NT Loader: 1. Log on as a user with Administrator Privileges. 2. Run hinstall -rs. 3. Restart the system.

Viewing the HASP NT Loader Entry in the SCManager ------------------------------------------------If the HASP NT Loader was properly installed, you can see its entry in the Windows NT SCManager (Service Control Manager). To see the entry in the SCManager: 1. In the Control Panel, double-click the Services icon. The HASP NT Loader entry appears in the Services list. 2. Check that the Status field is empty, and that the Startup field is set to Automatic. *****************************************************************************

NetHASP on an OS/2 Station ~~~~~~~~~~~~~~~~~~~~~~~~~~ The NetHASP License Manager for OS/2 is nhsrvos2.exe. To load the NetHASP License Manager: 1. Connect the NetHASP to an OS/2 station. 2. Run nhsrvos2.exe. To load the NetHASP License Manager automatically at boot time: * Add the following line to the startup.cmd file: start nhsrvos2 To remove the NetHASP License Manager: * Switch to the session running the NetHASP License Manager and press <Q>. ######################### NetHASP Automatic Search ########################## The most critical stage in NetHASP system installation is ensuring that the NetHASP client (the station activating the protected application) finds the NetHASP License Manager. A communication session can begin only after the NetHASP License Manager is found. The NetHASP Automatic Search lets you connect the NetHASP, load the NetHASP License Manager, and activate the protected application, without any settings or manual changes to the NetHASP system, or the environment in which it is installed. Nevertheless, the search mechanism allows fine-tuning of the NetHASP system with simple client-server adjustments. This is implemented by the NetHASP Custom Search. Both the automatic and custom search mechanisms are described in detail below. The NetHASP Automatic Search goes into operation when the NetHASP client does not find a NetHASP configuration file (such as nethasp.ini). The NetHASP-protected application then follows the following algorithm to search for the NetHASP License Manager: ------------------------------------------------------------Begin Detect the active communication protocols; Loop up to 3 times on the procedure below: (1)perform a NetHASP LOGIN using the IPX protocol, allow n seconds for success; if LOGIN succeeds continue using IPX; else (2)perform a NetHASP LOGIN using the TCP/IP protocol, allow n seconds for success;

if LOGIN succeeds continue using TCP/IP; else (3)perform a NetHASP LOGIN using the NetBIOS protocol; if LOGIN succeeds continue using NetBIOS; else (4)return to the beginning of the loop, and double the value of n; if all fails after the 3RD loop, return a NetHASP error. End ------------------------------------------------------------Initially, when beginning the NetHASP search loop, n=2 seconds. Before following the automatic search algorithm, the NetHASP system first checks which protocols are installed, and performs only the relevant steps. For example, if only the TCP/IP protocol was detected, only step 2 in the above algorithm will be performed. It will, however, be performed up to 3 times, doubling the value of n each time.

Automatic Search under IPX ~~~~~~~~~~~~~~~~~~~~~~~~~~ Under IPX the NetHASP system uses a SAP broadcast mechanism to automate the search for the NetHASP LM. That is , the NetHASP client broadcasts, while all IPX active NetHASP License Managers listen in. The first one to answer the client - enabling a NetHASP LOGIN - will provide the NetHASP services. With the automatic search under IPX, clients and NetHASP License Managers on separate segments can communicate. Automatic Search under TCP/IP ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Under TCP/IP the NetHASP system uses a UDP broadcast mechanism to automate the search for the NetHASP LM. That is, the NetHASP client broadcasts, while all TCP/IP active NetHASP License Managers listen in. The first one to answer the client - enabling a NetHASP LOGIN - will provide the NetHASP services. NOTE! With the automatic search under TCP/IP, NetHASP clients cannot access NetHASP License Managers which are located in other segments or on the Internet. To cross segments/Internet you need to customize the search mechanism see the NetHASP Custom Search section.

Automatic Search under NetBIOS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Under NetBIOS the NetHASP system: 1. Does not limit the search to n seconds. This is because the search mechanism takes longer than the specified search time. 2. Determines which lana numbers (communication channels) are in operation and uses them for communication. 3. Uses the default NetHASP NetBIOS name ( "AladinHaspV012.0" ).

Under NetBIOS, the automatic search mechanism operates according to the application type running on the NetHASP client: DOS and Win16 applications: =========================== Win16 applications search on all detected lana numbers (communication channels) for a NetHASP License Manager. This is performed in each iteration session ( (3) in the above search loop). When a NetHASP License Manager is found, regardless of its connected NetHASP key, the search ends. The Windows NetHASP License Manager listens on the first lana number it detects. Win32 applications: =================== Win32 applications search on all detected lana numbers for a NetHASP key. That is, the search will not end when a NetHASP License Manager answers, but rather when a NetHASP License Manager with the right NetHASP key answers. The Win32 NetHASP License Manager listens on all detected lana numbers. Because communication on all detected lananums takes time, an attempt will be made to communicate on a single lananum per iteration session. If communication fails, the next iteration session will use the next detected lananum. Note: If more than 3 lananums were detected, when the algorithm loop terminates its 3 iterations, session (3) will be performed again using the remaining unchecked lananums.

########################## NetHASP Custom Search ############################ Under various environments you might want or need to customize the NetHASP search mechanism. This is done by setting keywords in the NetHASP configuration file i.e. nethasp.ini file. The nethasp.ini file is read by the NetHASP client (the protected application) to customize the search mechanism. If the NetHASP client finds a nethasp.ini file, it reads it and uses the information. If not, the above NetHASP Automatic Search will take effect. The NetHASP client searches for the nethasp.ini file in the following locations: Under DOS: 1. Current directory 2. Netware search map Under Windows: 1. Current directory 2. Windows directory 3. Windows system directory 4. Protected executable file directory

5. Path 6. Netware search map Under Win32: 1. Protected executable file directory 2. Current directory 3. Windows system directory 4. Windows directory 5. Path

The following custom of the are described at the end of which you can

sections describe the nethasp.ini keywords used for basic NetHASP search mechanism. Not all nethasp.ini keywords in these sections. A nethasp.ini file template can be found this document with a brief description of all its keywords, use for additional fine tuning of the NetHASP system.

General Custom Search Information ********************************* To change the initial value of n - the first search period in the NetHASP algorithm loop - from its default 2 seconds value, perform the following: [NH_COMMON] NH_SESSION=<seconds> where <seconds> is the desired initial search period. 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.

Custom Search under IPX *********************** Custom search under IPX is application dependent. The following sections describe 4 custom options for Win16 applications, and 2 custom options for Win32 applications. Broadcast (DOS and Win16 applications) -------------------------------------1. Load the NetHASP License Manager with the -ipx switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_IPX=enabled [NH_IPX] NH_USE_BROADCAST=enabled NH_USE_BINDERY=disabled

This option is the default. It is also used by the Automatic Search (session (1) in the algorithm loop). It instructs the NetHASP system to use the SAP broadcast mechanism to search for the NetHASP License Manager.

Bindery / Broadcast (DOS and Win16 applications) -----------------------------------------------1. Load the NetHASP License Manager with the -ipx switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_IPX=enabled [NH_IPX] NH_USE_BROADCAST=enabled NH_USE_BINDERY=enabled This option instructs Manager in the Novell or the NetHASP LM not mechanism to complete the NetHASP system to search for the NetHASP License bindery. If the bindery is not supported, found, the NetHASP system will use the broadcast the search.

Bindery / Address File (DOS and Win16 applications) --------------------------------------------------1. Load the NetHASP License Manager with the -ipx switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_IPX=enabled [NH_IPX] NH_USE_BROADCAST=disabled NH_USE_BINDERY=enabled This option instructs the NetHASP system to search for the NetHASP License Manager in the Novell bindery. If the bindery is not supported, or if the NetHASP License Manager is not found, the NetHASP system will use the address file mechanism to complete the search, i.e. looks for the NetHASP LM address in the newhaddr.dat file.

Address File (DOS and Win16 applications) ----------------------------------------1. Load the NetHASP License Manager with the -ipx switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_IPX=enabled

[NH_IPX] NH_USE_BROADCAST=disabled NH_USE_BINDERY=disabled This option instructs the NetHASP system to search for the NetHASP License Manager using the address file mechanism (looks for the NetHASP LM address in the newhaddr.dat file).

Broadcast (Win32 applications) -----------------------------1. Load the NetHASP License Manager with the -ipx switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_IPX=enabled [NH_IPX] NH_USE_BROADCAST=enabled This option is the default. It is also used by the Automatic Search (session (1) in the algorithm loop). It instructs the NetHASP system to use the SAP broadcast mechanism to search for the NetHASP License Manager.

Address File (Win32 applications) --------------------------------1. Load the NetHASP License Manager with the -ipx switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_IPX=enabled [NH_IPX] NH_USE_BROADCAST=disabled This option instructs the NetHASP system to search for the NetHASP License Manager using the address file mechanism (looks for the NetHASP LM address in the newhaddr.dat file). General Note for IPX -------------------1. NH_USE_BINDERY is equivalent to the previous NH_USE_SAP keyword. You can use either keyword. 2. Win32 applications cannot use the Novell bindery. Therefore, the keyword NH_USE_BINDERY is irrelevant for these applications. 3. By default, a NetHASP address file (newhaddr.dat) is created in the directory of the NetHASP LM. When using HASPSERV.NLM, the address file

is created in the server root directory. The NetHASP client searches for the address file in the following order: Under DOS: 1. Current directory 2. Netware search map Under Windows: 1. Current directory 2. Windows directory 3. Windows system directory 4. Protected executable file directory 5. Path 6. Netware search map Under Win32: 1. Protected executable file directory 2. Current directory 3. Windows system directory 4. Windows directory 5. Path Adding the following keyword to the nethasp.ini in the Win16 and Win32 Address File options described above, you can specify the location path for the address file. NH_DATFILE_PATH=<path>

Custom Search under TCP/IP ************************** The following sections describe 3 custom options for TCP/IP. UDP Broadcast ------------1. Load the NetHASP License Manager with the -tcpip switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_TCPIP=enabled [NH_TCPIP] NH_TCPIP_METHOD=udp NH_USE_BROADCAST=enabled This option is the default. It is also used by the Automatic Search (session (2) in the algorithm loop). It instructs the NetHASP system to use the broadcast mechanism to search for the NetHASP License Manager. Note that with this setting, NetHASP clients cannot access NetHASP License Managers which are located in other segments/Internet.

UDP --1. Load the NetHASP License Manager with the -tcpip switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_TCPIP=enabled [NH_TCPIP] NH_TCPIP_METHOD=udp NH_SERVER_ADDR=<IP address of the NetHASP LM, or NetHASP LM host name> NH_USE_BROADCAST=disabled This option instructs the NetHASP client to search for a NetHASP License Manager with the specified IP address or host name. This option lets the NetHASP cross segments.

TCP --1. Load the NetHASP License Manager with the -tcpip switch. 2. Edit the nethasp.ini file and copy it to a location accessible by the application: [NH_COMMON] NH_TCPIP=enabled [NH_TCPIP] NH_TCPIP_METHOD=tcp NH_SERVER_ADDR=<IP address of the NetHASP LM, or NetHASP LM Host name> This option instructs the NetHASP client to search for a NetHASP License Manager with the specified IP address or Host name. This option lets NetHASP cross segments. Note: This option triggers automatic dialing on computers configured for dial-up networking. This is a known side effect of initiating a TCP session on such a computer. If your only use of TCP/IP is for dial-up networking, you should use one of the two options above, or a different protocol. General Notes for TCP/IP -----------------------a. NetHASP will not cross most firewalls or packet filters. To support UDP most firewalls use packet filtering, TCP connections can be supported with either proxies or packet filtering. NetHASP uses port 475 for both TCP and UDP. To configure your firewall to allow NetHASP to work, please consult your network administrator. b. The NetHASP License Manager defaults to port number 475. If you want it to listen to another port: 1. Load the NetHASP License Manager with both the -tcpip and -portnum=<number> switches.

2. Make the following additional change to the nethasp.ini file: [NH_TCPIP] NH_PORT_NUMBER =<number>

Custom Search under NetBIOS *************************** Win16 applications search on all lana numbers (communication channels) for a NetHASP License Manager. When a NetHASP License Manager is found the search ends. If the required NetHASP key is not connected, the NetHASP License Manager will return a "HASP not Found" message. In this case you can custom the search by instructing the NetHASP system to communicate on another lana number, in order to find a NetHASP License Manager with the appropriate NetHASP. This is done by editing the nethasp.ini: [NH_COMMON] NH_NETBIOS=enabled [NH_NETBIOS] NH_USE_LANANUM=<lana number> The NetHASP search algorithm will execute session (3) in the search loop, always communicating on the specified lana number. General Note for NetBIOS: ========================= The NetBEUI protocol does not cross segments. If you are activating the protected application in a NetBEUI environment, where the NetHASP License Manager and the NetHASP clients are on separate segments, the NetHASP clients will not find the NetHASP LM. In this case, you need to load the "IPX/SPX compatible transport with NetBIOS" and set it the default protocol, to enable the communication to cross segments.

##################### Adapting NetHASP to the Network ####################### This section describes additional NetHASP LM switches and nethasp.ini keywords you can use to further adjust the NetHASP system to your network environment. Defining the Range of Stations under IPX: ---------------------------------------To allow only some of the stations to access the NetHASP in an IPXbased network: 1. Load the NetHASP License Manager with the -ipxnosap switch. This ensures that the address of the NetHASP License Manager is advertised in the NetHASP address file - newhaddr.dat.

2. Edit the nethasp.ini file: [NH_COMMON] NH_IPX=enabled [NH_IPX] NH_USE_BROADCAST=disabled NH_USE_BINDERY=disabled This instructs the protected application running on stations in the range to search for the address file and read the address of the NetHASP License Manager. 3. Copy the protected application and the nethasp.ini file to the same directory. Make sure that each station in the range, and only stations in the range, load the application from this directory.

Defining the Range of Stations under TCP/IP: -------------------------------------------There are two methods to define the range of stations under TCP/IP. You can either specify the range of stations that the NetHASP LM serves, or you can specify that the range of stations search for a particular NetHASP LM. Specifying the Range Using nhsrv.ini ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The NetHASP License Managers for Windows and Win32 can read a configuration file - nhsrv.ini. You can edit this file to specify the range of stations the NetHASP License Manager will serve under TCP/IP. The file syntax is as follows: [NH_SERVER] NH_IP_LIMIT=<ipaddr> [,<ipaddr....] where <ipaddr> can receive values with the following format: For example: 10.1.2.3 10.1.2.* 10.1.*.* - the NetHASP License Manager will serve only the station with the specified ip address - the NetHASP License Manager will serve only stations that match the specified ip address mask, i.e. 10.1.2.0 through 10.1.2.255 - the NetHASP License Manager will serve only stations that match the specified ip address mask, i.e. 10.1.0.0 through 10.1.255.255

10.1.2.3-5 - the NetHASP License Manager will serve only stations with ip address 10.1.1.3, 10.1.1.4, 10.1.1.5 The NetHASP License Manager searches for the nhsrv.ini file in the following locations: Under Windows: 1. Current directory 2. Windows directory

3. 4. 5. 6.

Windows system directory Protected executable file directory Path Netware search map

Under Win32: 1. Protected executable file directory 2. Current directory 3. Windows system directory 4. Windows directory 5. Path To allow only some of the stations to access the NetHASP LM in a TCP/IP-based network: 1. Edit the nhsrv.ini and set the range of stations. 2. Copy nhsrv.ini to a location accessible by the NetHASP LM. Specifying the Range Using nethasp.ini ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You can edit the NetHASP Configuration File to specify the NetHASP LM (according to address) for which a range of stations searches. To specify the NetHASP License Manager for which a range of station searches: Edit the nethasp.ini file and copy it to a location accessible by the protected application. [NH_COMMON] NH_TCPIP=enabled [NH_TCPIP] NH_SERVER_ADDRESS=<address of the NetHASP LM>

Defining the Range of Stations under NetBIOS -------------------------------------------To allow only some of the stations to access the key in a NetBIOS-based network: 1. Load the NetHASP License Manager with the -nbname switch set to a name of your choice (up to 8 characters, not case-sensitive). This defines the NetBIOS name of the NetHASP License Manager. For example, to load haspserv.exe and define the NetBIOS name of the station as firstsrv, enter: haspserv -nbname=firstsrv 2. Edit the nethasp.ini file: [NH_COMMON] NH_NETBIOS=enabled [NH_NETBIOS] NH_NBNAME=firstsrv

This links the stations to the NetBIOS name. 3. Copy the protected application and the nethasp.ini file to the same directory. Make sure that each station in the range, and only stations in the range, load the application from this directory. Note: You cannot have two stations with the same NetBIOS name. If you want to load the NetHASP License Manager on more than one station, you must define a different NetBIOS name for each NetHASP License Manager. Adapting the Timeout Length --------------------------The NetHASP License Manager cannot serve more than one request at a time. The timeout length determines how long a protected application repeatedly tries to access the NetHASP License Manager before giving up. In almost all networks, the default timeout values are sufficient, so you only need to change the default values in networks that have a NetHASP connected to a slow or busy station. To define the timeout length: In the appropriate section of the nethasp.ini file, set: NH_SESSION=<m> NH_SEND_RCV=<n> where m and n are measured in seconds. By default, m is 2 seconds and n is 1 second.

Defining the Number of Served Protected Applications ---------------------------------------------------NetHASP License Manager for DOS: ================================ The NetHASP License Manager for DOS allocates memory space for 250 protected applications (about 4KB). If necessary, you can save memory space by changing this default value. To change the default memory space allocation: Load the NetHASP License Manager as follows: haspserv -userlist=n where n is the maximum number of protected applications. NetHASP License Manager for Win32: ================================= The NetHASP License Manager for Win32 can serve more than the default 250 protected applications. This is done by loading the LM with a switch:

nhsrvw32 -userlist=n where n is the number of protected applications it serves.

NetHASP in Local Networks and Internetworks -------------------------------------------------This section describes NetHASP in networks that consist of several interconnected networks using the IPX protocol. With the NetHASP system, local network is a flexible term. The NetHASP License Manager and NetHASP client (the protected application) refer to the local network differently. The NetHASP License Manager refers to the local network as all the segments directly connected to the NetHASP License Manager. The NetHASP client refers to the local network as the current segment. An internetwork is a group of two or more local networks linked together. The example below shows how you can set the NetHASP client and NetHASP License Manager to work on either a local or internetwork. Adapting the NetHASP License Manager ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The internetwork in our example has two file servers: File Server 1 and File Server 2. File Server 1 has two segments with network numbers 111 and 222. File Server 2 has two segments with network numbers 333 and 444. By default, the NetHASP License Manager loaded on either File Server 1 or File Server 2 serves the entire internetwork. That means that if you load the NetHASP License Manager with no switches, it serves network segments 111, 222, 333, and 444. If you want the NetHASP License Manager to serve only stations in the File Server 1 local network (stations on segments 111 and 222): On File Server 1, load haspserv.nlm with the -localnet switch as follows: load haspserv -localnet Now the NetHASP License Manager will not serve stations on segments 333 and 444. If you want the NetHASP License Manager to serve only stations in segment 222: On File Server 1, load the NetHASP License Manager with the additional switch, -net, as follows: load haspserv -localnet -net 222 Now the NetHASP License Manager will serve stations on segment 222, but not those on segments 111, 333, or 444.

Adapting the NetHASP Client ~~~~~~~~~~~~~~~~~~~~~~~~~~~ By default, a protected application searches for the NetHASP License Manager throughout the internetwork. If you want the protected application to search only its local network for a NetHASP License Manager: Edit the nethasp.ini file as follows: [NH_COMMON] NH_IPX=enabled [NH_IPX] NH_SEARCH_METHOD=localnet If the protected application is running on a station in segment 222, the application finds the NetHASP License Manager on segment 222 only. The application does not search for a NetHASP License Manager that may be active in other local networks.

#################### NetHASP License Manager Switches ####################### This section describes the NetHASP License Manager switches and their usage.

-? ==== Applicable for: haspserv.exe, haspserv.nlm, nhdosj.exe (for NEC) Display a list of available switches.

-addrappend ================= Applicable for: haspserv.exe, nhsrvwin.exe, haspserv.nlm, nhsrvw32.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Do not overwrite the newhaddr.dat file. Add the NetHASP License Manager address to the already existing addresses in previously created address files.

-addrpath=<path> ===================== Applicable for: haspserv.exe, nhsrvwin.exe, haspserv.nlm, nhsrvw32.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Specify a location for saving newhaddr.dat. By default, the NetHASP License Manager places newhaddr.dat in the directory where it is loaded.

-help ======== Applicable for: haspserv.exe, haspserv.nlm, nhdosj.exe (for NEC) Display a list of available switches.

-ibm ========== Applicable for: haspserv.exe, nhsrvwin.exe, haspserv.nlm, nhsrvw32.exe, nhsrvos2.exe Default. Use this switch with IBM PCs to search for standard NetHASP keys only.

-ibm36 =========== Applicable for: haspserv.exe, nhsrvwin.exe, haspserv.nlm, nhsrvw32.exe, nhsrvos2.exe Use this switch with IBM PCs to search first for a NetHASP36 and then for a standard NetHASP.

-ipx ======= Applicable for: haspserv.exe, nhsrvwin.exe, nhsrvw32.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Instruct the NetHASP system to use the IPX protocol with SAP.

-ipxnosap ============= Applicable for: haspserv.exe, nhsrvwin.exe, haspserv.nlm, nhsrvw32.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Instruct the NetHASP system to use only the IPX protocol (without SAP). (With the NetHASP License Manager for Win32, you can still load other protocols by using either the -tcpip or -netbios switch or both.) When you use this switch, the NetHASP License Manager creates a file called newhaddr.dat. This file contains the node address of the station running the NetHASP License Manager. When you load the NetHASP License Manager with this switch, only protected applications with access to newhaddr.dat can communicate with the NetHASP License Manager.

-localnet ============= Applicable for: haspserv.exe, nhsrvwin.exe, haspserv.nlm, nhsrvw32.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Use this switch if you want the NetHASP License Manager to serve only requests from stations in the local network. If requests come from stations

that are not part of the local network, the NetHASP License Manager returns error 140.

-nbname=<name> ==================== Applicable for: haspserv.exe, nhsrvwin.exe, nhsrvw32.exe, nhsrvos2.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Assign a NetBIOS name to the NetHASP License Manager. This switch is identical to the -nethaspnbname switch.

-nec ====== Applicable for: haspserv.nlm, nhsrvos2.exe Use this switch with NEC computers to search for NetHASP36 keys only.

-net ====== Applicable for: haspserv.nlm Advertise the NetHASP License Manager address with a specific local network number.

-netbios ========== Applicable for: haspserv.exe, nhsrvwin.exe, nhsrvw32.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Force the NetHASP system to listen only to the NetBIOS protocol.

-nethaspnbname=<name> ======================== Applicable for: haspserv.exe, nhsrvwin.exe, nhsrvw32.exe, nhsrvos2.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Assign a NetBIOS name to the NetHASP License Manager. This switch is identical to the -nbname switch.

-openmin ============ Applicable for: nhsrvw32.exe Load the NetHASP License Manager program with its window minimized. By default the windows is maximized.

-portnum=<number> ====================== Applicable for: nhsrvwin.exe, nhsrvw32.exe, nhswinj.exe (for NEC) If you are using the TCP/IP protocol, you can use this switch to instruct the NetHASP License Manager to listen to the port you specify. The default Port Number is 475.

-r ===== Applicable for: haspserv.exe, nhdosj.exe (for NEC) Remove the NetHASP License Manager from memory.

-saptofile ============== Applicable for: haspserv.nlm When you use this switch, the NetHASP License Manager creates the newhaddr.dat file. This file contains the node address of the station running the NetHASP License Manager.

-srvname=<name>[,name] ========================= Applicable for: haspserv.exe, nhsrvwin.exe, haspserv.nlm, nhsrvw32.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Assign one or more names to the NetHASP License Manager. You can assign up to six names.

-tcpip ========== Applicable for: nhsrvwin.exe, nhsrvw32.exe, nhswinj.exe (for NEC) Force the NetHASP system to listen only to the TCP/IP protocol.

-uselananum=<x>[,<x>] =========================== Applicable for: haspserv.exe, nhsrvwin.exe, nhsrvw32.exe, nhdosj.exe (for NEC), nhswinj.exe (for NEC) Instruct the NetHASP License Manager to listen to specific lana numbers.

-userlist =========== Applicable for: haspserv.exe, nhsrvw32.exe, nhdosj.exe (for NEC) Limit the maximum number of protected applications.