Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
TopLicPage
TopLicPage

...

Once the Sentinel run-time driver is installed and the network license is connected, CHARON-AXP can be started on any appropriate host on the LAN network segment.

Info

The Network license key contains a specific parameter to restrict the number of hosts allowed to run CHARON-AXP at the same time. Together with a parameter defining the number of CHARON-AXP instances that may run at the same time, the network license Note that the following operations have to be performed on installation phase for network licenses:

  • On server side (where network license will reside): open port 1947 for both TCP and UDP
  • On clients side: open UDP ports 30000-65535
  • Both on server and client sides: setup default gateway

Please consult with your Windows User's Guide on details.

If stricter firewall rules are required, it is possible to open the ports 30000-65535 and 1947 only for the "Sentinel HASP License Manager" (hasplms.exe) service (it will be installed by CHARON-AXP ).

Info

The Network license key contains a specific parameter to restrict the number of hosts allowed to run CHARON-AXP at the same time. Together with a parameter defining the number of CHARON-AXP instances that may run at the same time, the network license sets the total number of running CHARON-AXP instances on the allowed number of hosts.

...

Warning

Installation of Sentinel run-time (driver) described below is needed for Sentinel HASP keys (both regular and network), Sentinel HL keys (both regular and network), Sentinel HL keys (both regular and network) without "driverless" mode enabled, Sentinel HL Network keys (red dongles) - is they are going to be used network wide and Sentinel Software Licenses (SL).

Please skip installation of Sentinel run-time (driver) if you use locally connected Sentinel HL keys in "driverless" mode or going to use Sentinel HL Network key in "driverless" mode from some other host on local network. Just connect the license key to the host and proceed with collecting "*.c2v" file (see below) if the license inside your Sentinel HL key must be updated.

Installation of a CHARON-AXP regular or network licenses consists of:

  1. Installation of the Sentinel run-time environment on the CHARON-AXP host (regular and network keys) or on the host that will distribute CHARON-AXP licenses over a local network segment (network key only). The Sentinel software is installed automatically by CHARON-AXP for Windows.
  2. Physical connection of the HASP license dongle to the CHARON-AXP host or to the host distributing the CHARON-AXP license over the local network segment.
  3. Collecting system fingerprint (*.c2v file), sending it to STROMASYS and applying update (*.v2c file) in case of software license. See the details below.
When manual installation of Sentinel run-time is required (in the case of the network license server that does not have CHARON-AXP installed):

...

Issue:

...> haspdinst.exe -fr -kp -nomsg...> haspdinst.exe -install -cm

...

and network) without "driverless" mode enabled, Sentinel HL Network keys (red dongles) - is they are going to be used network wide and Sentinel Software Licenses (SL).

Please skip installation of Sentinel run-time (driver) if you use locally connected Sentinel HL keys in "driverless" mode or going to use Sentinel HL Network key in "driverless" mode from some other host on local network. Just connect the license key to the host and proceed with collecting "*.c2v" file (see below) if the license inside your Sentinel HL key must be updated.

Installation of a CHARON-AXP regular or network licenses consists of:

  1. Installation of the Sentinel run-time environment on the CHARON-AXP host (regular and network keys) or on the host that will distribute CHARON-AXP licenses over a local network segment (network key only). The Sentinel software is installed automatically by CHARON-AXP for Windows.
  2. Physical connection of the HASP license dongle to the CHARON-AXP host or to the host distributing the CHARON-AXP license over the local network segment.
  3. Collecting system fingerprint (*.c2v file), sending it to STROMASYS and applying update (*.v2c file) in case of software license. See the details below.
When manual installation of Sentinel run-time is required (in the case of the network license server that does not have CHARON-AXP installed):
  1. Open the CHARON-AXP kit folder
  2. Switch to the "hasp_install" subfolder
  3. Unzip the archive located in this folder
  4. Open "cmd.exe" and switch to the folder where the files were unzipped
  5. Issue:

    ...> haspdinst.exe -fr -kp -nomsg...> haspdinst.exe -install -cm
    Info

    Sentinel HL keys can be provided both in "driverless" and regular modes. To switch the Sentinel HL key to "driverless" mode it is required to install Sentinel run-time first as described above and apply a special *.v2c file that switches the key to "driverless" mode. Once it is done the Sentinel run-time can be deinstalled.

    Info

    Note that the following operations have to be performed on installation phase for network licenses:

    • On server side (where network license will reside): open port 1947 for both TCP and UDP
    • On clients side: open UDP ports 30000-65535
    • Both on server and client sides: setup default gateway

    Please consult with your Windows User's Guide on details.

    If stricter firewall rules are required, it is possible to open the ports 30000-65535 and 1947 only for the "Sentinel HASP License Manager" (hasplms.exe) service (it will be installed by CHARON-AXP ).

...

Disable remote keys access 

A helpful feature of Sentinel Admin Control Center is the ability to disable access to remote keys. If the network key is installed locally, access to the key from remote hosts can be disabled. The following examples demonstrate how this can be done.

To disable access to remote keys switch to the "Access to Remote License Managers" tab and uncheck the "Allow Access to Remote Licenses" checkbox. Then press the "Submit" button to apply this change:

...