hayuqcom asked a question.
We are trying to establish a FlexNet floating license server for an engineering tool that our team uses: PTC windchill risk and reliability. The server installation seems to be fine, but client machines are not able to access the server. Based on experience with other SWs, we are aware that our IT does not allow communication among computers inside our intranet (not sure why), we need to submit exception request to allow it case-by-case. During the license server configuration, we defined its communication port number, but IT still asks which program in the server computer needs to be allowed to communicate through this port. Without knowing such details, we provided the path of lmadmin.exe. However, after this exception request was approved and implemented, the license server still does not work. Can someone here tell whether lmadmin.exe is the right program that need to access TCP/IP port, and whether any other programs need accessibility to port as well? Thanks!
Hi @hayuqcom thank you for raising this query. Have you been able to establish a connection with the client, or are you still exploring a solution? If the client and server are located in different networks and an external firewall is involved, please confirm.
If so, kindly ensure that the ports for both are fixed in the license file. if not, then it will use the dynamic port for lmgrd
and the vendor daemon every restart.
After setting the static port, request your firewall team to allow inbound and outbound traffic for both ports. This configuration should resolve the issue.
I am still struggling for the issue. Both client and sever are in the same network, but there is probably some configuration settings blocking them from communication, due to company IT policy, therefor I need to know which program is communicating between server and client for FlexNet license management.
Any clue is appreciated. Thanks!
BR, Hao
Hi @hayuqcom
Steps to Allow lmgrd.exe and <vendordeamon>.exe Through the Windows Firewall
If the client application fails with a FlexNet -16 error or any other error you are getting it?
The firewall restrictions are suspected to be the cause, add exceptions for the license manager daemons to the Windows Firewall. Here are the steps to add the applications to the Windows firewall.
1. Open Windows Defender Firewall with Advanced Security
This advanced settings screen for the firewall is the best way to add specific application exceptions.
- Click the Start button or press the Windows key
- Type wf.msc and press Enter
Create Inbound Rules for the Applications
These rules will allow incoming connections to the license manager executables.
For lmgrd.exe:
- In the left pane, click Inbound Rules
- In the right pane (Actions), click New Rule to open the New Inbound Rule Wizard
- On the Rule Type screen, select Program and click Next
- On the Program screen, click Browse
- Navigate to where lmgrd is and then select lmgrd.exe. Click Open
- Click Next
- On the Action screen, make sure Allow the connection is selected and click Next
- On the Profile screen, ensure all options (Domain, Private, and Public) are checked and click Next
- On the Name screen, enter a descriptive name, like License Manager (lmgrd), and click Finish
For <vendordeamon>.exe: This is your <application>.exe
- In the right pane (Actions), click New Rule again
- On the Rule Type screen, select Program and click Next
- On the Program screen, click Browse
- Navigate to licensemanager and select <application>.exe, for example, ptc.exe. Click Open
- Click Next
- On the Action screen, make sure Allow the connection is selected and click Next
- On the Profile screen, ensure all options (Domain, Private, and Public) are checked and click Next
- On the Name screen, enter a descriptive name, like Vendor Daemon (ptc), and click Finish
3. Verify and Test the New Rules
After creating both rules, they should appear in the Inbound Rules list. The status for both rules should be Enabled with a green checkmark. Attempt to run the client application again to test the connection. This approach of creating specific rules for each executable is more robust than just opening the ports and should resolve the issue with the retramissions failing the client connection.
Let me know more error details if the above information is not helping to fix thei ssue.