Copyright: Aladdin Knowledge Systems Ltd. © 1997


Advanced Settings for All Protocols

The Advanced Settings for All Protocols screen contains the following options:

Timeout Length

The timeout length is the amount of time (in seconds) a protected application attempts to perform a NetHASP LOGIN.

The protected application attempts to login using all the protocols you specified in the Communication Protocols screen until it succeeds.  The application first tries to login using IPX, then TCP/IP, and then NetBIOS (depending on your selection of protocols).

By default, the protected application tries to login for a communication time of 2 seconds with each protocol.  If the login fails with each of the selected protocols, the protected application tries again, doubling the communication time to 4 seconds per protocol.  If login fails again with each of the selected protocols, the communication time is doubled once again to 8 seconds.  If the application still cannot perform a NetHASP LOGIN, it returns an error.

In this screen, you can change the initial communication time from its default value of 2 seconds.

You can also change the amount of time the protected application attempts to send or receive a packet.  The application attempts to send or receive packets using a specific protocol until the attempt is successful, or until the end of the communication time.  If the application cannot login, the send/receive packet time is doubled when the communication time is doubled.

In this screen, you can change the initial send/receive packet time from its default value of 1 second.

Machine Type

Select the type of computer your application uses: either an IBM Compatible PC, or a Japanese NEC.  The default value is IBM.


Advanced Settings for IPX

The Advanced Settings for IPX screen contains the following options:

General

Socket Number	Enter a socket number on which the client searches for the NetHASP License Manager.

The default socket number is 7483H.

Interrupt	Choose either 2F_NEW or 7A_OLD as the interrupt method.  Former IPX Drivers used Interrupt 7AH as the main interface for the IPX protocol.  Use 7AH to provide backward compatibility for drivers which do not support Interrupt 2FH.

The default method is 2F_NEW.

Search Method	Choose Internet to cross segments, or Localnet to limit your search to the local segment.

The default method is Internet.

NetHASP LM Logical Name(s)

The NetHASP License Manager logical name is used to direct the client to login to a particular License Manager.  You can direct a client to search for a maximum of 6 License Managers.  Enter the License Manager name (up to 7 characters), and click Add.  To remove a License Manager from the list, select it and click Remove.

Timeout Length

The timeout length is the amount of time (in seconds) a protected application attempts to perform a NetHASP LOGIN.

The protected application attempts to login using all the protocols you specified in the Communication Protocols screen until it succeeds.  The application first tries to login using IPX, then TCP/IP, and then NetBIOS (depending on your selection of protocols).

By default, the protected application tries to login for a communication time of 2 seconds with each protocol.  If the login fails with each of the selected protocols, the protected application tries again, doubling the communication time to 4 seconds per protocol.  If login fails again with each of the selected protocols, the communication time is doubled once again to 8 seconds.  If the application still cannot perform a NetHASP LOGIN, it returns an error.

In this screen, you can change the initial communication time from its default value of 2 seconds.

You can also change the amount of time the protected application attempts to send or receive a packet.  The application attempts to send or receive packets using a specific protocol until the attempt is successful, or until the end of the communication time.  If the application cannot login, the send/receive packet time is doubled when the communication time is doubled.

In this screen, you can change the initial send/receive packet time from its default value of 1 second.


Advanced Settings for NetBIOS

The Advanced Settings for NetBIOS screen contains the following options:

Timeout Length

The timeout length is the amount of time (in seconds) a protected application attempts to perform a NetHASP LOGIN.

The protected application attempts to login using all the protocols you specified in the Communication Protocols screen until it succeeds.  The application first tries to login using IPX, then TCP/IP, and then NetBIOS (depending on your selection of protocols).

By default, the protected application tries to login for a communication time of 2 seconds with each protocol.  If the login fails with each of the selected protocols, the protected application tries again, doubling the communication time to 4 seconds per protocol.  If login fails again with each of the selected protocols, the communication time is doubled once again to 8 seconds.  If the application still cannot perform a NetHASP LOGIN, it returns an error.

In this screen, you can change the initial communication time from its default value of 2 seconds.

You can also change the amount of time the protected application attempts to send or receive a packet.  The application attempts to send or receive packets using a specific protocol until the attempt is successful, or until the end of the communication time.  If the application cannot login, the send/receive packet time is doubled when the communication time is doubled.

In this screen, you can change the initial send/receive packet time from its default value of 1 second.


Advanced Settings for TCP/IP

The Advanced Settings for IPX screen contains the following options:

TCP/IP Port Number

Enter a port number which the client uses to search for the NetHASP License Manager.  The default port number is 475.

NetHASP LM Logical Name(s)

The NetHASP License Manager Logical Name is used to direct the client to login to a particular License Manager.  You can direct a client to search for a maximum of 6 License Managers.  Enter the License Manager name (up to 7 characters), and click Add.  To remove a License Manager from the list, select it and click Remove.

Timeout Length

The timeout length is the amount of time (in seconds) a protected application attempts to perform a NetHASP LOGIN.

The protected application attempts to login using all the protocols you specified in the Communication Protocols screen until it succeeds.  The application first tries to login using IPX, then TCP/IP, and then NetBIOS (depending on your selection of protocols).

By default, the protected application tries to login for a communication time of 2 seconds with each protocol.  If the login fails with each of the selected protocols, the protected application tries again, doubling the communication time to 4 seconds per protocol.  If login fails again with each of the selected protocols, the communication time is doubled once again to 8 seconds.  If the application still cannot perform a NetHASP LOGIN, it returns an error.

In this screen, you can change the initial communication time from its default value of 2 seconds.

You can also change the amount of time the protected application attempts to send or receive a packet.  The application attempts to send or receive packets using a specific protocol until the attempt is successful, or until the end of the communication time.  If the application cannot login, the send/receive packet time is doubled when the communication time is doubled.

In this screen, you can change the initial send/receive packet time from its default value of 1 second.


Contents

Wizard Screens

What is the NetHASP Configuration File Wizard?

NetHASP Configuration Filename

Network Communication Protocols

IPX Protocol Settings

NetBIOS Protocol Settings

TCP/IP Protocol Settings

Load NetHASP Test Utility


IPX Protocol Settings

NetHASP clients under IPX supports the following search mechanisms:

Bindery	A database in which the License Manager advertises itself, and in which the NetHASP client searches for it.

Broadcast	Instructs the NetHASP client to broadcast while the License Manager listens.

NetHASP Address File	Instructs the client to use an address file to search for the License Manager.

You can select any one of the three advertising mechanisms individually, or choose both IPX with Bindery and IPX Broadcast together.  When you use an IP Address file, you cannot select IPX with Bindery or IPX Broadcast.

By default, the IPX Broadcast mechanism is enabled, Bindery is disabled, and no address file is used.

To select a mechanism, click the check box next to it.  When you work with the IPX Address File mechanism, you can specify the path of the address file, or leave it blank to use the default path.

Click Advanced to set additional IPX options.

Click Next to advance to the following screen.

See Also	Advanced Settings for IPX


Load NetHASP Test Utility

You can test the configuration file you create/edit by running the NetHASP test utility.  The test utility performs routine network functions using the generated configuration file.

The test utility runs from the same directory as the NetHASP Configuration File Wizard.  By default, the generated configuration file is located in the same directory. The test utility searches for the configuration 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.	Protected executable file directory

4.	Current directory

5.	Windows directory

6.	Path

Make sure that the configuration file is in one of these locations, so that the test utility can find it and test accordingly.

To load the utility, click the box next to the type of application.  If you do not want to load a utility, click Do not load a utility.

Click Finish to generate the new/modified configuration file.


NetBIOS Protocol Settings

By default, the NetHASP client looks for the License Manager registered under the name “AladinHaspV012.0”.  You can change the name by entering a new name up to 8 characters in the field provided.  If you change the name, make sure to load the License Manager with the new name.

By default, Win32 applications search for a NetHASP License Manager on all detected lana numbers (communication channels).  You can instruct the NetHASP client to search using a specific lana number.  Type a number from 0 to 255 in the LAN Adapter Number field.

Click Advanced to set additional IPX options.

Click Next to advance to the following screen.

See Also 	Advanced Settings for NetBIOS


NetHASP Configuration Filename

When you create or edit your NetHASP configuration, you must specify the path of the configuration file.  The default name for the configuration file is nethasp.ini.

To Specify the NetHASP Configuration File Path:

1.	Type the name of the NetHASP configuration file which you want to create/edit, or click Browse to select it.

Note that the file must have an .ini extension.  If the file already exists, its contents are displayed.

2.	Click Next to continue.

The Wizard either creates a new file, or opens an existing file for editing.

3.	Click OK to confirm.

When you have finished editing the NetHASP configuration file, make sure to copy it to a place accessible by the protected application.  The application searches for the configuration 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.	Protected executable file directory

4.	Current directory

5.	Windows directory

6.	Path

Later in this wizard, you can load a utility to test the functioning of your configuration file.  If you load a test utility, make sure that the configuration file is in one of the above locations, so that the utility can find the configuration file and test it accordingly.


Network Communication Protocols

NetHASP clients and License Managers supports the following network protocols:

IPX

NetBIOS

TCP/IP

Select one, two, or all three of the protocols to include in your NetHASP configuration file.  If you select more than one, the NetHASP client performs a search for a protocol in a specific order, which cannot be changed.  The client searches first for IPX, then TCP/IP, and finally NetBIOS.

In the screens which follow, you specify settings for each protocol you select.

Click Advanced to set additional network protocol options.

Click Next to advance to the following screen.

See Also	Advanced Settings for All Protocols


TCP/IP Protocol Settings

When you use TCP/IP, there are three options when you search for the NetHASP License Manager:

UDP Broadcast

UDP

TCP

UDP Broadcast

By default, the client uses the UDP Broadcast mechanism with the TCP/IP protocol to search for the NetHASP License Manager.  When you use this setting, NetHASP clients cannot access NetHASP License Managers located on other segments or on the Internet.

To Use UDP Broadcast:

1.	Select UDP from the Mode list

2.	Click Use UDP Broadcast, or press control

UDP and TCP

When you work in UDP or TCP mode, the NetHASP client searches for a NetHASP License Manager with specified IP addresses or host names.  In these modes, the NetHASP can cross segments.

To Use UDP or TCP:

1.	Select UDP or TCP from the Mode list.

2.	Specify the IP Address(es) and/or host name(s) in the field provided.

3.	Click Add to enter the address/host name.  To remove an address/host name, select it and click Remove.

Click Advanced to set additional TCP/IP options.

Click Next to advance to the following screen.

See Also 	Advanced Settings for TCP/IP


What is the NetHASP Configuration File Wizard?

The NetHASP Configuration File Wizard is designed to help you create or edit the NetHASP configuration file quickly and easily.  The NetHASP configuration file is a file in which you can fine-tune the NetHASP settings for your protected application.

The NetHASP Configuration File Wizard lets you indicate which protocols you are using, and specify new settings for each protocol.  You can go back and reedit a previous screen at any point in the Wizard, by clicking Back.  To continue on to the following screen, click Next.  If you want to exit the Wizard, click Cancel.