Home → More on Networks → Servers (5.x) → Palisade Using TCP-Port ... (5.x)
Applies to:
Palisade software releases 5.x
(If you have a 6.x network, or you're using Server Manager with a 5.x network, please see "Port Numbers" in the Guide for Administrators. The copy at that Web link was updated in May 2013 and contains complete information.)
Question:
The debug log shows two port numbers, an "lmgrd tcp-port" and a "palisade using TCP-port". How do I control these?
Response:
The "lmgrd port" can be specified in Server Manager or on the SERVER line of your license file. Client and server use the same port number for communication between the license software on the client and the LMGRD program on the server. For more on this port, please see Port Number Change for 5.x Concurrent Network.
The "Palisade port" or "vendor daemon port" is typically left unspecified. The Palisade.exe program (the "vendor daemon") chooses a server port number for communications with the client licensing software, and the client licensing software (PalFlexServer5.exe) chooses a client server port for communicating with the Palisade.exe program on the server. In the great majority of cases, this works well. In a very few unusual setups, it may be a problem for an Internet firewall. In that case, you can select a port that's not otherwise used on the server and then add that port as an exception to the server's firewall.
Specifying Palisade port (vendor daemon port):
last edited: 2013-05-09