Ports and Protocols from the client to the License server

[sergio_v6]

[ FlexSim 21.2.4 ]

Hello.

I have a problem connecting from client side Flexsim to the license server. I have the client in a virtual machine which has restricted security (closed ports, disabled communication protocols, etc). I wanted to know, on the client side, what ports and communication protocols are used to reach the license server.

In the documentation (https://account.flexsim.com/ftp/FlexNetPublisher/downloads/FlexSimLicenseServer_Installation.pdf) I found that I need to have the following ports open:

• 26914 (lmgrd.exe)

• 56914 (flexsim.exe)

What other ports or protocols do I need to have enabled on the client side?

As a note, I have the firewall disabled and my license server is on a custom port (like [email protected])

Thanks

[Ben_WilsonADSK · Accepted solution]

Hi @Sergio V6 ,

There are two things you'll want to check:

1. licenses are properly being hosted on your license server
2. required communications are not blocked.

Let's go over tests for each of these in turn.

LICENSE SERVER CONFIGURED PROPERLY

You can test if your server is properly configured and hosting FlexSim licenses by installing an appropriate version of FlexSim simulation software directly on your license server. Use the Licensing a single-user client PC instructions on page 19 of our license server installation instructions to configure FlexSim to get a license from the local license server.

Use as your License Server Address <port>@127.0.0.1 where <port> should be the lmgrd port number. Our default license file uses 26914, but you may have chosen a different port number.

If a local-to-the-license-server FlexSim instance is able to properly get a license, then you've verified that your license server is properly hosting your FlexSim seats.

WORKING NETWORK COMMUNICATION

A FlexSim client instance must maintain a solid connection to the license server in order to obtain and keep a FlexSim seat. These connections happen over the lmgrd and vendor daemon ports. You can change our default ports (26914 and 56914) in the file flexsimLicenseFile.lic to be whatever available port numbers you like. After you change the license file, be sure to restart the service.

The communication between your license server and any client PCs happens across those two ports, so for licensing purposes, those are the only firewall exceptions you would need.

You can use the telnet test to determine if communication is working from your client PC to the license server across those two ports. The video at that link has some references to lmadmin, but our recommendation today is to use lmtools to host your FlexSim licenses. The important parts of that video are about testing connectivity using telnet.

Be sure to test both ports. If one or both ports times out, there is some issue connecting between the two machines that needs to be debugged by your network administrator to allow the communication to go through.

[sergio_v6]

Hi Ben.

I don't have access to the license server but i think is configured correctly, because we can connect from other clients (not VM).

About those ports (26914 and 56914) if our license server have another port (example 12345@licenseserver.mycompany.com), do we need to open the port 12345 also in the client side?

The cmd ping test passed, but the telnet failed, i will test it again after i have those ports open.

[Ben_WilsonADSK]

Every organization will have a unique networking situation, but typically you do not need to open any firewall exceptions on the client.

If you cannot telnet from the client to the server using the two ports (lmgrd and vendor daemon), that needs to be debugged by your networking admin. Once you can make those connections from client to server using telnet, FlexSim should also have no problem using those ports to obtain a license from your server.

Good luck!

[sergio_v6]

Good luck!

Thank Ben, I will need this!

[Ben_WilsonADSK]

Let us know if any new questions come up or if you need clarification on any points. For now, though, I can't think of anything else to share that would be helpful, or anything we can do from our end.

It seems to be in the hands of your network team at this point.

[lambert]

Hi, I am having the same problem.

I have setup the license server on an AWS EC2 instance.

When I run FlexSim from my personal PC, it manages to retrieve a license.

However, when I run FlexSim from an Amazon Workspace (corporate network), it fails to retrieve a license. Telnet test is unsuccessful, even with the firewall fully disabled for private and public networks.

Any support please?

Thank you

[Ben_WilsonADSK]

Hi @Lambert,

It might be interesting to see what is shown in your log files. Do you have access to the license server?

Please plan to schedule a live web meeting with your local FlexSim distributor. They will coordinate with someone from our team to help debug. We'll want to have access to view the screen both on your affected client PC and on your license server, so if you need to coordinate with a server admin or someone for access, please do so and schedule with that person and your local FlexSim distributor, who will coordinate to have someone from our team there.

Also, as a note, best practice is not to ask a new question as an "Answer" or comment on an old question, but to ask a new question. You can link back to the old question if it is helpful, but an old Q&A typically isn't the place to add more questions. Something for next time.

Thx

[Ben_WilsonADSK]

@Lambert,

I just noticed in your message that you said "Telnet test is unsuccessful". I misread that initially that Telnet worked.

If the Telnet test fails, that means there is a connectivity issue that a network admin on your side will need to resolve. Perhaps your work computer is filtering communications, or maybe the issue is on a network appliance between your PC and the license server.

Whatever the case, we will not be able to help debug issues at the network level. You DO need to have a successful Telnet test across both ports in order for licensing to work.

Please engage whoever you need internally to be able to make those network connections.

Thank you.