• View Communities
    • Citrix Developer Network
      The place for unfiltered straight talk on Citrix products. Blogs, code downloads, best practices, APIs, and more can all be found here.
    • Citrix Ready Community Verified
      Does it work with Citrix? Application compatibility questions are a thing of the past with the new Citrix Community Verified site.
    • Blogs
      Learn the latest from the Citrix employees who are building application delivery infrastructure technologies.
    • Blogosphere
      The Citrix Blogosphere is a window into the thousands of conversations taking place about Citrix and Application Delivery.
  •  Sign In
The Citrix Blog
Personal Blog
Gus Pinto
Related Tags
Version 1 by Gus Pinto
on May 11, 2008 20:18.


 
compared with
Current by Gus Pinto
on May 12, 2008 08:36.


 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

 Out of curiosity I decided to collect the communication ports for any given technology within the Citrix XenApp platform.... It turned out I didn't have to look much further, I found them on [Vinny's blog|http://community.citrix.com/blogs/citrite/elvins], posted a while back right here on the Citrix blogs, however his post only got a handful of views, since I think Vinny did a great job and tons of people need this kind of information, I'm extending his collection and sharing it out with a broader audience...
  
 This is an extremely helpful list to have always handy:
 \\
 \\
 *Application Performance Monitoring (powered by Citrix EdgeSight)*
 * EdgeSight Agent to Edgesight Server - TCP 80/443 (Payload and alerts)
 * EdgeSight Web console (non-IMA) to RSCorSvc on EdgeSight Agent - TCP 9035
 * EdgeSight Agent internal communication - TCP 9036 (client-side database)
 * EdgeSight database - SQL 1433 (configurable)
  
 *Client-side Application Virtualization -*
 * Streaming Client to Application Hub (File Server/Share) - SMB 445
  
 *EasyCall*
 * To client - HTTP(S)-TCP 8443 (PSync)
 * To Admin console (non-IMA) - TCP 443
 * To LDAP Directory\- TCP 389
 * To PBX - port varies by vendor
  
 *Independent Management Architecture (IMA) Services* \- TCP 2512, 2513
  
 *Licensing Service* \- TCP 27000, 27009 (configurable)
  
 *Server-side Application Virtualization*
 * Management Console (Using IMA) - TCP 2512, 2513
 * Application requests - TCP XML 80, 8080 or 443 (configurable)
 * Access to Applications Virtualized on the Server - ICA-TCP 1494, 2598 (Session Reliability)
  
 *Single Sign-on (powered by Citrix Password Manager)*
 * Management Console (non-IMA) or Agent to Password Manager Service - TCP-443
 * Management Console (non-IMA), Agent or Service to credential store
 ** Network File Share Credential Store - TCP/UDP 445 (CIFS) or TCP/UDP 135-139 (NetBIOS)
 ** Active Directory Credential Store - TCP/UDP - 389, 636, TCP - 3268, 3269
 ** Novell File Share Credential Store - TCP/UDP - 524  
  
 *SmartAccess (powered by Citrix Access Gateway)*
 * Standard and Advanced Edition
 ** Client connections\- TCP-SSL 443 (configurable)
 ** Advanced Access Control (AAC) to Appliance communication - TCP 80 or 443 (configurable), 9001, 9002, 9005
 ** Management Console
 *** to Appliance (non-IMA) - 9001, 9002, 9005
 *** to AAC - IMA-TCP-2513
 *** Enterprise Edition
 *** To client - SSL-TCP 443
 *** To internal network - SSL-TCP 443, Native Authentication port (i.e. RADIUS 1812, LDAP 389), Native application ports (i.e. ICA-1494)
 *** Management console (non-IMA) - SSH-TCP 22, HTTP(S)-TCP 80/443
  
 *SmartAuditor*
 * Management (non-IMA) - Use local console on Agent or on Server.
 * Agent to Broker (Recording and Policy Check) - TCP 80/443 (configurable)
 * Player to Broker - TCP 80/443 (configurable)
 * Agent to Server (Metadata and Video)\- Microsoft Message Queuing,
 ** Default - TCP: 1801; RPC: 135, 2101*, 2103*, 2105*; UDP: 3527, 1801 (*These port numbers may be incremented by 11 if the initia choice of RPC port is being used when Message Queuing initializes. A connecting QM queries port 135 to discover the 2xxx ports.)
 ** Over SSL\- TCP 80,443
  
 *WAN Optimizer \-Guidance provided was to get it from Admin Guide*
 * Appliance to Appliance - Pass-through native application port (e.g. ICA-1494, HTTP-80, LDAP-389)
 * Management Console (non-IMA) - TCP 80
 * Client to Appliance - TCP 443
  
 *Web Interface*
 * Client connections - TCP 80/443 (configurable)
 * Server-to-server - TCP XML 80/8080, 443 (using SSL Relay)
  
 Management console (partially IMA) - DCOM 135 (\+ configurable high port range), IMA-TCP 2513, TCP 80/443
 \\
 \\
 \--\-
   
 {color:#cc0000}*\!*{color} Please be advised that these have been gathered from product documentation and can change on future product releases. ;-)
  
 \--\-
 \\
 \\
 Nice work Vinny boy\! :-)
 Keep an eye on this guy's blog\!\!\!
 \\
 \\
 \\
 \\
 Cheers,
 \\
 \\
 Gus Pinto
 Microsoft MVP - Virtualization
 [Twitter/GusPinto|http://twitter.com/GusPinto]