Forcing Matlab to reconnect to the license server?

I access Matlab with an institutional license over a VPN and occasionally when the network flickers out I will get the message:

"MATLAB has lost its connection to the license server.

MATLAB will make 10 more reconnection attempt(s) and then exit. Any unsaved changes will be lost."

This of course counts down until it reaches 0 and then I have to quit and restart Matlab, which is a non-ideal solution because it involves reloading large quantities of data. My question is whether I can somehow force Matlab to recognize that the network is up again and the license server is reachable, stopping this inevitable march toward a restart. Are there any ideas for ways that this could be done? Currently I'm on Mac 10.14.6, but this has happened many times in the past also.

[Mark Ducey]

I wish I could answer this... same issue. From the related posts I recognize that the current licensing software employed by MathWorks seems to impose this limitation, but it's a major hassle for users who work with unreliable networks, who need to change physical work locations, or who occasionally need to work without connectivity. The lack of an answer from anyone at Mathworks to this and several of the related posts is disappointing, even if the answer is "fixing this is beyond our technical capability."

[Maggie]

I also have this problem.

[Walter Roberson]

@Mark Ducey

As far as I can tell, the two largest commercial licensing systems are:

• Microsoft
• Flexera

I have never seen Microsoft licensing used for third-party programs (other than those sold through the Microsoft store). Maybe it happens and I have just never seen it. Microsoft licensing does not allow per-feature licensing (as-far as I can tell) unless you get into Client Access Licenses (CALs), and it's all a headache... you pretty much have to run Microsoft Active Directory services as far as I can see.

Flexera is the current name of the company that does the FlexLM licensing system, which is the system that Mathworks uses -- as does Adobe, Maplesoft (Waterloo Maple), Wolfram (Mathematica), MathCAD, and many others. Flexera is certainly not without its drawbacks, with complications due to trying to accomodate lots of different licensing models. But it is what lots of major companies use if they do not build their own license system.

Getting Flexera to improve technical underpinnings is... challenging.

So... realistically, in order for Mathworks to fix this problem, they would have to implement their own licensing system. (I do not know how much they would be able to leverage the work already done for OpenLM, the more "open" work-alike replacement for Flexera)