Tech Paper: Communication Ports Used by Citrix Technologies 编辑

November 3, 2022 Author:  Martin Zugec, Mads Petersen, Arnaud Pain, James Kindon, Matt Brooks, Steve Beals, Rainer HasenzaglSpecial thanks:  Bjorn Paulson, Jan Tytgat

Tech Paper: Communication Ports Used by Citrix Technologies

This article provides an overview of common ports that are used by Citrix components and must be considered as part of networking architecture, especially if communication traffic traverses network components such as firewalls or proxy servers where ports must be opened to ensure communication flow.

Not all ports need to be open, depending on your deployment and requirements.


Citrix SDX

SourceDestinationTypePortDetails
Admin WorkstationCitrix SDX lights out managementTCP80, 443HTTP or HTTPS - GUI Administration
 Citrix SDX SVMTCP80, 443HTTP or HTTPS - GUI and NITRO communication
  TCP22SSH/SCP Access
 Citrix SDX HypervisorTCP22SSH/SCP Access
Citrix SDX SVMCitrix ADC instanceTCP80, 443HTTP or HTTPS - GUI and NITRO communication
  TCP22SSH/SCP Access
  ICMP Using ICMP protocol to check instance availability
 NTP ServerUDP123Default NTP server port for synchronizing with multiple time sources
Citrix ADC NSIPCitrix SDX SVMSNMP161, 162SNMP events/traps from ADC instances to SDX SVM
  ICMP Using ICMP protocol to check instance availability


Citrix ADC

SourceDestinationTypePortDetails
Citrix ADC NSIPCitrix ADC Appliances in cluster setupUDP7000Cluster heartbeat exchange
 Citrix ADC Appliance (for High Availability)UDP3003Exchange of hello packets for communicating UP/DOWN status (heartbeat)
  TCP3008Secure High Availability configuration synchronization
  TCP3009For secure MEP.
  TCP3010Non-secure high availability configuration synchronization.
  TCP3011For non-secure MEP.
  UDP162Traps from ADC to Citrix ADM Center
  TCP22Used by the rsync process during file synchronization in high availability setup
 DNS ServerTCP, UDP53DNS name resolution
 NTP ServerUDP123Default NTP server port for synchronizing with multiple time sources
 Application Firewall signature URLTCP443Hosted signature updates on AWS
 Bot Management signature URLTCP443Hosted signature updates on AWS
 ADC lights out managementTCP4001, 5900, 623Daemon which offers complete and unified configuration management of all the routing protocols
 LDAP ServerTCP636LDAP SSL connection
  TCP3268LDAP connection to Global Catalog
  TCP3269LDAP connection to Global Catalog over SSL
  TCP389LDAP plaintext or TLS
 RADIUS ServerUDP1813RADIUS accounting
  UDP1645, 1812RADIUS connection
 Thales HSMTCP9004RFS and Thales HSM
Citrix ADC NSIPCitrix ADMUDP4739For AppFlow communication
  SNMP161, 162To send SNMP events/traps
  Syslog514To receive syslog messages in Citrix ADM
Citrix ADC SNIPCitrix ADMTCP5563For ADC metrics (counters), system events, and Audit Log messages from Citrix ADC to Citrix ADM.
  TCP5557, 5558For logstream communication from Citrix ADC to Citrix ADM.
Admin WorkstationCitrix ADC NSIPTCP80, 443HTTP or HTTPS - GUI Administration
  TCP22SSH Access

Note:

Depending on the Citrix ADC configuration, network traffic can originate from SNIP, MIP, or NSIP interfaces.If you have configured Citrix ADCs in High Availability mode, Citrix ADM uses the Citrix ADC subnet IP (Management SNIP) address to communicate with Citrix ADC.

Link to application firewall signatures

Link to bot management signatures


Citrix ADM

SourceDestinationTypePortDetails
Citrix ADMCitrix ADC NSIP or Citrix SD-WAN instanceTCP80, 443For NITRO communication
  TCP22For SSH communication
  ICMPNo reserved portTo detect network reachability between Citrix ADM and ADC instances, SD-WAN instances, or the secondary Citrix ADM server deployed in high availability mode.
 Citrix ADMTCP22For synchronization between Citrix ADM servers deployed in high availability mode.
  TCP5454Default port for communication, and database synchronization in between Citrix ADM nodes in high availability mode.
 UsersTCP25To send SMTP notifications from Citrix ADM to users.
 LDAP external authentication serverTCP389, 636Default port for authentication protocol. For communication between Citrix ADM and LDAP external authentication server.
 NTP ServerUDP123Default NTP server port for synchronizing with multiple time sources.
 RADIUS external authentication serverRADIUS1812Default port for authentication protocol. For communication between Citrix ADM and RADIUS external authentication server.
 TACACS external authentication serverTACACS49Default port for authentication protocol. For communication between Citrix ADM and TACACS external authentication server.
Citrix ADC/CPX instanceCitrix ADM license server/agentTCP27000License port for communication between Citrix ADM license server/agent and ADC/CPX instance.
  TCP7279Citrix vendor daemon port.
Citrix ADC NSIPCitrix ADMUDP162To receive SNMP traps from Citrix ADC
  UDP4739To receive ADC analytics log data using IPFIX protocol
  UDP514To receive syslog messages from Citrix ADC ADM
Citrix ADC SNIPCitrix ADMTCP5563To receive ADC metrics (counters), system events, and Audit Log messages from Citrix ADC instance to Citrix ADM
  TCP5557, 5558For logstream communication (for Security Insight, Web Insight, and HDX Insight) from Citrix ADC
Citrix ADMCitrix ADM AgentTCP443, 7443, 8443Port for communication between Citrix ADC agent and Citrix ADM

Note:

If you have configured Citrix ADCs in High Availability mode, Citrix ADM uses the Citrix ADC subnet IP (Management SNIP) address to communicate with Citrix ADC.

CTX124386 describes how to change the source, to communicate syslog messages to ADM, from the NSIP to the SNIP


Citrix Cloud

The only Citrix component needed to serve as a channel for communication between Citrix Cloud and your resource locations is a connector. This connector might be a Connector Appliance or a Cloud Connector depending on your use case. For more information on which connector you require, see Resource types
.


Connector Appliance

Once installed, the Connector Appliance initiates communication with Citrix Cloud through an outbound connection. All connections are established from the Connector Appliance to the cloud using the standard HTTPS port (443) and the TCP protocol. No incoming connections are allowed.

This is a list of ports that the Connector Appliance requires access to:

ServicePortSupported Domain ProtocolConfiguration details
DNS53TCP/UDPThis port must be open to the local setup
NTP123UDPThis port must be open to the local setup
HTTPS443TCPConnector Appliance requires outbound access to this port
HTTP3128TCPIf the Connector Appliance is set up as a proxy for Citrix Hypervisor updates, it requires inbound access to this port

To configure the Connector Appliance, IT admins must be able to access the admin interface on port 443 (HTTPS) of the Connector Appliance.

Note: You must include https:// at the start of the IP address.

Connector Appliance with Active Directory

Additional ports are required to use Active Directory with Connector Appliance. The Connector Appliance requires an outbound connection to the Active Directory domain via the following ports:

ServicePortSupported Domain Protocol
Kerberos88TCP/UDP
End Point Mapper (DCE/RPC Locator Service)135TCP
NetBIOS Name Service137UDP
NetBIOS Datagram138UDP
NetBIOS Session139TCP
LDAP389TCP/UDP
SMB over TCP445TCP
Kerberos kpasswd464TCP/UDP
Global Catalog3268TCP
Dynamic RPC Ports49152–65535TCP


Cloud Connector

All connections are established from the Cloud Connector to the cloud using the standard HTTPS port (443) and the TCP protocol. No incoming connections are accepted.

Cloud Connectors must be able to connect to Digicert for certificate revocation checks.

SourceDestinationTypePortDetails
Cloud Connectorshttp://*.digicert.comHTTP80Periodic Certificate Revocation List checks
 https://*.digicert.comHTTPS443 
 https://dl.cacerts.digicert.com/DigiCertAssuredIDRootCA.crtHTTPS443 
 https://dl.cacerts.digicert.com/DigiCertSHA2AssuredIDCodeSigningCA.crtHTTPS443 

To find the list of addresses that are common to most Citrix Cloud services and their function, refer to product documentation
.


Citrix DaaS

SourceDestinationTypePortDetails
Virtual Delivery AgentGateway ServiceTCP443Rendezvous Protocol
Cloud ConnectorsCloud Connectors  The cloud connector acts as proxy for the Delivery Controller. All ports listed for Delivery Controller to Delivery Controller in the Citrix Virtual Apps and Desktops section
also need to be considered.
Cloud ConnectorsVirtual Delivery AgentTCP, UDP1494Access to applications and virtual desktops by ICA/HDX. EDT protocol requires 1494 to be open for UDP.
  TCP, UDP2598Access to applications and virtual desktops by ICA/HDX with Session Reliability. EDT protocol requires 2598 to be open for UDP.
    The cloud connector acts as proxy for the Delivery Controller. All ports listed for Delivery Controller to VDA in the Citrix Virtual Apps and Desktops section
also need to be considered.
 File ServerTCP139,445Access to VDI acting as File server CSV mount points
Citrix Provisioning Server ConsoleCloud ConnectorsHTTPS443Provisioning Server integration with Citrix Cloud Studio
Citrix License ServerCitrix CloudHTTPS443Citrix License Server integration with Citrix Cloud
CVAD Remote PowerShell SDKCitrix CloudHTTPS443Any system running scripts based on the CVAD Remote PowerShell SDK

Read more about Citrix License Server integration here
. Read more about Citrix Provisioning Server integration here
. Read more about the CVAD Remote PowerShell SDK here


Citrix Gateway Service

By default, the Gateway Service will proxy HDX connections via the Citrix Cloud Connectors, however Rendezvous Protocol changes the flow of HDX connections in an attempt to directly connect the Virtual Delivery Agent to the Gateway Service bypassing the Citrix Cloud Connectors

Rendezvous Protocol and HDX Enlightened Data Transport Protocol (EDT)

SourceDestinationTypePortDetails
Virtual Delivery AgentGateway ServiceUDP443EDT UDP over 443 to Gateway Service

The Virtual Delivery Agents must have access to https://*.nssvc.net, including all subdomains. Or https://*.c.nssvc.net and https://*.g.nssvc.net.

Note:

If using EDT in Microsoft Azure, UDP must be defined on the Azure Network Security Group (NSG) protecting the Virtual Delivery Agent

Read more about Rendezvous Protocol and HDX Enlightened Data Transport Protocol (EDT) requirements here
.


Citrix Session Recording Service

Refer to the following link for Citrix Session Recording Service ports - Connectivity Requirements


Citrix Workspace Environment Management Service

SourceDestinationTypePortDetails
WEM AgentWEM ServiceHTTPS443HTTPS based communication between the WEM Agent and the WEM Service
WEM AgentCloud ConnectorTCP443, 8080Registration Traffic for WEM Agents

Read more about Citrix Workspace Environment Management Service requirements here
.


Citrix Endpoint Management

Refer to the following link for Citrix Endpoint Management (XenMobile) Ports – Port Requirements
.


Citrix Gateway

SourceDestinationTypePortDetails
Citrix Gateway SNIPLDAP Server (Load Balancing)TCP636LDAPS SSL connection
  TCP3268LDAP connection to Global Catalog
  TCP3269LDAP connection to Global Catalog over SSL
  TCP389LDAP plaintext or TLS
 RADIUS Server (Load Balancing)UDP1813RADIUS accounting
  UDP1645, 1812RADIUS connection
 Secure Ticketing Authority (STA)TCP80, 8080, 443Secure Ticketing Authority (embedded into XML Service)
 Virtual Delivery AgentTCP, UDP1494Access to applications and virtual desktops by ICA/HDX. EDT protocol requires 1494 to be open for UDP.
  TCP, UDP2598Access to applications and virtual desktops by ICA/HDX with Session Reliability. EDT protocol requires 2598 to be open for UDP.
  TCP, UDP443Access to applications and virtual desktops by ICA/HDX over TLS/DTLS.
  TCP8008Access to applications and virtual desktops by ICA/HDX from Citrix Workspace app for HTML5
  UDP16500..16509ICA/HDX audio over UDP Real-time Transport
 StoreFrontTCP80, 443Citrix Gateway communication with StoreFront
Citrix Gateway Plug-inVPN/CVADUDP3108, 3168, 3188For VPN tunnel with secure ICA connections
  TCP, UDP3148, 3149, 3159For VPN tunnel with secure ICA connections
Admin WorkstationCitrix GatewayTCP80, 443HTTPS - GUI Administration
  TCP22SSH Access
Citrix GatewayDNSTCP, UDP53Communication with the DNS server

For more information about required ports for Citrix Gateway in DMZ setup, refer to CTX113250
.

Note:

All the above ports are not mandatory, depending on your own configuration.


Citrix Hypervisor

SourceDestinationTypePortDetails
Citrix HypervisorCitrix HypervisorTCP443Intra-host communication between members of a Resource Pool using XenAPI
 NTP ServiceTCP, UDP123Time Synchronization
 DNS Service Domain ControllerTCP, UDP TCP53, 389DNS User authentication when using Active Directory integration (LDAP)
  TCP636LDAP over SSL (LDAPS)
 FileServerTCP, UDP139ISOStore:NetBIOSSessionService
  TCP, UDP445ISOStore:Microsoft-DS
 SAN ControllerTCP3260iSCSI Storage
 NAS Head/ File ServerTCP2049NFS Storage
 SyslogTCP514Sends data to a central location for collation
 ClusteringTCP8892, 21064Communication between all pool members in a clustered pool.
  UDP5404, 5405 
Admin Workstation (XenCenter)Citrix HypervisorTCP22SSH
  TCP443Management using XenAPI
 Virtual MachineTCP5900VNC for Linux Guests
  TCP3389RDP for WindowsGuests

Read more about Citrix License Server requirements here
.

Note:

If FQDN is used instead of IP as resource, then make sure it is resolvable.


Citrix License Server

SourceDestinationTypePortDetails
Any Citrix ComponentCitrix License ServerTCP27000Handles initial point of contact for license requests
  TCP7279Check-in/check-out of Citrix licenses
Admin WorkstationCitrix License ServerTCP8082Web-based administration console (Lmadmin.exe)
  TCP8083Simple License Service port (required for CVAD)
  TCP80Licensing Config PowerShell Snap-in Service


Citrix SD-WAN

SourceDestinationTypePortDetails
SD-WAN Standard and Enterprise EditionSD-WAN Standard and Enterprise EditionUDP4980Static Virtual Path and Dynamic Virtual Path tunnels between SD-WAN SE/EE devices.
 SD-WAN CenterTCP2156Reporting communication between SD-WAN Center and SD-WAN SE/EE devices.
 Citrix Cloud Zero Touch Deployment ServiceTCP443Authentication communication between SD-WAN devices and Citrix Cloud Services.
 RADIUSTCP1812Default port for authentication protocol. For communication between SD-WAN SE/EE and RADIUS external authentication server.
 TACACS+TACACS49Default port for authentication protocol. For communication between SD-WAN SE/EE and TACACS external authentication server.
 SNMPUDP161, 162SNMP authentication and polling to SD-WAN SE/EE devices.
 NetFlowUDP2055NetFlow polling to SD-WAN SE/EE devices.
 AppFlow (Citrix ADM)TCP4739For AppFlow communication between Citrix ADM and SD-WAN SE/EE devices.
 APITCP80, 443For NITRO API communication to SD-WAN SE/EE devices.
SD-WAN CenterCitrix Cloud Zero Touch Deployment ServiceTCP443Authentication communication between SD-WAN devices and Citrix Cloud Services.
SD-WAN WANOP EditionSD-WAN WANOP EditionTCPN/ASD-WAN WO Edition transparently optimizes TCP traffic between two sites. The original source destination and port go unchanged throughout the segments of the network.
 API (Citrix ADM)TCP80, 443For NITRO API communication between Citrix ADM and SD-WAN WANOP devices.
 SSH (Citrix ADM)TCP22For SSH communication between Citrix ADM and SD-WAN WANOP devices.
 AppFlow (Citrix ADM)TCP4739For AppFlow communication between Citrix ADM and SD-WAN WANOP devices.
 Citrix ADMICMPN/AFor network reachability between Citrix ADM and SD-WAN WANOP devices.
 RADIUSTCP1812Default port for authentication protocol. For communication between SD-WAN WO and RADIUS external authentication server.
 TACACS+TACACS49Default port for authentication protocol. For communication between SD-WAN WO and TACACS external authentication server.
 SNMPUDP161, 162SNMP authentication and polling to SD-WAN WO devices.
SD-WAN WANOP Edition (SSL Acceleration Enabled)SD-WAN WANOP Edition (SSL Acceleration Enabled)TCP443SD-WAN WO Edition secure peering feature encrypts traffic between SD-WAN peers.
Citrix Orchestrator On-Premises9.9.9.9UDP/TCP53DNS resolution of pertinent cloud service domains
 SD-WAN Standard and Enterprise EditionTCP443Communication between Orchestrator On-Premises and SD-WAN SE/EE devices
 Citrix CloudTCP443Authentication communication with Citrix Cloud services
 SD-WAN Standard and Enterprise EditionSSH22Communication between Orchestrator On-Premises and SD-WAN SE/EE devices


Citrix Virtual Apps and Desktops

SourceDestinationTypePortDetails
Delivery ControllerCitrix Hypervisor Resource Pool MasterTCP80, 443Communication with Citrix Hypervisor infrastructure
 Microsoft SCVMM ServerTCP8100Communication with Hyper-V infrastructure
 VMware vCenter ServerTCP443Communication with vSphere infrastructure
 Microsoft SQL ServerTCP1433Microsoft SQL Server
 Virtual Delivery AgentTCP80 (Bidirectional)Delivery Controller initiates the connection when discovering local applications or for gathering information about local processes, performance data, and so on.
 Delivery ControllerTCP80Communication between Delivery Controllers
  TCP89Local Host Cache (This use of port 89 may change in future releases.)
  TCP9095Orchestration service
Citrix Director and Admin WorkstationVirtual Delivery AgentTCP135,3389Communication between Citrix Director and Virtual Delivery Agent for Remote Assistance
  TCP389LDAP Note: For the login step, Citrix Director does not contact the AD but does a local logon using the native Windows API - LoginUser (which might internally be contacting the AD).
Citrix Workspace appStoreFrontTCP, UDP80,443Communication with StoreFront
  UDP16500..16509Port range for UDP ICA/HDX audio
Virtual Delivery AgentDelivery ControllerTCP80 (Bidirectional)Used by process ‘WorkstationAgent.exe’ for communication with Delivery Controller.
Admin WorkstationDirector ServerTCP80, 443Access to Citrix Director website
 Delivery ControllerTCP80, 443When using a locally installed Citrix Studio console or the SDK to directly access Delivery Controller.
 Virtual Delivery AgentTCP, UDP49152..65535Dynamically allocated high-port when initiating a Remote Assistance session from a Windows machine to a Virtual Delivery Agent.
HdxVideo.jsVirtual Delivery AgentTCP9001HTML5 video redirection and Browser Content Redirection
secure WebSocket service needed to redirect HTTPS websites. WebSocketService.exe - runs on the local system and performs SSL termination and user session mapping. TLS Secure WebSocket listening on 127.0.0.1 port 9001.

Read more about Citrix License Server requirements here
.


Citrix App Layering

Refer to the following link for Citrix App Layering ports – Firewall Ports
.


Federated Authentication Service

SourceDestinationTypePortDetails
StoreFrontFAS ServerTCP80To send identity assertion of the user.
FAS ServerMicrosoft Certificate AuthorityTCP135Certificate Request*
Virtual Delivery AgentFAS ServerTCP80Fetch the user certificate from the FAS Server.

Note:


Provisioning Services

SourceDestinationTypePortDetails
Provisioning ServerProvisioning ServerUDP6890..6909Inter-server communication
 Microsoft SQL ServerTCP1433Communication with Microsoft SQL Server
 Domain ControllerTCP389Communication with Active Directory
Target DeviceBroadcast/DHCPServerUDP66, 67Only DHCP options: Obtaining network boot DHCP options 66-TFTP Server Name (Bootstrap Protocol Server) and 67-Boot file name (Bootstrap Protocol Client).
 Broadcast/PXEServiceUDP69Trivial File Transfer (TFTP) for Bootstrap delivery
 TFTP ServerUDP6910Target Device login at Provisioning Services
 Provisioning ServerUDP6910..6930Virtual disk Streaming (Streaming Service) (configurable)
  UDP6901, 6902, 6905Target device to Citrix Provisioning communication (not configurable)
  UDP6969, 2071Only BDM: Two Stage Boot (BDM). Used in boot from ISO or USB scenarios only.
  TCP54321..54323SOAP Service – Used by Imaging Wizards
Admin WorkstationProvisioning ServerTCP54321..54323SOAP Service – Used by Console and APIs (MCLI, PowerShell, etc.)
 Delivery ControllerTCP80When using on-prem CVAD - used by Console wizards when creating Broker Catalogs
 CVAD ServiceTCP443When using CVADS - used by Console wizards when creating Broker Catalogs


Universal Print Server

SourceDestinationTypePortDetails
Virtual Delivery AgentUniversal Print ServerUDP7229Universal Print Server print data stream (CGP) port (configurable
)
Virtual Delivery AgentUniversal Print ServerTCP8080Universal Print Server web service (HTTP/SOAP) port (configurable
)


Remote PC Access

SourceDestinationTypePortDetails
Admin WorkstationVirtual Delivery AgentUDP9Wake on LAN for Remote PC Access power management
WOL ProxyVirtual Delivery AgentTCP135Wake Up Proxy for Remote PC Access power management

Note:

Remote PC Access is using the same Virtual Delivery Agent ports as regular virtual desktops


Session Recording

SourceDestinationTypePortDetails
Virtual Delivery AgentSession Recording ServerTCP80, 443Communication between Session Recording Agent installed on Virtual Delivery Agent to connect to the Session Recording Server. Default installation uses HTTPS/SSL to secure communications. If SSL is not configured, use HTTP.
Session Recording Policy ConsoleSession Recording ServerTCP80, 443Communication between server where the Session Recording Policy Console is installed and Session Recording Server
Session Recording PlayerSession Recording ServerTCP80, 443Communication between the workstation where the Session Recording Player is installed and Session Recording Server.


StoreFront

SourceDestinationTypePortDetails
User DeviceStoreFront ServerTCP80, 443Connecting to the store hosted on StoreFront server
StoreFront ServerDomain ControllerTCP, UDP389LDAP connection to query user-friendly name and email addresses
  TCP, UDP88Kerberos
  TCP, UDP464Native Windows authentication protocol to allow users to change expired passwords
 StoreFront ServerTCPRandomly selected unreserved port per service. Scroll down to the end of this table for configuration of firewalls when you place StoreFront in its own network.Used for Peer-to-peer Services (Credential Wallet, Subscriptions Store (1 per Store). This service uses MS .Net NetPeerTcpBinding which negotiates a random port on each server between the peers. Only used for communication within the cluster.
  TCP808Used for Subscription Replication Services. Not installed by default. Used to replicate subscriptions between associated clusters
 Delivery Controller, XenMobileTCP80, 443For application and desktop requests.
 Citrix ADCTCP8000For Monitoring Service used by Citrix ADC load balancer.
StoreFrontCitrix GatewayTCP443Callback URL to reach Citrix Gateway from StoreFront

Use the following information for configuration of firewalls when you place StoreFront in its own network:

  1. Locate the config files:
    • C:\Program Files\Citrix\Receiver StoreFront\Services\SubscriptionsStoreService\Citrix.DeliveryServices.SubscriptionsStore.ServiceHost.exe.config
    • C:\Program Files\Citrix\Receiver StoreFront\Services\CredentialWallet\Citrix.DeliveryServices.CredentialWallet.ServiceHost.exe.config
  2. Edit both the config files changing the values for endpoint URIs.

    For example - <endpoint uri="net.p2p://CitrixCredentialWalletReplication"> so any address that starts with net.p2p:// includes the port. You should end up with <endpoint uri="net.p2p://CitrixCredentialWalletReplication:93”> and <endpoint uri="net.p2p://Citrix-Subscriptions-1__Citrix_Store"> becomes <endpoint uri="net.p2p://Citrix-Subscriptions-1__Citrix_Store:93"> and so on for all other net.p2p addresses.

  3. Restart the subscriptions store and credential wallet.
  4. The local firewall includes rules for allowing per application access, so it is not locked down by port.


Workspace Environment Management

SourceDestinationTypePortDetails
Infrastructure serviceAgent hostTCP49752“Agent port”. Listening port on the agent host which receives instructions from the infrastructure service.
Administration consoleInfrastructure serviceTCP8284“Administration port”. Port on which the administration console connects to the infrastructure service.
AgentInfrastructure serviceTCP8286“Agent service port”. Port on which the agent connects to the infrastructure server.
Agent cache synchronization processInfrastructure serviceTCP8285“Cache synchronization port”. Applicable to Workspace Environment Management 1909 and earlier; replaced by Cached data synchronization port in Workspace Environment Management 1912 and later. Port on which the agent cache synchronization process connects to the infrastructure service to synchronize the agent cache with the infrastructure server.
  TCP8288“Cached data synchronization port”. Applicable to Workspace Environment Management 1912 and later; replaces Cache synchronization port of Workspace Environment Management 1909 and earlier. Port on which the agent cache synchronization process connects to the infrastructure service to synchronize the agent cache with the infrastructure server.
Monitoring serviceInfrastructure serviceTCP8287“WEM monitoring port”. Listening port on the infrastructure server used by the monitoring service. (Not yet implemented.)
Infrastructure serviceMicrosoft SQL ServerTCP1433To connect to WEM Database
 Citrix License ServerTCP27000“Citrix License Server port”. The port on which the Citrix License Server is listening and to which the infrastructure service then connects to validate licensing.
  TCP7279The port used by the dedicated Citrix component (daemon) in the Citrix License Server to validate licensing.

Read more about Citrix Workspace Environment Management requirements here
.

Read more about Citrix License Server requirements here
.


CSV File

We would like to provide you with a csv file of the Citrix Communication Ports
that you can use for your own needs.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:3 次

字数:53388

最后编辑:6 年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文