Client connections fail with license server name is not resolvable on client
In 11.17.2, the license server name returned to the client from lmgrd appears to be used by the client for communications to the license server regardless of the name specified in the client license environment variables.
This causes a problem when the client is on a different subnet and is connected by network tunneling software. The license server FQDN for the client is different from the FQDN specified in the license file on the license server.
Is there a way to disable the client from using the FQDN returned from the license server and use the settings of the flexlm environment variable on the client?
Depending on your FQDN , you might have a look at the attribute "LM_A_USE_FQDN" and see if it helps in your use case . Apart from this below is the order ,of searching for a license .
A FlexEnabled application looks for a license file as follows: 1. When the VENDOR_LICENSE_FILE environment variable has been set for the publisher of the application, then items in the license search path set in this environment variable are searched in order. 2. The items in a license search path set in the LM_LICENSE_FILE environment variable are searched in order. 3. When any license file specified in a license search path contains a USE_SERVER line, then a license is requested from the license server specified in the SERVER line. Any FEATURE and INCREMENT lines entries after the USE_SERVER line in the license file are ignored. 4. When the environment variables are not set and the FlexEnabled application does not specify the location of the license, then default location are used .
You can always node lock the server to an IP Address, hostname or hostid .
