Thick client separated from the CMS by packet filtering

You can publish reports or analytic objects to Crystal Enterprise by saving these objects to Crystal Enterprise from within Crystal Reports or Crystal Analysis, or by using the Crystal Import or Publishing Wizards. However, if there is a firewall between the computer running one of these thick clients and the CMS, this operation fails.

Configuring your Crystal Enterprise system to support this configuration when the firewall uses packet filtering is very similar to configuring your system to support a packet filtering firewall between the application tier and the Crystal Management Server (CMS).

First you must configure the CMS and the Input File Repository Server to use fixed port numbers for communications. Next you must alter your firewall rules to facilitate communication across the firewall using the fixed ports that you have specified.

For full instructions, follow the detailed steps in Application Tier separated from CMS by packet filtering but:

• Configure only the Crystal Management Server and the Input File Repository Server.
• Establish inbound firewall rules for communication between the Crystal Reports or Crystal Analysis machine and the CMS and Input File Repository Server. You do not need to establish an outbound firewall rule.

Related topics

• Command lines overview
• Changing the default server port numbers
• ccm.sh
• Configuring for packet filtering