Gateway

Opening the Appropriate Ports on the Firewalls

January 8, 2024

Contributed by:

C S C

You must ensure that the appropriate ports are open on the firewalls to support the different connections that occur among the various components involved in a double-hop DMZ deployment. For more information about the connection process, see Communication Flow in a Double-Hop DMZ Deployment.

The following figure shows common ports that can be used in a double-hop DMZ deployment.

localized image

The following table shows the connections that occur through the first firewall and the ports that must be open to support the connections.

Connections through the first firewall	Ports used
The web browser from the Internet connects to Citrix Gateway in the first DMZ. Note: Citrix Gateway includes an option to redirect connections that are made on port 80 to a secure port. If you enable this option on Citrix Gateway, you can open port 80 through the first firewall. When a user makes an unencrypted connection to Citrix Gateway on port 80, Citrix Gateway automatically redirects the connection to a secure port.	Open TCP port 443 through the first firewall.
Citrix Receiver from the Internet connects to Citrix Gateway in the first DMZ.	Open TCP port 443 through the first firewall.

Connections through the first firewall

Ports used

The web browser from the Internet connects to Citrix Gateway in the first DMZ. Note: Citrix Gateway includes an option to redirect connections that are made on port 80 to a secure port. If you enable this option on Citrix Gateway, you can open port 80 through the first firewall. When a user makes an unencrypted connection to Citrix Gateway on port 80, Citrix Gateway automatically redirects the connection to a secure port.

Open TCP port 443 through the first firewall.

Citrix Receiver from the Internet connects to Citrix Gateway in the first DMZ.

Open TCP port 443 through the first firewall.

The following table shows the connections that occur through the second firewall and the ports that must be open to support the connections.

Connections through the second firewall	Ports used
Citrix Gateway in the first DMZ connects to the Web Interface in the second DMZ.	Open either TCP port 80 for an unsecure connection or TCP port 443 for a secure connection through the second firewall.
Citrix Gateway in the first DMZ connects to Citrix Gateway in the second DMZ.	Open TCP port 443 for a secure SOCKS connection through the second firewall.
If you enabled authentication on Citrix Gateway in the first DMZ, this appliance might need to connect to an authentication server in the internal network.	Open the TCP port on which the authentication server listens for connections. Examples include port 1812 for RADIUS and port 389 for LDAP.

The following table shows the connections that occur through the third firewall and the ports that must be open to support the connections.

Connections through the third firewall	Ports used
StoreFront or the Web Interface in the second DMZ connects to the XML Service hosted on a server in the internal network.	Open either port 80 for an unsecure connection or port 443 for a secure connection through the third firewall.
StoreFront or the Web Interface in the second DMZ connects to the Secure Ticket Authority (STA) hosted on a server in the internal network.	Open either port 80 for an unsecure connection or port 443 for a secure connection through the third firewall.
Citrix Gateway in the second DMZ connects to the STA residing in the secure network.	Open either port 80 for an unsecure connection or port 443 for a secure connection through the third firewall.
Citrix Gateway in the second DMZ makes an ICA connection to a published application or virtual desktop on a server in the internal network.	Open TCP port 1494 to support ICA connections through the third firewall. If you enabled session reliability on Citrix Virtual Apps, open TCP port 2598 instead of 1494.
If you enabled authentication on Citrix Gateway in the first DMZ, this appliance may need to connect to an authentication server in the internal network.	Open the TCP port on which the authentication server listens for connections. Examples include port 1812 for RADIUS and port 389 for LDAP.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Opening the Appropriate Ports on the Firewalls

January 8, 2024

Contributed by:

C S C

January 8, 2024

Contributed by:

C S C

Opening the Appropriate Ports on the Firewalls

In this article