|
|
GLD Network Dongle (Hardware Key) Instructions
This page contains the information needed to activate and install the network version of GLDTM using the network license dongle. This information is directed towards IT Managers/Network Administrators.
Note 1: Only the
commercial version of GLDs is available for the network environment.
Note 2: Accessing a client machine (with standalone GLDs installed) via a remote desktop
session
MAY NOT WORK.
The HASP License Manager and DRM features of Windows will prevent
this type
of access. This is NOT an issue with GLDs. The Network License version
of GLDs
does support
access via remote desktop or other types of remote access.
Please choose your version of GLD:
Older Versions of GLD - No Longer Supported
Network Dongle Instructions for GLD2016 and Later
GLDs Network Dongle instructions are similar to earlier versions except that the dongle type is intellegent and is different in appearance. Network License keys are Red. Also, the new Network Dongle is aware of the network time and date and it is necessary that both the workstation and server are observing the network time. See examples of key images
Are you looking for the License Manager for your server?
For convenience, a direct link to the HASP run time installer: download
from
here.
Alternately, for the a specific Thales/Gemalto/SafeNet driver, you
could visit their site at
https://supportportal.gemalto.com and download their latest driver set.
Overview: For multi-license users, GLDTM uses a hardware network USB dongle that enables a number of workstations that are all connected to the same LAN/WAN to run up to the purchased number of licenses simultaneously. Instead of requiring one dongle per computer, a single network dongle is installed on any PC in the network. The computer that holds the license key is referred to as the server. This can be either a traditional server, virtual server, virtual PC or a standard PC attached to the network. Please follow these steps to get GLDTM up and running on your network:
Please Note: The network and standalone versions of GLD2016 and newer will NOT coexist on the same network. Due to the way that the HASP key system operates, having a standalone version detected on the network will prevent the network license from being issued correctly. This is a limitation of the licensing system and not a problem with GLD.
SERVER/KEY HOST:
- Install the license manager on your key host/server. It is not necessary to install the full GLDs installation if the key host is not being used as a workstation for GLDs.
- Insert your key into a USB port. The key host/server must be able to communicate with the key. Your key host may be physical or virtual but requires access to a physical USB port.
- Open a web browser on the "server" and type in the following URL :
http://localhost:1947
This address provides access to the license manager admin control center.
- The network key will have a red symbol and will show a vendor number 80625. Once you can demonstrate that the network key is visible to the license manager, you can proceed to the workstation setup.
WORSTATION INSTALLATION:
- Install the network edition of GLDTM on
all network-enabled target computers.
- GLDs network setup download
- Open a web browser on the workstation and type in the following URL :
http://localhost:1947
This address provides access to the license manager admin control center.
- In the control center, in the leftmost column find the CONFIGURATION
option and click it.
- Select the ACCESS TO REMOTE LICENSE MANAGERS and check all options
(allow access to remote licenses, broadcast search for remote licenses and
aggressive search for remote licenses)are checked.
- You may need to add an entry in the open text box with the IP address of
the key host, especially when hopping subnets or using a VPN. This is
done on the workstation onlyu and will only need to be done once.
- Click the SUBMIT button
- Repeat the configuration on all WAN PCs that will be accessing the
license key.
- Make sure that the firewall is configured for inbound and outbound
traffic for TCP port1947. This should be done automatically
during setup but should be checked in the event of difficulties. Some
antivirus programs also have firewall features and should be similarly
checked to allow traffic on port 1947.
- When you start GLDTM and it logs into
the network, the splash screen will indicate “logged into network”. If GLDTM
does not show this screen and closes automatically it means either a) all
network licenses are currently in use or b) your network license
configuration needs to be double checked.
- From within the license manager admin control center (
http://localhost:1947) the
network administrator can select the HASP KEYS option in the left column to
see current license status.
- If accesing the license key from a different subnet, it is necessary to
make certain that the key can be seen from the remote location. Your
VPN / Firewall / Routers must be configured to allow traffic on Port
1947.
Additionally, please make sure that you add an entry to the workstation that
allows the HASP software to see the remote server. this can be done
from the license manager admin control center on each workstation:
- http://localhost:1947
- Choose Configuration --> Access to Remote License Managers
- In the box to "specify search parameters": Please enter the unique IP address of
the machine that is acting as the "server".
- Click submit
Note: If you can't ping the server from the remote location, it is not likely that HASP key software will be able to get a license. With all of the security that is in place in many domain environments, it will be necessary for your IT Professional to configure the infrastructure to allow the appropriate traffic between the locations. - Unsure if you have the right HASP Key/Dongle? Photos here
- Questions? Contact our
Support Department
-
The license manager product is purchased from a third party.
The current name of the security solutions company is "Thales". Here are some links to their support center. The product as supplied by GroundLoopDesign should work without any modification to the default settings except as noted. Support for any other configuration will need to come directly from the security vendor.
Thales / Gemalto / Safenet Technical Support Websitehttps://supportportal.gemalto.com/csm/
Phone: 1-410-931-7520 International
The Ground Loop Design vendor number for Thales/Gemalto/Safenet is: 80625
The Thales/Gemalto/Safenet product for network installations is: HASP HL Net 10
Note: Versions below are outdated. Self support only.
GLD2012 / GLD2014 Network Dongle Instructions
GLD 2012 Network Dongle instructions are essentially unchanged compared to GLD2014 and are repeated here with the relevant download links for the 2012 version. The key that is used is an obsolete key style and we no longer can program or support it.
Overview: For multi-license users, GLDTM uses a hardware network USB dongle that enables a number of workstations that are all connected to the same LAN/WAN to run up to the purchased number of licenses simultaneously. Instead of requiring one dongle per computer, a single network dongle is installed on any PC in the network. The computer that holds the license key is referred to as the server. This can be either a traditional server or a standard PC attached to the network. Please follow these steps to get GLDTM up and running on your network:
Note: Previous standalone or beta versions of GLD2014 must be uninstalled prior to installing the GLD2014 Network version. This applies to all workstations that will be used to run the network version client.
Please Note: The network and standalone versions of GLD2014 will NOT coexist on the same network. Due to the way that the HASP key system operates, having a standalone version detected on the network will prevent the network license from being issued correctly. This is a limitation of the licensing system and not a problem with GLD.
- Install the network edition of GLDTM on all network-enabled target computers.
- Attach the license key to the “server”. This may be any windows machine on the network, including workstations or servers.
- Open a web browser on the "server" and type in the following URL :
http://localhost:1947
This address provides access to the license manager admin control center.
- In the control center, in the leftmost column find the CONFIGURATION
option and click it.
- Select the ACCESS TO REMOTE LICENSE MANAGERS and check all three options
(allow access to remote licenses, broadcast search for remote licenses and
aggressive search for remote licenses)
- Click the SUBMIT button
- Next, select ACCESS FROM REMOTE CLIENTS and check “allow access from
remote clients".
- Click the SUBMIT button
- Restart the HASP License Manager by going to the control panel →
administrative tools → services, finding the HASP license manager, and then
restarting it.
- Repeat the configuration on all WAN PCs that will be accessing the
license key.
- Make sure that the firewall is configured for inbound and outbound
traffic for UDP port 475. This should be done automatically
during setup but should be checked in the event of difficulties. Some
antivirus programs also have firewall features and should be similarly
checked to allow traffic on port 475.
- When you start GLDTM and it logs into
the network, the splash screen will indicate “logged into network”. If GLDTM
does not show this screen and closes automatically it means either a) all
network licenses are currently in use or b) your network license
configuration needs to be double checked.
- From within the license manager admin control center (
http://localhost:1947) the
network administrator can select the HASP KEYS option in the left column to
see current license status.
- If accesing the license key from a different subnet, it is necessary to
make certain that the key can be seen from the remote location. Your
VPN / Firewall / Routers must be configured to allow traffic on Port 1947.
Additionally, please make sure that you add an entry to the workstation that
allows the HASP software to see the remote server. this can be done
from the license manager admin control center on each workstation:
- http://localhost:1947
- Choose Configuration --> Access to Remote License Managers
- In the box to "specify search parameters": Please enter the unique IP address of
the machine that is acting as the "server".
- Click submit
Note: If you can't ping the server from the remote location, it is not likely that HASP key software will be able to get a license. With all of the security that is in place in many domain environments, it will be necessary for your IT Professional to configure the infrastructure to allow the appropriate traffic between the locations. - Additional Troubleshooting suggestions here.
- Unsure if you have the right HASP Key/Dongle? Photos here
Note: Versions below are outdated. Self support only.
GLD 2009 / 2010 Network Dongle Instructions
Overview: The last several versions of GLD have many similarities in terms of the licensing configuration. For multi-license users, GLDTM uses a hardware network USB dongle that enables a number of workstations that are all connected to the same LAN/WAN to run up to the purchased number of licenses simultaneously. Instead of requiring one dongle per computer, a single network dongle is installed on any PC in the network. The computer that holds the license key is referred to as the server. This can be either a traditional server or a standard PC attached to the network. Please follow these steps to get GLDTM up and running on your network:
Note: Previous standalone or beta versions of GLD2010 MUST be uninstalled prior to installing the GLD2010 Network version. This applies to all workstations that will be used to run the network version client.
- Install the network edition of GLDTM on all network-enabled target computers.
- Attach the license key to the “server”.
- Open a web browser on the server and type in the following URL :
http://localhost:1947
This address provides access to the license manager admin control center.
- In the control center, in the leftmost column find the CONFIGURATION
option and click it.
- Select the ACCESS TO REMOTE LICENSE MANAGERS and check all three options
(allow access to remote licenses, broadcast search for remote licenses and
aggressive search for remote licenses)
- Click the SUBMIT button
- Next, select ACCESS FROM REMOTE CLIENTS and check “allow access from
remote clients".
- Click the SUBMIT button
- Repeat the configuration on all WAN PCs that will be accessing the
license key.
- Make sure that the firewall is configured for inbound and outbound traffic for UDP port 1947. This should be done automatically during setup but should be checked in the event of difficulties. Some antivirus programs also have firewall features and should be similarly checked to allow traffic on port 1947.
- When you start GLDTM and it logs into
the network, the splash screen will indicate “logged into network”. If GLDTM
does not show this screen and closes automatically it means either a) all
network licenses are currently in use or b) your network license
configuration needs to be double checked.
- If problems persist, go to the ACCESS TO REMOTE LICENSE MANAGERS tab and under Specify Search Parameters, enter the server IP address and click SUBMIT.
- Additional Troubleshooting suggestions here.
- Unsure if you have the right HASP Key/Dongle?
Photos here
Note: Versions below are outdated. Self support only.
GLD Versions 5.x Network Dongle Instructions
Overview: For multi-license users, GLD uses a hardware network USB dongle that enables a number of workstations that are all connected to the same LAN/WAN to run up to the purchased number of licenses simultaneously. Instead of requiring one dongle per computer, a single network dongle is installed on any PC in the network. This computer is referred to as the server. Please follow these steps to get GLD up and running on your network:
- Install GLD on all network-enabled target computers.
- GLD 5.3 network setup download
- Designate one networked computer as your “server”
- Download GLDnetworkkit.zip onto your server.
- The download is available here.
This zip file contains the following files:
1) lmsetup.exe
2) aksmon32.exe
3) 4 nethasp zip files (for four network protocols)
-
Run lmsetup.exe to install the HASP DONGLE LICENSE MANAGER on the server. Note: set this up as a service. This program maintains communication links between the license dongle and the distributed GLD programs. After installation is complete, you can find the license manager service icon in the desktop system tray (usually in the lower right corner of the desktop). Click on it and make sure that your network protocol is “loaded."
-
Next, find the Nhsrv.ini file in the C:/Program Files/Aladdin/HASP LM folder on the server. This files allows the network administrator to specify which computers are served by the dongle server. Modify it as necessary with the IP addresses of the GLD-enabled computers that will be utilizing the network dongle.
-
Run aksmon32.exe to install the Monitor program. This program provides for centralized administration of the HASP License Manager application and the HASP dongle. You can use this Monitor program to check the status of the dongle as well as to keep track of how many concurrent GLD users there are at any given time.
-
GLD uses the nethasp.ini file to store information about your network and the location of the dongle server. Choose the nethasp zip file that matches your network needs and unzip it. Open the nethasp.ini file and customize it as necessary. For WAN deployments, configure the nethasp.ini file with the IP Address of the License Manager location and disable broadcast. Then, save the nethasp.ini file on the server in the Program Files/Gaia Geothermal/Ground Loop Design folder (the same folder that has the GLD executable). This nethasp.ini file should also be copied to the Program Files/Gaia Geothermal/Ground Loop Design folder on all PCs that have GLD. Doing so can eliminate network delays.
-
Make sure that the firewall is configured for inbound and outbound traffic for UDP port 475 and 1947.
-
Attach the dongle to the server and open GLD. You should see a “logged into network” message when you open the program