The NextGen network key (red USB device) allows you to centralize the distribution of licenses, allowing the use of the program by computers connected to the same LAN or WAN.
Based on the location (both logical and geographic) of the computers running NextGen, a simple configuration needs to be performed so that those stations know where to look for the licensing device.
This article is aimed at users who do not deal with network configurations on a daily basis. Some terms and scenarios have been simplified. Users with more advanced knowledge of the subject will be able to extrapolate useful information for their use case.
Let's assume a server SRV_01
to which the red network key is connected.
In the following example, the server SRV_01
has IP address 192.168.100.1
If you do not know the IP address of a computer, whether server or client, you need to contact your network administrator or execute the command ```
ipconfig```
from the command line. Typically, the desired value is the one indicated as "IPv4 Address"
The simplest scenario is that of a computer, CLI_01
in the example, which is located on the same portion of the network as the server. The IP address of CLI_01
is 192.168.100.10
and in this case the server will be found automatically, without any additional configuration.
In more complex or large networks, IP addresses are organized into different groups called subnets. In the example, CLI_02
has the IP 192.168.200.23
and therefore belongs to a different subnet from the server. You will not be able to find the server address yourself, which we remember is 192.168.100.1
and will therefore need to specify it manually.
To do this, you need to open the web address http://localhost:1947/ on the browser of the computer CLI_02
on which NextGen is installed : the "Sentinel Admin Control Center" will be displayed, from which in the "Configuration" > "Access to remote license managers" section you can set the address to which the current computer must connect to find the license, then the IP address of SRV_01
above: 192.168.100.1
It is possible that servers and clients are physically distant, located in different company locations or in the case of remote working. In this case it is sufficient to proceed as in the previous point.
A specific article regarding this case is available here.