Question
We’ve installed the Network Licence Server, but our network doesn’t like the fact that the “ISV Server” is assigned a random port number each time it is started. Can we fix it to a static number?
Answer
Yes. With RLM v16.1 this only requires a small edit to your licence file, which can be made from within the RLM web interface, followed by a restart of the ISV server.
Log In to the Web Interface
- Open the web interface on the server at https://localhost:5054/ (note: https, not http). Your browser may warn that the connection is not private; this is because RLM uses a self-signed certificate, and it is safe to proceed.
- Log in. If this is the first time the web interface has been used, the default username and password are both
admin, and you will be prompted to set a new password.
Edit the ISV Line in Your Licence File
- On the home page, find the “limitstate” ISV server, click the hamburger ( ⋮ ) menu on the right of its row and select “View / Edit License(s)”.
- Find the line beginning
ISV limitstateand add the desired port number using theport=keyword, e.g.:
ISV limitstate port=12345
(12345 is illustrative; you can use any available port of your choosing, but it must be different from the HOST port (default 5053) and from the web interface port (default 5054).)
- Save the changes.
Restart the ISV Server
- Click the hamburger ( ⋮ ) menu for the “limitstate” ISV server again and select “Reread / Restart Server”.
- Check that the “limitstate” ISV server is running and is reporting port 12345.
Open the Port
- Ensure that port 12345 (as well as the HOST port, 5053 by default) is allowed through the firewall on the server machine and any network firewalls between the server and client machines.
Check Licences Are Served OK
- Open the LimitState software (RING, GEO etc.) on a client machine and check that a licence can be obtained from the server via:
- 5053@<your_server_name> (e.g. 5053@licserver)
- 5053@<your_server_ip> (e.g. 5053@10.11.12.13)
Clients always connect to the HOST port first, which then directs them to the ISV server on its (now fixed) port.
Troubleshooting
- If the web interface still reports the old port number, or licences cannot be checked out, restart the RLM service via the Windows Services dialog (services.msc > “RLM” > Stop, then Start). This clears any cached licence files and settings.
- If you are unable to save changes in the web interface, you can instead edit the licence file directly in a text editor (it is usually in the same folder as rlm.exe), then restart the RLM service as in step 10.
Note
The port for the host server itself can also be changed (5053 is used if nothing else is specified). To do this:
i) In step 4 above, also locate the HOST line:
HOST localhost <machine_id> 5053
ii) Change (or add) the port number at the end, e.g.:
HOST localhost <machine_id> 5432
iii) Save the changes, then restart the RLM service via the Windows Services dialog (as in step 10), since a change to the HOST port affects the main RLM server rather than just the ISV server. Ensure the new port is also open in the firewall, and that clients use it (e.g. 5432@<your_server_name>). Note that the web interface address stays at port 5054.