Specifications

Configuring the License Server Client
34
Chapter 2 - Configuring the License Server
Test the “Broadcast Method” of Locating a License Server
You can test the configuration using the following steps:
1. Verify the LSHOST and LSFORCEHOST environmental variables
aren’t set and there isn’t an LSHOST or lshost file in the same directory
as the protected application.
2. Run either the lswhere or WlmAdmin utilities on the client computer.
These utilities do a network broadcast for license servers and display a
list of all license servers that are visible from the client computer.
WlmAdmin also displays a list of licenses; you can check that list to
verify there is a server for the applications you want to run.
3. If all expected license servers are present, then the application will be
able to run using the broadcast method. Of course, one of the license
servers that is found must have a network license code that can be used
to authorize use of the client computer.
4. If you are not able to see a particular license server, you should verify the
network connection by using a network diagnostic program like ping.
You can make this check by providing either the network address as a
number (192.33.22.2) or as a name (license_host). If ping cannot find
the server, then you have a network configuration problem that must be
resolved before your SentinelLM-protected application can be used with
a network license.
Test the “Named License Server Method” of Locating a
License Server
You can test the configuration using the following steps:
1. Follow the steps given for the broadcast method until the client computer
is able to find each license server that you want. If you are using the
named license server method because the client computer and license
server aren’t on the same subnet, then you may want to skip right to the
last step and just use ping.