Select when the new rule should be applied using the checkboxes (we recommend applying the rule at all times but you can modify this as required) and click Next.Select Allow the connection and click Next.Select TCP and Specific local ports, enter the port number from the HOST/SERVER line of the license, in the field provided (e.g.Select the Port radio button and then click Next.From the Windows Start menu, click Control Panel > System and Security > Windows Firewall and then click on the Advanced Settings link on the left hand side.Launch the Foundry Licensing Utility (FLU), click on License Server then Control Server, then Stop and Start the License Server.Click Next and enter a meaningful name for the rule, such as RLM_SERVER and then click Finish to complete the process.Domain, Private, and Public in the example below. Select all the checkboxes that apply to the rule.Click Allow the connection and then click Next.Browse to the location of the RLM server:.Click on the Change Settings > Allow another app link on the right hand side.Select Allow an app through the firewall.From the Windows Start menu, click Windows Security > Firewall and network connection.Select This program path and then browse to the location of the RLM server:Ĭ:\Program Files\The Foundry\LicensingTools8.0\bin\RLM Add.Select Inbound Rules in the left-hand panel and click New Rule.From the Windows Start menu, click Control Panel > System and Security > Windows Firewall and then click on the Advanced Settings link on the left hand side.The Program Exceptions is the easiest method to turn on. There are two firewall exception methods on Windows, Program Exceptions and Port Exceptions. You can then lock these changes by clicking on the Lock icon on the bottom left of the System Preferences window.Navigate to "/Applications/TheFoundry/LicensingTools8.0/bin/RLM" then select "rlm.foundry" and click Add.Under the list of incoming connections, click on the + (plus) button to add a program.You may need to click the lock icon at the bottom-left to enable changes Go to the Firewall tab and click the Firewall Options button.Open your System Preferences and click on Security & Privacy.The exact steps will depend upon the version of OSX that you're running, but they should be like the following. You can do this by running the following terminal commands as root or with sudo.Īfter you've set the ports for the server you can then open them on your firewall settings. NOTE: You'll need to fully restart the license server(s) after adding these ports for the changes to take effect. If you are opening ports on the firewall then you need to set a dedicated port for the ISV, instructions on how to do this are available in: Q100374: How to make the RLM server use a dedicated ISV port The port the ISV runs on changes randomly whenever the server restarts unless it is set in the license file. If you are opening ports on your firewall you will need to open two for the RLM server - one for the main port that is specific on the HOST line of the license (default value of 4101) and one for the ISV vendor daemon part of the server. usr/local/foundry/LicensingTools8.0/bin/RLM/ If you're opening the firewall to a specific program, the RLM Server program you need to specify is "rlm.foundry" from the following directory: Please consult your system administrator for the exact steps but the following information will be useful. If you have an older version installed then you need to replace "LicensingTools8.0" with the version you are using, e.g. NOTE: The paths below are for the server tools installed by Foundry Licensing Utility 8. The exact steps that you need to take will depend upon the OS of your license server. In order to fix this, you need will need to change your firewall settings to allow the license server software to communicate through the firewall. If you have installed your floating licenses, installed and started the server tools, pointed the other machines on your network to your server correctly, but you still cannot get a license then a firewall on the server could be blocking the license requests.Ī typical licensing error message caused by a firewall is: => nuke_i : Communications error with license server (-17) It is possible to make the license server work through the firewall by adding exceptions to the firewall settings, either for the license server executable or by opening the ports the license server uses. If you have a firewall running on your license server machine then it may block license requests from other machines on the same network.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |