Hi all,

My organization is currently moving parts of our infrastructure to a new Windows Server 2019 production machine, and we're currently stuck getting Reflection Workspace to connect to one of our remote mainframes from the new environment.

We have a seemingly identical Reflection installation on our old box, and it's able to to reach the remote system using the same session file, so I'm not sure exactly what's going wrong with the new installation.  The exact error is as follows:

"A timeout occurred during a call to transport code"

And it comes up when the session files is first opened, and on any subsequent attempts to connect to the host; the connection is never established.  The attempted connection is through telnet, with the host address explicitly specified.  Outside of Reflection, we're able to both ping and open a telnet connection to the host from Powershell or the command window successfully. 

(I should also note that this is a bare setup of Windows Server, with only the minimum set of features turned on at the moment, and I had to enable the Telnet Client to get the call mentioned above to work, so I wasn't sure whether there might be any other hidden dependencies or switches I needed to flip to get the connection through Reflection working correctly.)

I search for the issue in past discussions, but couldn't find anything for this particular error.  Is this something anyone has encountered, or has any idea about how to resolve?  Thanks in advance for any help you can provide.

Hi ,

Here is what our support team suggests. If the issue still persists, they recommend opening a support ticket, or feel free to follow up with more details here since some of the below contains clarifying questions: 

The first question to ask is “What version of Reflection Desktop?”  is the customer using. They indicate it works on another identical system, but fails on this new one. Guessing it is the same version, but I always like to know what version of our software which is installed, as it sometimes makes a difference in trouble-shooting and resolving the issue.

The message of “A timeout occurred during a call to transport code” sure looks like a secure connection or TLS related message. They indicate they are using Telnet, and the same session file from the PC which works, but could they be using a TLS 1.0 or TLS 1.2 connection. If so, they will need to get the certificate for their host system installed, this typically goes in the Microsoft Windows certificate cache. Thus they may have copied the Reflection session file from the working PC, but they will still need to install the Host certificate in the certificate store:

Information on secure connections:

https://www.microfocus.com/documentation/reflection-desktop/16-2/deployment-guide/ic-secure-tls.htm

Information on certificates:

https://www.microfocus.com/documentation/reflection-desktop/16-2/deployment-guide/ic-secure-rcm.htm

They could use the Microsoft Windows Certificate Manager to compare the stores on the system which works and the system which fails. I suspect the certificate stores are different.