If the SIMetrix-SIMPLIS network license manager problem does not start correctly or does start correctly but does not check out licenses, then the most likely cause is that a firewall is blocking communication to it.
This page helps resolve these problems. The content of this page is targeted at Windows users but much is relevant to Linux as well.
"Thanks for the lightning fast reply and thank you very much for creating the best spice product on the market"
These problems are nearly always caused by a firewall. Firewalls block communication in selective ways in order to protect you from malicious traffic. Unfortunately a firewall will also block legitimate applications unless instructed not to.
Broadly there are three ways to fix this problem. Click on the links below for more information:
For maximum security some firewalls may allow you to combine 2 and 3 above.
The best way to test the result of any changes is to install SIMetrix and run it. Be aware that your firewall may require that SIMetrix itself is unblocked for network access. If so you should unblock Sim.exe.
Turning off the firewall altogetherWith some systems, a firewall may have been enabled by default but isn't actually necessary. A common network configuration is to use employ a firewall at the Internet gateway but to allow free network traffic inside the local area network. In such systems, simply switching off the firewall will be an easy, effective and safe solution. If relevant, you should consult your network administrator before doing this. |
Configure the firewall to allow the license manager processes unrestricted network accessMany firewalls allow you to unblock specific processes. If your firewall allows this (and we believe that most do) then we recommend this approach as it does not require any change in the license manager's configuration. You should unblock these processes: lmgrd.exe NEWTECH.exe pdt.exe (pdt.exe is used only for SIMPLIS licenses). Some firewalls provide some flexibility in the extent of the unblock. For example it may allow you to specify that the process be restricted to communication within the local area network. If so, you may find it necessary to allow full access (i.e. including the wider Internet) in order to get it to work even on the local machine. If this is the case, see the section below The Loopback IP Address |
Open the specific TCP ports that the license manager usesWith this approach you open specific TCP ports. This is a more complex procedure than unblocking processes as it is necessary to configure both the firewall and the license manager. The license manager requires configuring because in its default setup, it uses default TCP ports that change when restarted. It is necessary therefore to tell the license manager to use fixed ports. These ports can then be opened in the firewall. The procedure is as follows:
|
We know at least one firewall that, in its default configuration, does not include the IP address 127.0.0.1 as part of the local area network. This IP address is known as the loopback address or localhost and is used for local IP communication - that is not only is it within the local area network but is in fact within the local machine. The license manager uses this IP address for local inter-process communication and if this is blocked it won't start correctly.
If you find that you need to give the license manager processes access to the wider Internet even for use on the local machine, then it is likely that it is blocking the loopback address. We strongly recommend that you configure your firewall to classify 127.0.0.1 as a local IP address as opening the license manager processes to the wider Internet represents a security risk.