Jump to content
Welcome to our new Citrix community!
  • 0

html5 receiver disconnects and closes tab after starting the app


Blair Muller

Question

Hi, 

 

Receiver 1.4, storefront 2.6, XenApp 7.6. HTML5 receiver is enabled in storefront and in through policies on the delivery controller - The Websocket registry entries were created on the worker servers and both ports 8008 and 1494 are listening and accessible via telnet. 

 

I can log into receiver for web and start an application or desktop - i can see up to the welcome part of starting the desktop (server 2012 r2) and there is a box on the screen that says 'starting application' but when its meant to start the tab is closed.

 

I've enabled logging and have got the following:

 

start Session
SESSION:|:BROWSERINFO:|:navigator =Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
SESSION:|:BROWSERINFO:|:os =WINDOWS
SESSION:|:BROWSERINFO:|:browser =CHROME;version=39
SESSION:|:PREFERENCE:|:ajax=true
SESSION:|:CONNECTION:|:ICA:|:ica type=autoOpener
SESSION:|:CONNECTION:|:LOADTIME:|:ica load time =24
SESSION:|:CONNECTION:|:LOADTIME:|:script load =129
SESSION:|:PREFERENCE:|:language=en-US
SESSION:|:CONNECTION:|:LOADTIME:|:language =224
SESSION:|:CONNECTION:|:initializing session
SESSION:|:CONNECTION:|:UI:|:initializing ui-interface
SESSION:|:GRAPHICS:|:session-size width:1920 height:979
SESSION:|:CONNECTION:|:LOADTIME:|:ui initialize =14
 SESSION:|:CONNECTION:|:ICA:|:ClientVersion 1.4.0.5024
SESSION:|:CONNECTION:|:ICA:|:initializing ica-interface
SESSION:|:CONNECTION:|:LOADTIME:|:ica initialize =7
SESSION:|:ICA:|:CHANNEL:|:supported channelCTXCPM 
SESSION:|:ICA:|:CHANNEL:|:supported channelCTXTW  
SESSION:|:ICA:|:CHANNEL:|:supported channelCTXTWI 
SESSION:|:ICA:|:CHANNEL:|:supported channelCTXCLIP
SESSION:|:ICA:|:CHANNEL:|:supported channelCTXCAM 
SESSION:|:ICA:|:CHANNEL:|:supported channelCTXCTL 
SESSION:|:ICA:|:CHANNEL:|:supported channelCTXEUEM
SESSION:|:ICA:|:TRANSPORT:|:WEBSOCKET:|:websocket-url=ws://<worker server IP>:8008
SESSION:|:ICA:|:TRANSPORT:|:WEBSOCKET:|:connected
SESSION:|:ICA:|:WINSTATION:|:DRIVER:|:init request
SESSION:|:ICA:|:THINWIRE:|:DRIVER:|:decoder worker
UI:|:RENDER:|:RENDERER:|:mode=2;width=1920,height=978
UI:|:RENDER:|:WEBGL:|:INIT_COMMAND
SESSION:|:ICA:|:WINSTATION:|:DRIVER:|:terminate session5
SESSION:|:ICA:|:TRANSPORT:|:WEBSOCKET:|:disconnect=
SESSION:|:CONNECTION:|:session ended
SESSION:|:CONNECTION:|:closing tab
ERROR:|:error =Citrix Receiver cannot connect to the server.
 
Can someone help me with this please?
 

 

Link to comment

10 answers to this question

Recommended Posts

  • 0

I don't know if un-encrypted websockets is a supported configuration.

I know that un-encrypted websockets used to work a while ago when you configured the browser to allow non-secure websockets.

But the last time I've tested that configuration was with Chrome 38.

I'm not sure if this still works reliably with Chrome 39.

I'd suggest that you configure a secure WebSockets scenario (either through NetScaler Gateway or direct SSL on the VDA) and try again.

Link to comment
  • 0

Thanks for the reply. 

 

I tested it externally so that it was going through the netscaler and the same result occurred. Here's the log from the external connection attempt:

 

start Session

SESSION:|:BROWSERINFO:|:navigator =Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36

SESSION:|:BROWSERINFO:|:os =WINDOWS

SESSION:|:BROWSERINFO:|:browser =CHROME;version=39

SESSION:|:PREFERENCE:|:ajax=true

SESSION:|:CONNECTION:|:ICA:|:ica type=autoOpener

SESSION:|:CONNECTION:|:LOADTIME:|:ica load time =208

SESSION:|:CONNECTION:|:LOADTIME:|:script load =717

SESSION:|:PREFERENCE:|:language=en-US

SESSION:|:CONNECTION:|:LOADTIME:|:language =870

SESSION:|:CONNECTION:|:initializing session

SESSION:|:CONNECTION:|:UI:|:initializing ui-interface

SESSION:|:GRAPHICS:|:session-size width:1920 height:975

SESSION:|:CONNECTION:|:LOADTIME:|:ui initialize =16

SESSION:|:CONNECTION:|:ICA:|:ClientVersion 1.4.0.5024

SESSION:|:CONNECTION:|:ICA:|:initializing ica-interface

SESSION:|:CONNECTION:|:LOADTIME:|:ica initialize =16

SESSION:|:ICA:|:CHANNEL:|:supported channelCTXCPM

SESSION:|:ICA:|:CHANNEL:|:supported channelCTXTW 

SESSION:|:ICA:|:CHANNEL:|:supported channelCTXTWI

SESSION:|:ICA:|:CHANNEL:|:supported channelCTXCLIP

SESSION:|:ICA:|:CHANNEL:|:supported channelCTXCAM

SESSION:|:ICA:|:CHANNEL:|:supported channelCTXCTL

SESSION:|:ICA:|:CHANNEL:|:supported channelCTXEUEM

SESSION:|:ICA:|:TRANSPORT:|:WEBSOCKET:|:websocket-url=wss://<netscaler external dns name>:443

SESSION:|:ICA:|:TRANSPORT:|:WEBSOCKET:|:connected

SESSION:|:ICA:|:WINSTATION:|:DRIVER:|:init request

SESSION:|:ICA:|:THINWIRE:|:DRIVER:|:decoder worker

UI:|:RENDER:|:RENDERER:|:mode=2;width=1920,height=974

SESSION:|:ICA:|:WINSTATION:|:DRIVER:|:terminate session5

SESSION:|:ICA:|:TRANSPORT:|:WEBSOCKET:|:disconnect=

SESSION:|:CONNECTION:|:session ended

SESSION:|:CONNECTION:|:closing tab

ERROR:|:error =Citrix Receiver cannot connect to the server.

 

 

We're running a configuration where the external netscaler dns name and the internal DNS name for the load balancing storefront IP is the same. Could this be an issue?

 

I also attempted the same connection but using a direct url to the delivery controller. This also failed.

Link to comment
  • 0

In the system event log on the worker server I found an error from 'TdIca', event ID 1016:

 

"The Citrix ICA Transport Driver received an invalid Transport packet on port 8008."

 

I can't find any reference to this on the web. Could anyone explain what this means or what it's caused by?

Link to comment
  • 0

Using the same DNS name for Gateway and StoreFront is certainly something I would not recommend to use! Even though this is now a supported configuration with 2.6, I still find that StoreFront is a complex beast and it will certainly act in unexpected ways.

Though, considering that the ICA session connects initially, I would say that it has nothing to do with StoreFront.

 

The eventlog message is rather strange.

 

I would start investigating the network stack and troubleshoot there (Network and Firewall drivers in the VDA image, Hypervisor virtual switch, Host Server NIC config, Switches, Routers, Cables)

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...