HomeNetwork GuideFAQsNetwork Ports and Firewalls

3.8. Network Ports and Firewalls

Applies to:
Palisade network software 6.x/7.x

How should I set up my firewalls?

Most of our customers don't need to make any changes in their firewall settings at all. But if you have a restrictive firewall, you may need to change some settings to let your Palisade network software run.

TL;DR version: On server, give Palisade.exe and lmgrd.exe send/receive privilege; if Automatic Activation fails use Manual Activation instead. On client, give send/receive privilege to PalFlexServer6.exe or PalFlexServer7.exe, depending on your software version.

How should I configure the firewall on my license server?

Your license server does two jobs: it activates your network license with Palisade's license server, and it provides licenses to the client computers.

Server's Internet communications with Palisade (when activating or deactivating a license):

If your firewall settings prevent Automatic Activation of your license, we recommend that you use the manual procedure rather than make firewall changes. For Manual Activation and Manual Deactivation instructions, see Activate Network License and Deactivating a Network License.

If you prefer to change server firewall settings and perform Automatic Activation, here is the relevant information:

  • Server Manager makes a direct connection between your server and Palisade's server via port 80, the same port used by Web browsers for http.
  • If you need to specify exceptions for your server firewall, use *.palisade.com.
  • If your firewall won't let you use wildcards, specify service.palisade.com and service2.palisade.com. We do not recommend listing our IP addresses in your firewall exceptions, because they could change without notice.

Server's communications with end-user computers (clients):

On the server, it's simplest to list Palisade.exe and lmgrd.exe as exceptions for send and receive.

If you prefer to open specific ports on the server, specify them as described in Port Numbers, and then open those in the server firewall for send and receive.

How should I configure the firewall on client (end-user) computers?

Client computers never need to communicate with Palisade's server. They do need to communicate with your license server. Concurrent Network clients do this while they run @RISK or other Palisade applications; Enterprise Network clients do this only during install or when updating the annual license.

If your client firewall is blocking communication with the server's license process, it's simplest to list PalFlexServer6.exe or PalFlexServer7.exe (depending on your software version) as an exception for send and receive in the client computer's firewall. If you prefer to open specific port numbers, see Set Options—Port Numbers to set specific lmgrd and vendor daemon ports on your server, and then open those ports for send and receive on the client.

Last edited: 2017-12-03

This page was: Helpful | Not Helpful