Xenapps Troubleshooting Blog

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...

■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-...