Skip to main content

Network Communication Ports used by Citrix XenApp (the new name for Presentation Server)

■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) NOTE: After EdgeSight 4.5, replaced with IPC)

◦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

Comments

Post a Comment

Popular posts from this blog

The Ultimate Guide to Terminal Server Printing - Design and Configuration

The Ultimate Guide to Terminal Server Printing - Design and Configuration Written on Feb 02 2004 Filed under: Third Party Software, Printing, White Papers 131,143 views, 86 comments ________________________________________ by Brian Madden This paper is excerpted from the book Terminal Services for Windows Server 2003:Advanced Technical Design Guide, by Brian Madden and Ron Oglesby. At some point during your Terminal Server system design you'll remember that your users will probably want to print something sooner or later. Printing is an important function to users within their Terminal Server sessions, yet it has traditionally been the biggest nightmare for administrators of server-based computing systems. Ideally, printing from applications via RDP sessions should be no different than printing from any other application. It should be relatively seamless to the users, allowing them to click the print button within their application, easily select a printer, and qu...
Post a Comment
Read more

Troubleshooting Citrix Slow Performance Issues

Slowness reasons what is your environment ? - Changes . check Last Application Change, Network changes, OS changes patches, updates -  Roaming profiles , local , hybrid ? -> check the profile server - Terminal server event ID -  Fileserver                -where is the fileserver with the profiles located. ((so it's profile size isn't very big)                - Process CPU utilization                 -Teaming and bonding are specific name for Ethernet network,                 -load balancing -   DC/ DNS  (domain controller) -  SAN ( disk responsive time) ,- User connections (Disk Queue Length ,Disk Transfer Time) -  Antivirus check Logs malware ...
Post a Comment
Read more

Citrix Communications

Citrix Web Interface - Client Communications The diagram below shows the client communications when accessing Citrix XenApp via the Citrix Web Interface: Client device utilize a Web browser to authenticate to the Web Interface. 1. The Web server reads users’ credentials and forwards the information to the Citrix XML Service on servers in the server farms. The designated server configured with Web interface console acts as a broker between the Web server and the other servers in the farm. 2. The Citrix XML Service on the designated server retrieves from the servers a list of applications that users can access. These applications comprise the user’s application set. The Citrix XML Service retrieves the application set from the Independent Management Architecture (IMA) system. 3. The Citrix XML Service then returns the user’s application set information to the Web Interface running on the server. 4. The user clicks an application icon in the HTML page. 5. The C...
Post a Comment
Read more