OpenLM Agent connectivity issues can manifest in many ways, but are summarized as general Agent malfunction. Such connectivity issues may be caused by the following reasons:
1. Incorrect server name or address
2. Firewall blocks the OpenLM Server or the Agent port.
3. A proxy server blocks the Agent requests.
4. .NET Framework not installed on the OpenLM Agent machine
If you encounter connectivity issues, Please act according to the following checklist:
1. Make sure that .NET Framework not installed on the OpenLM Agent machine
2. Make sure that the server name and address are correct.
3. Make sure that the port is open:
3a. Try disabling the firewall temporarily.
3b. Enter “Control Panel” → “System and Security” → “Windows Firewall” → “Advanced settings”.
3c. If the port isn’t defined under the “‘Inbound Rules” open the port by adding a New Rule using the “New Rule” button located on the lower right side of the screen as depicted below:
If connectivity issues persist, and a Proxy Server is configured on your machine, ensure that it is not blocking the OpenLM server; Open the OpenLM Agent Configuration window and uncheck the “Use local computer’s proxy settings” box as depicted below:
|Title||Troubleshoot 03.003: Agent fails to connect to the OpenLM Server|
|Category||Permissions and Roles.|
|Date||March 12, 2013|
|Applies to license managers||FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS|
|Applies to license model||Floating licenses, Network licenses, Concurrent licenses|
|Symptoms||Can not set a connection between OpenLM Server and OpenLM Agent.|
|Observed during investigation||No license usage presented in OpenLM Agent,
“Check connectivity…” button yields an error,
Other general Agent malfunctions
|Trouble shoot process|