

- #CITRIX RECEIVER NOT WORKING ON SAMSUNG CHROMEBOOK SERIES#
- #CITRIX RECEIVER NOT WORKING ON SAMSUNG CHROMEBOOK WINDOWS#
Of course, the downside here is that the backend needs to understand the WebSocket protocol, extract data from it and pass it on to the next layer.

HTML5 API provided by browsers instead provides a higher level WebSocket API, which abstracts sockets across various browsers (Chrome, Firefox, Safari, IE etc.) and platforms (such as Windows, Mac, Linux, ChromeOS etc) through which Receiver for HTML5 connects to XenApp and XenDesktop. What this means for connection is that it can’t use an OS-provided socket API like other native Receivers, meaning it can’t connect directly to 1494 (ICA) or 2598 (CGP) ports. Receiver uses HTML5 APIs provided by the browsers for all the features. This means we avoid installation, but also have the benefit of Receiver available for subsequent access. Browsers typically cache resources, so that files do not get downloaded multiple times. HTML, js, css, images and other resources are downloaded first time when users access HTML5 HDX session. Receiver for HTML5 is a javascript-based engine. This communication doesn’t involve any plugins or add-ons.

To start an HDX session, Receiver for Web opens Receiver for HTML5 in a new tab and passes. Receiver for HTML5, on the other hand, uses Receiver for Web for enumeration of apps/desktops.
#CITRIX RECEIVER NOT WORKING ON SAMSUNG CHROMEBOOK WINDOWS#
Receiver for Windows and Receiver for Chrome connecting directly to XA/XD. (Let’s keep Receiver for Chrome aside for now)īelow diagram shows how native Citrix Receivers like Receiver for Windows connect to XenApp and XenDesktop. Let’s take a look at how direct connections are made to XenApp 6.5 and XenApp/XenDesktop 7.6 environments without going through NetScaler Gateway. Users can also go to Receiver for Web (RfWeb)/Web Interface/NetScaler Gateway URL in a browser and launch native Receiver using browser plugins or protocol handler based communication in SF 3.0ĭirect Connections to XenApp and XenDesktop: ica file for a particular app/desktop and connect to XA/XD/Gateway for actual HDX connection. Windows, Linux, Mac) connect to Storefront/Web Interface/NetScaler Gateway to enumerate resources (App and Desktop), get the. Traditionally, native Citrix Receivers (e.g.
#CITRIX RECEIVER NOT WORKING ON SAMSUNG CHROMEBOOK SERIES#
This post is the first one in a series focused on how Receiver for HTML5 and Receiver for Chrome connect to the XenApp and XenDesktop backend in various deployments. We are starting the blog series explaining the technical internals of Receivers. I work for Receiver for HTML5 and Receiver for Chrome development team.
