Home →
Network Guide →
Server Setup →
Step 2a: Set Options—Port Numbers
1.4. Step 2a: Set Options—Port Numbers
Disponible en español: Paso 2a: Configuración de Opciones – Números de Puertos
Applies to:
Palisade Server Manager 6.x/7.x/8.x
Click Start »
All Programs » Palisade Network Server » Server
Manager. Server Manager will update any 5.x-7.x license process;
see What
if I already have a Palisade 5.x-7.x license on this server?
The defaults are to select both communication ports
dynamically, and to disallow borrowing. Your current options are shown in the
Network Server Information box. Click Options if you
want to change them. Otherwise, skip to Server
Step 3.
Which port numbers does the license process use?
The FLEXnet licensing software uses two TCP/IP ports for
communications between client and server. They are called the lmgrd port and the Palisade or vendor daemon port. You
can allow both of them to be chosen dynamically (the typical setting), or you
can specify either or both of them. “Dynamic” means that the software chooses
the ports each time the license service starts.
- If you specify the lmgrd port, you can choose any unused
port number. If the lmgrd port is set to “Dynamic”, the software will choose an
unused port number, but only within the range 27000 to 27009.
- If you specify the Palisade vendor daemon port, you can
choose any unused port number. If the Palisade port is set to “Dynamic”, the
software will choose an unused port number, not limited to the range 27000 to
27009.
- You must not specify the same port number for lmgrd and the
vendor daemon.
- By default, a first-time install of Server Manager allows
both ports to be chosen dynamically. However, if you’re installing Server
Manager on a server that already has Palisade 5.x-7.x licensing software,
Server Manager will bring forward any port selections you have already made.
- If you want to specify port numbers, it’s best to do that
before you install multiple clients. If you change the lmgrd port number later,
you will also need to change it on every Concurrent Network client that is
already installed.
Caution:
If you have other FLEXnet-licensed products on the same server, then either
every one needs to specify a unique lmgrd port number, or none of them can
specify an lmgrd port number.
If you have not specified port numbers, you can determine
which ports the server is actually using. Click Status
in Server Manager.
Caution: There's no guarantee that the same ports will be used the next time the service starts up.
How can I set or change the lmgrd port?
- In
Server Manager, click Options.
- On
the Options screen, under Communication Port
Number (lmgrd), specify a port number (not otherwise used) or select
Dynamic.
- Click
OK, then Stop
Service, then Start Service.
- Generate
a new Palisade_NetworkClient.ini file to replace the old one, even if
you're not installing any new clients at this time.
- In a Concurrent Network, change the lmgrd port
number on any clients that have already been installed. See How
do I change port numbers or server names on existing Concurrent Network
clients?
How can I set or change the Palisade vendor daemon port?
| Server Manager 6.2 and newer | Server Manager 6.0 and 6.1 |
|---|
- In Server Manager, click Options,
just
below the lmgrd port
- On the Options screen, under Communication Port Number (vendor daemon), specify a port number (not otherwise used) or select Dynamic.
- Click OK, then Stop Service, then Start Service.
|
- In Server Manager, click Open LIC Folder.
- Open PalisadeNetwork.lic in Notepad or another plain-text editor.
- To specify a port, add PORT=portnumber at the end of the VENDOR line in both files. To let the FLEXnet software choose a port dynamically, remove the PORT specification from the VENDOR line.
- Repeat the same edit on Server.lic. Server.lic must use the same vendor daemon port as PalisadeNetwork.lic.
- In Server Manager, click Stop Service, then Start Service.
|
There is no need for a new INI file if you change the vendor daemon port but not the lmgrd port.
There’s no software setting on the client for the vendor
daemon port. However, if you previously found that you needed to open that port
in the firewall of any installed clients, you will need to update the client
firewall settings.
See also: Network Ports and Firewalls for recommended firewall settings.
Last edited: 2020-03-27