if you still face a problem accessing the Sentinel HL key after performing the 5 steps above, try the following workaround, documented in:
Accessing Sentinel License Manager Located on a Different Subnet
When a Windows application that is protected with Sentinel LDK v.6.0 or later is located on a different subnet than Sentinel License Manager and the Sentinel protection key, you must create a separate configuration file to enable the application to find the License Manager. Create a file called hasp_vendorID.ini, where vendorID is the Vendor ID associated with your Batch Code (for the DEMOMA Batch Code, use hasp_demo.ini). Place the file on the same machine as the protected application, in the directory described below.
| Type of application |
Directory |
|
Desktop |
%LocalAppData%/SafeNet Sentinel/Sentinel LDK/ |
|
Desktop |
%UserProfile%/Local Settings/Application Data/SafeNet Sentinel/Sentinel LDK/ |
|
Service
(LocalSystem) |
%windir%\SysWOW64\config\systemprofile\AppData\Local\SafeNet Sentinel\Sentinel LDK\ |
|
Service
(LocalSystem) |
%windir%\System32\config\systemprofile\AppData\Local\SafeNet Sentinel\Sentinel LDK\ |
|
Service (Network) |
%windir%\ServiceProfiles\NetworkService\AppData\Local\SafeNet Sentinel\Sentinel LDK\ |
Example
For a desktop application, for Vendor ID 37517 and a user named test1, create the following file:
- For Windows Vista or Windows 7:
%SystemDrive%\Users\test1\AppData\Local\SafeNet Sentinel\Sentinel LDK\hasp_37517.ini
- For Windows XP:
%SystemDrive%\Documents and Settings\test1\Local Settings\Application Data\SafeNet Sentinel\Sentinel LDK\hasp_37517.ini
A separate .ini file must be created on the machine for each user of the protected application.
The hasp_vendorID.ini file should contain the following line:
SERVERADDR = remoteServerAddress
where remoteServerAddress is the IP address or computer name of the remote machine that contains Sentinel License Manager and the protection key.
Regards,
Olivier