Applies to:
Concurrent Network software 6.x and Up

Changing Port Numbers or Server Names on Existing Concurrent Network Clients

 

Problem Statement

How do I change port numbers or server names on existing Concurrent Network clients?

Important Notes

• For server-side changes, see Port Numbers.
• Enterprise Network clients do not connect to the server after activation, so they do not need to be updated if the server name or port number changes.
• If you change or specify the DTS port (vendor daemon port) on the server, no client changes are usually required.
  • However, if the old port was opened as a remote port in the clients’ firewalls, those firewall rules must be updated to allow the new port.
• If you change the lmgrd port on the server, you must update any existing clients.
• Clients must also be updated if the server name changes or if licenses are moved to a different server.

Where Client Settings Are Stored

The server name and port number are stored on each client in a System Registry key.

64-bit Windows:
HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE

32-bit Windows:
HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE

This information originally comes from the Palisade_NetworkClient.ini file used during installation. It can be changed later either through the end-user software’s License Manager or directly in the System Registry.

 

Redirecting a Client – Method 1: End-User Software

If you have only a few installed clients, this is usually the easiest approach.

1. Run @RISK (or any DTS-licensed software) with full administrative rights by right-clicking and selecting Run as Administrator.

   1. All DTS applications share the same license path.

2. Click the @RISK icon on the left-hand side and then click License Manager.

3. Click Select License, then click the settings cog to open Manage Network Server Connections.

4. Select the old entry (portnumber@servername or @servername) and click Delete.

5. Click Import Client.ini and browse to the Palisade_NetworkClient.ini file created on the new server.

As an alternative to steps 4 and 5, you can select the old server entry and click Edit.

If you previously opened the old lmgrd port as a remote port in the client firewall, update the firewall settings to allow the new port.

 

Redirecting a Client – Method 2: Registry Edit

You can also update the lmgrd port number or server name directly by editing the System Registry key.

If the lmgrd port number is specified on the server, the registry value should be in the form:
portnumber@servername;PalisadeSystemFolder

If the lmgrd port is dynamic on the server, the registry value should be:
@servername;PalisadeSystemFolder

Multiple servers can be listed, separated by semicolons (;).

PalisadeSystemFolder is the System folder under the main DTS installation folder.

By default:
64-bit Windows: C:\Program Files (x86)\Palisade\System
32-bit Windows: C:\Program Files\Palisade\System

 

Examples

27003@ourserver;C:\Program Files\Palisade\System
@ourserver;C:\Program Files\Palisade\System
27003@ourserver;C:\Program Files (x86)\Palisade\System
@ourserver;C:\Program Files (x86)\Palisade\System

If you opened the old lmgrd port as a remote port in the client firewall, update the firewall rules to match the new port.

Using a .REG File

You may automate the change using a .REG file.

For 64-bit Windows:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\FLEXlm License Manager]
"PALISADE_LICENSE_FILE"="27003@ourserver;C:\Program Files (x86)\Palisade\System"

For 32-bit Windows:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager]
"PALISADE_LICENSE_FILE"="27003@ourserver;C:\Program Files\Palisade\System"

If the lmgrd port on the server is dynamic, omit the port number but keep the @ sign in the registry value.

 

Related Articles

Port Numbers
Installing and Configuring Palisade Server Manager