Summary

Error: -15,570 - LM_CANTCONNECT - Cannot connect to server

Symptoms

Whilst trying to checkout a license from a license server you may see the following error message:

Cause

This error would normally indicate that there is a problem with the connection from the client application to the license server. This issue may be due to the configuration of the network, the quality of the network or could be a configuration issue on the Flexnet Publisher side.

Resolution

Things to check:

1. Check that there are no issues with the license server. Check the debug log for error messages that would indicate a problem and check that the license server has fully started. A log file for a working license server would look something like this:

10:12:12 (lmgrd) pid 7848

10:12:12 (lmgrd) Detecting other license server manager (lmgrd) processes...

10:12:12 (lmgrd) Done rereading

10:12:12 (lmgrd) FLEXnet Licensing (v11.10.0.0 build 95001 i86_n3) started on CHLTFLYNN (IBM PC) (10/13/2011)

10:12:12 (lmgrd) Copyright (c) 1988-2011 Flexera Software, Inc. All Rights Reserved.

10:12:12 (lmgrd) US Patents 5,390,297 and 5,671,412.

10:12:12 (lmgrd) World Wide Web: http://www.flexerasoftware.com

10:12:12 (lmgrd) License file(s): counted.lic

10:12:12 (lmgrd) lmgrd tcp-port 27000

10:12:12 (lmgrd) Starting vendor daemons ...

10:12:12 (lmgrd) Started flexera (pid 5428)

10:12:12 (flexera) FLEXnet Licensing version v11.10.0.0 build 95001 i86_n3

10:12:12 (flexera) Using options file: ".\flexera.opt"

10:12:13 (flexera) Server started on CHLTFLEXERA for: c1

10:12:13 (flexera) c2 c3 c4

10:12:13 (flexera) c5 e2

10:12:13 (flexera) EXTERNAL FILTERS are OFF

10:12:13 (lmgrd) flexera using TCP-port 63051

If there is an issue with the license server then please troubleshoot the issue using KB articles related to the error observed.

2. Check that you can ping the server machine from the client machine. If the ping fails then there is most likely an issue with network connection between client and server. Correct ping output would look like this on Windows:

C:\FNP\FNP 11.10\i86_n3>ping chkrispykreme

Pinging chkrispykreme.acresso.com [10.50.0.22] with 32 bytes of data:

Reply from 10.50.0.22: bytes=32 time=7ms TTL=128

Reply from 10.50.0.22: bytes=32 time<1ms TTL=128

Reply from 10.50.0.22: bytes=32 time<1ms TTL=128

Reply from 10.50.0.22: bytes=32 time<1ms TTL=128

Ping statistics for 10.50.0.22:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 7ms, Average = 1ms

3. Check that the license search path is looking at the correct location for the license server. Check the output of lmpath -status and see if the license server machine is listed:

Output from lmpath -status:

C:\FNP\FNP 11.10\i86_n3>lmpath -status

lmpath - Copyright (c) 1989-2011 Flexera Software, Inc. All Rights Reserved.

Known Vendors:

_____________

demo: @localhost;C:\Users\sflynn\Documents\New folder\license.lic

epro.lic

magnaecs: @localhost

niakwa: 27001@che-tech-sf1

flexera: @localhost

_____________

Other Vendors:

______________

C:\flexlm\license.dat

If the path is incorrect, then you can change the values using lmpath -override

If using a port outside of the default flex ports (27000-27009), make sure that the path includes the port number, for example 5555@chltflynn

4. Check the path of the server and client machines using the ipconfig tool on Windows and the ifconfig tool on Linux. Ensure that the information returned by these tools are the same as the information contained on the SERVER line of the license file that is being used. Also ensure that the Client and Server are on the same network as each other.

5. On Linux, check the /etc/hosts file to see if the correct IP address and hostname are being used.