You can use the “View Log…” button on the “Config Services” tab of LMTOOLs in order to see which ports need to be opened through your firewall. Please notice that the Windows built-in firewall can cause these sort of problems. For example, my server log has these lines:
License file(s): C:\Program Files (x86)\Prime Focus\Krakatoa\etc\Win32\frantic_license.lic
9:19:08 (lmgrd) lmgrd tcp-port 27000
9:19:08 (lmgrd) Starting vendor daemons ...
9:19:08 (lmgrd) Started frantic (pid 6600)
9:19:08 (frantic) FLEXnet Licensing version v11.4.0.0 build 31341
9:19:08 (frantic) Server started on GODEL for: krakatoa-max
9:19:08 (frantic) krakatoa-max-render
9:19:08 (lmgrd) frantic using TCP-port 3567
So I should enable communication over port 27000 for the machine’s external facing firewall.
You might try specifying the TCP port of the license server in the registry setting so that instead of @cs02 you get 27000@cs02. The license file can be modified in order to manually choose a TCP port by adding the port number to the right of your MAC address on the SERVER line of the license file.
That log seems to indicate that there is a rogue lmgrd.exe running the frantic vendor daemon already. Basically, one of the older attempts at a license server failed to shut down correctly.
You can resolve this by restarting (if that is feasible for your workplace) or by using Task Manager to kill the rogue process. I prefer the tool “Process Explorer” since it will easily show you which lmgrd.exe has spawned the frantic.exe as a sub-process.