Hi,
We have Reflection for HP v14.1 packaged as AppV deployed into XenApp published desktop v6.5. A couple of issues:
1) ssh sessions fails to connect (error trace below).
2) Using the Connection Setting will crash the session.

I have tested the connection to the host separately using the ssh command and it works fine (that is, firewall rules are in place, ports are open, etc.). Also, when connecting using telnet, the Reflection session works as well. Only fails with ssh sessions. Also, running the same ssh session in a regular Windows (that is, non-Citrix) environment works as well.

Using the Reflection trace facility, the trace log shows that the ssh connection failed very early in the handshake. Here are the some relevant information from the trace log (I have deleted
ip addr information from the trace that could be confidential):

Attachmate Reflection for HP with NS/VT 14.1.3
Reflection for HP
Version 14.1.3 build 459 32-bit

Operating System Microsoft Windows Server 2008 'R2' Enterprise x64 Edition
Version 6.1.7601 Service Pack 1 Build 7601

. . .
Reflection_14.1.411, SSH protocols 1.5/2.0, Reflection SSC Crypto Module 2.0.40
2018-06-08 14:52:12:421 debug3: Caller configured either IPV4 or IPV6
2018-06-08 14:52:12:421 debug3: ROT Entry to find COM server: {. . .
2018-06-08 14:52:12:421 debug3: Entering COM connection service critical section.
2018-06-08 14:52:12:421 debug3: Finding COM connection service.
2018-06-08 14:52:12:421 debug3: Connection not found for re-use . . . connection.
2018-06-08 14:52:12:421 debug3: Leaving COM connection service critical section.

0:05.83 ( .08) Network: 2018-06-08 14:52:12:499 debug3: Entering COM connection service critical section.
2018-06-08 14:52:12:499 debug3: Creating COM connection service.

0:07.26 ( 1.43) Network: error: Failed to create SSH connection server
error: Error (0x80004002): No such interface supported
2018-06-08 14:52:13:934 debug3: COM server creation failed . . . connection.
2018-06-08 14:52:13:934 debug3: Leaving COM connection service critical section.

Tried to google the 0x80004002 error, but didn't find related information.....

Your help is appreciated. Thank you.