Applies to:
Network software

Setting Up Firewalls for @RISK or DecisionTools Suite Network Software

Question 1

Do I need to change my firewall settings to use the network software?

Answer

Most customers don’t need to modify their firewall settings. However, if your firewall is restrictive, you may need to allow certain programs to send/receive data.

Quick TL;DR:

• Server: Allow Palisade.exe and lmgrd.exe send/receive privileges.

• Client: Allow PalFlexServer8.exe.

• If Automatic Activation fails due to a firewall, use Manual Activation instead.

Question 2

How should I configure the firewall on my license server?

Answer

Your license server has two roles:

1. Activates your network license

2. Provides licenses to client computers

Internet access (server only, for activation/deactivation):

• Server Manager connects to Palisade’s server via port 80 (HTTP).

• To allow this through a firewall:

  • Use *.palisade.com as an exception

  • If wildcards aren’t supported, use:

    • service.palisade.com

    • service2.palisade.com

• Do not list IP addresses—they may change without notice.

• If Automatic Activation fails, use Manual Activation instead of changing firewall settings.

Server ↔ client communications:

• On the server: allow Palisade.exe and lmgrd.exe for send/receive.

• If you prefer opening ports: see Port Numbers and open them in the server firewall.

Question 3

How should clients be configured for firewall access?

Answer:

• Each client must communicate with the server when launching software and periodically while running.

• Client side: allow PalFlexServer8.exe for send/receive.

• Server side: allow Palisade.exe and lmgrd.exe.

• If opening specific ports: open outgoing server ports and, if necessary, the same ports as remote ports in the client firewall.