bhui Absent Member.
Absent Member.
1945 views

ssh session failed to connect

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.
0 Likes
1 Reply
AutomaticReply Absent Member.
Absent Member.

Re: ssh session failed to connect

bhui,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.microfocus.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.microfocus.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.microfocus.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team
http://forums.microfocus.com



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.