Network Software License: server set-up

Modified on Wed, 5 Mar at 12:30 PM

MANUAL NETWORK ADMINISTRATOR

Setting up a Network License Server for Pythagoras

A network license allows multiple users to access Pythagoras from different computers by connecting to a central license server. This guide explains how to install and activate a software-based network license on a server.


Prerequisites

Before installation, ensure you have:

  • A Windows-based server (Windows 10/11 or Windows Server). (System requirements)
  • Administrator rights on the server.
  • A stable internet connection for activation.
  • The Product Key received via email.


Download, install and activate

License management and control

Troubleshooting

License Transfer


Download, install and activate

1. Install Pythagoras and the Sentinel License Manager

  1. Download Pythagoras from the Download Pythagoras page.
  2. Run the installer and follow the instructions.
  3. The installer includes:
    • Pythagoras software.
    • Sentinel License Manager (SLM) for license management.


2. Activate the Network License

Online Activation (Recommended)

  1. Start Pythagoras.
  2. The Licensing window appears.
  3. Copy and paste the Product Key from your email.
  4. Click Install, then Close.
  5. Restart Pythagoras.
  6. The software should now use the network license.


Manual Activation (No Internet)

If online activation fails due to security settings, follow these steps: How to activate the license manually



License management and control

Sentinel License Manager

You can check the license details in Sentinel Admin Control Center:

  1. Open a web browser and go to: http://localhost:1947.
  2. Navigate to Products to view:
    • License number.
    • Available and in-use licenses.


Admin Control Center: http://localhost:1947 - allows you to check the license number, how many licenses are available, and how many are in use

Client - server communications

Pythagoras (= the protected application) on the client computer communicates via the Sentinal License Manager with other Sentinel License Managers running on other computers on the network. The Sentinel License Manager is software running on both the clients and the server.  


The local Sentinal License Manager running on a client discovers and communicates with the License Manager on the computer containing the Sentinel protection key using one of the following methods: 

  • The local Sentinel License Manager issues an UDB broadcast to local subnets on port 1947 using: IPv4 (always) or Ipv6 (if available).
  • The local Sentinel License Manager issues a UDP “ping” packet to port 1947 for all addresses specified in the Admin Control Center field “Specify Search Parameters”. These addresses may be individual machine addresses or  broadcast addresses. 

All Sentinel License Managers found by the discovery process are then connected via the TCP port 1947, using IPv4 or IPv6 as detected during discovery, and data regarding the remote Sentinel protection keys are transferred.


Changing the communication configuration:

  1. Open Sentinel Admin Control Center (http://localhost:1947).
  2. Go to Configuration > Access from Remote Clients.
  3. Ensure Broadcast Search for Remote Licenses is enabled.
  4. Add client IPs if security restrictions require manual configuration.
  5. Save changes and restart the Sentinel License Manager service.

Troubleshooting

  • Ensure port 1947 (TCP & UDP) is open on the server firewall.
  • The Sentinel License Manager service must be running.
  • Clients must be on the same network or configured for remote access.
  • If activation issues persist, contact Pythagoras support.

License Transfer

To move the license to another server, follow the How to transfer a license guide.

For further assistance, visit Pythagoras Support.








Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article