FNP standard and TOKEN license security FAQs

Q: Can I install and run two or more FNP servers from different vendors at the same time on the same computer?

A: Yes, the same computer can host two or more copies of FNP servers, each from a different vendor. However, we highly recommends that all the servers be installed into different locations on the hard drive so that they do not interfere with one another.

Q: Can I install and run two or more FNP servers from AVEVA at the same time on the same computer?

A: The same computer can host two or more copies of FNP servers. However, only one version can be active at a time. For example, you can install IPASSI FNP 11.14 and 11.16 servers in different locations on the same computer, but you can run only one of them at a time.

Q: Can the IPASSI FNP License Server manage both standard FNP standard licenses and TOKEN licenses?

A: Yes, the FNP License Server can handle both types of licenses at the same time.

Q: How can I allow application computers to have access to the FNP License Server while the firewall on the license server computer is active?

A: The IPASSI FNP License Server install program, by default, makes the IPASSI.exe and lmgrd.exe exceptions to the system firewall, and that should allow applications on other machines to access the IPASSI license server for licensing needs.

Q: How do I prevent users on other computers from shutting down the FNP License Server?

A: To deny users on other computers the ability to shut down the FNP License Server, follow these steps:

1. Launch the LMTOOLS utility.

2. Select the Start/Stop/Reread tab.

3. Select the FNP License Server.

4. Stop the server.

5. Click the Edit Advanced settings button.

   

6. Check the Restrict lmdown to work only from node where lmgrd is running check box, and then click the Save Advanced settings button to save the change.

   

7. Click the Start Server button.

   With these settings, only users on this computer can shut down the FNP license server while users on other computers do not have the capability.

Q: How do I find the system information about the FNP license server computer?

A: The System Settings tab on FNP utility program lmtools.exe shows the computer system information, including the host ID and the Ethernet address. Exploring server system information shows an example of lmtools.exe System Settings tab display.

The second item on the SERVER line in your license file must be the same as the value in the Computer/Hostname field or the IP Address field of the System Settings tab.

Q: How can I speed up the initial connection between the application and the FNP license server?

A: If the FNP license server does not use the default lmgrd port (27000), explicitly specifying the port in both the license server and the application may speed up their initial connection.

On the server computer, follow the steps described in Configure and Install the Temporary License File to set the port numbers in the FNP license file.

On the application computer, the user edits the IPASSI_LICENSE_FILE environment variable to include the LMGRD port number in its value. Example: 30000@FNPSERVER. That way the Client computers now know exactly which port on the Server computer to use when trying to connect to the FNP License Server.

Q: How can I set a longer time for the initial connection attempt over a slow wide-area network?

A: This is can be accomplished on the application computer by setting the environment variable FLEXLM_TIMEOUT. This variable determines the amount of time a FNP-licensed application uses when it tries to connect to a license server. Possible settings range from 0 through 2147483647 microseconds. The user can set the environment variable to a value larger than the default setting of 100000 microseconds.

Q: When I request help, what information should I have ready to give Technical Support?

A: For fast support, you should provide the following:

• A screenshot of any FNP or TOKEN licensing security error message that the application displays

• The FNP license file ipassi.lic.

• The FNP License Server log file ipassi.log.