In Windows systems with Hyper-V, Docker or WSL we may find that the port 1116 used by the License Server is not available. so this application cannot be run, therefore any of the SGO's softwares can't be activated through the Activation Tool. 


This is due because dynamic tcp port range should be changed in Windows distributions following IANA's recommendation, but some Windows installations don't have this change applied:


https://learn.microsoft.com/en-US/troubleshoot/windows-server/networking/default-dynamic-port-range-tcpip-chang


In a cmd we can also check if the port 1116 is available navigating to "C:\Program Files\SGO Apps\License Server\bin" and executing "sgoLicenseServer.exe -v". Any trouble with the port connection will appear prompted:



To list the ports in use in our system (and check that it does not appear the port 1116):


netstat -aof


To consult the list of excluded ports (and check that port 1116 is found in the excluded ports list):


netsh int ipv4 show excludedportrange protocol=tcp


this is an output example of the command above:


Protocolo tcp Intervalos de exclusión de puertos


Puerto de inicio    Puerto final

----------          --------

      1024        1123

      1124        1223

      1224        1323

      1324        1423

      1424        1523

      1524        1623

      2048        2147

      2180        2279

      2280        2379

      2380        2479

      2480        2579

      2706        2805

      2869        2869

      2870        2969

      2970        3069

      3070        3169

      3170        3269

      3270        3369

      3370        3469

      3480        3579

      3580        3679

      3780        3879

      3880        3979

      4393        4492

      4509        4608

      4709        4808

      4809        4908

      5357        5357

      6368        6467

      6468        6567

      7571        7670

      9574        9673

      9674        9773

      9774        9873

      9974       10073

     10074       10173

     10629       10728

     12762       12861

     12862       12961

     12962       13061

     14778       14877

     14878       14977

     50000       50059     *


* - Exclusiones de puertos administrados.


One temporary solution is to stop/start the winnat service. As admin:


net stop winnat

net start winnat


Now the port exclusion list may be something like:


netsh int ipv4 show excludedportrange protocol=tcp


Protocolo tcp Intervalos de exclusión de puertos


Puerto de inicio    Puerto final

----------          --------

      2869        2869

      5357        5357

     50000       50059     *


* - Exclusiones de puertos administrados.


We can also check in our Windows system our dynamic port interval in use:


netsh int ipv4 show dynamicport tcp


If the system is wrong configurated it will prompt something like:


Intervalo de puerto dinámico de protocolo tcp

-----------------------------------------------------------

Puerto de inicio    : 1024

Número de puertos   : 13977


To solve it permanently we can make use of these two commands (as admin):


netsh int ipv4 set dynamic tcp start=49152 num=16384

netsh int ipv6 set dynamic tcp start=49152 num=16384


and then reboot the system. After the reboot the output of command above should be: