Network requirements for TAH concurrent license manager

Hello.

What are the network requirements for a TAH concurrent network license server? Specifically does the network license management daemon require access to the public internet? I have a license server on a private/RFC-1918 subnet, the logs of which indicate it is able to validate my current license and start successfully, yet when clients connect I'm seeing odd license server errors. When moved to a globally addressable IP clients are able to successfully checkout licenses.

Thank you, Justin

[Kojiro Saito]

Global IP address is not mandatory, but every client of your TAH licensed users can access to TAH license servers. So, every client machine must resolve the hostname of the license servers. What's the odd error you got?

[Justin Davis]

Thank you for the followup.

The client machine is on a public network. When the server is running on a private (non-routed) network, I get the following error when attempting to checkout a license:

License checkout failed.
License Manager Error -7
This version of MATLAB requires a newer version
  of the license manager.

Update the license manager software to the latest version.
Troubleshoot this issue by visiting:
http://www.mathworks.com/support/lme/R2017a/7

Diagnostic Information:
Feature: MATLAB
License path: 10280@myhostname
Licensing error: -7,10015.

Nothing is logged on the server when this happens. If I move the same server to a public network I am able to successfully checkout a license. The same behavior is exhibited with Matlab versions 2016b, 2017a and 2017b.

I am running lmgrd version v11.14.1.2 build 208719.

[Kojiro Saito]

Your cient can resolve the server hostname correctly both when the server is in the public network and private network?

In your client's terminal or command prompt, let's do

 ping myhostname -4

in both cases server's under public network and private network.

Also, how about specifying the server hostname by FQDN with domain name rather than just short hostname?

[Justin Davis]

Hi Kojiro.

I have verified that client server communications work via the server shortname, FQDN and explicit IP address. The error behavior is the same. I am leveraging the "search" domain attribute in my client's resolv.conf when using the server's shortname.

For testing I've also explicity defined the "myhostname" domain in my `/etc/hosts` file with identical results.

Thanks again, Justin

[Kojiro Saito]

You had better contact MathWorks's customer support team from the following link.

https://www.mathworks.com/support/contact_us.html