HomeTroubleshootingAll Products: Startup"FAILURE: Unable to reach a network server."

2.50. "FAILURE: Unable to reach a network server."

Applies to: All 6.x/7.x network client software

I installed the 6.x or 7.x network client successfully, but when I try to run it, I get this error message:

FAILURE: Unable to reach a network server.

followed by

Authorization failure.
Details:
There is no available license for @RISK.

(or whatever product I'm trying to launch).

There are several possible causes. The first thing is to determine whether the problem is on the client or the server, or on your network between them.

Are other clients able to run?

If no clients can run, especially if they used to be able to run, the problem is likely to be on the server rather than the clients. Please follow the troubleshooting tips in this first section.

  • Look at Server Manager's display to verify that a network license has been activated and is still current.

  • Check the server firewall settings to ensure that the server lets Palisade.exe and lmgrd.exe both send and receive. See also Network Ports and Firewalls (7.x) or Network Ports and Firewalls (6.x).

  • Make sure that the license process is running on the server. If Server Manager says "Running", click the Status button and look for "Palisade UP" in the status display. If the status display does not contain "Palisade UP", the license process is not running. In that case, click the magnifying glass in lower left, and then the View button, and look at the last few lines of the display to see the failure reason. Most likely it s a port-number conflict.

  • If you have other FLEXnet software licenses from other vendors running on the same server, verify that they are not using the same lmgrd ports as Palisade. The best way to do this is to leave them all unspecified. But if you specify any of the lmgrd ports, you must specify all of the lmgrd ports, and they must be unique.

    With vendor daemon ports, we don't recommend that you specify any, but if you do then you don't need to specify all of them. For any vendor daemon ports that you do specify, stay away from ports that you specified for lmgrd or for any other software from Palisade or any other vendor, and stay away from the range 27000–27009 if lmgrd ports are unspecified.

  • If you have manually edited your Server.lic file, you may have made a mistake. (We strongly recommend that you never edit this file directly. Instead, use Server Manager to set ports.) The SERVER line can have two or three fields: computer name of the server, Ethernet address, and lmgrd port number.

    • this_host is a valid wild-card for the first field, though Server Manager will change it to the actual computer name.
    • ANY is used in place of the second field when you have only activatable licenses. When you have certificate licenses, the actual Ethernet address appears in the second field and must not be changed, because that would break the digital signature of the file.
    • The third field will not appear if the lmgrd port number is set to Dynamic in Server Manager.

If other clients can run, either this client's settings or network connections are more likely to be the problem. The remainder of this article will help you troubleshoot them.

Are server and client set up to use the same name and LMGRD port?

  1. On the server, launch Server Manager. The first line of the display gives the server name. The communication port is given a line or two below that.

  2. On the client, in License Manager, click Select License » Concurrent Network and it will show you the server name it is trying to reach and the port number it is trying to use.

The server name on the client should match the host name in Server Manager. (There are some unusual exceptions, where network administrators use fully qualified domain names or IP addresses on clients. These must be carefully tested.)

If the server specifies a port number, the client must be using that port. If the server port is dynamic, the client port must also be dynamic. If anything doesn't match, click Edit on the client screen and make the necessary changes. For more information, please see Redirecting 7.x Concurrent Clients to a New Server or Port Number or Redirecting 6.x Concurrent Clients to a New Server or Port Number.

Can the client communicate with the server on the LMGRD port?

Verify that the client can communicate with the server using the server name and port number specified in the System Registry key
HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE or
HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE.
If no port number is specified, all ports in the range 27000 through 27009 must be open.

You can test whether a given port is open by using Telnet. (This requires a Telnet client on the client computer and a Telnet server on the server. These are part of Windows, but they might not be turned on. If they're not enabled, you can enable them in Windows Control Panel » Programs and Features » Turn Windows features on or off.) The command format is

telnet myservname 27000

You should get a blank screen if the port is open. If it's not, you should get an error message within about 60 seconds.

Can the client communicate with the server on the vendor daemon port?

The licensing software uses a second port, called the vendor daemon port. Problems with this port, in the absence of problems with the LMGRD port, are extremely rare but when other issues have been eliminated you should check for them.

  1. On the server, launch Server Manager. Click the magnifying-glass icon at lower left, then the View button. A Notepad window will open. Scroll down near the bottom to find the "Palisade using tcp-port". (Ctrl+F is the search command in Notepad.)

  2. On the client, repeat the above Telnet test but specify the "Palisade using tcp-port" number. If you're checking firewall logs, be aware that the client typically uses a different port to communicate with this server's vendor daemon port. Unlike the LMGRD port, the vendor daemon port is not specified anywhere in the System Registry or elsewhere on the client.

If you have an issue with this port, you will need to adjust your firewall settings; see server firewall information in Network Ports and Firewalls (7.x) or Network Ports and Firewalls (6.x).

Are client and server on different subnets?

If so, you might need to use a fully qualified domain name, portnumber@servername.company.com rather than just portnumber@servername. You can set this in the System Registry key
HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE or
HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE.
(If you anticipate this problem, and you haven't yet installed the client software, edit the server name in the Palisade_NetworkClient.ini file before installing the client software.)

Additional keywords: Subdomain

Is the client firewall locking out Palisade software?

The client computer's firewall should allow PalFlexServer6.exe or PalFlexServer7.exe to send and receive. See client firewall information in Network Ports and Firewalls (7.x) or Network Ports and Firewalls (6.x).

Does FLEXnet need a longer timeout?

Most clients are fine with the default FLEXnet timeout of 0.1 second, but some have a problem because they need to make too many Internet "hops" to reach your server. If you've eliminated client configuration issues, you may have a timeout problem. Please see FLEXlm License Manager Times Out for more on this possibility.

Last edited: 2017-02-03

This page was: Helpful | Not Helpful