Why can't I connect via RDP to the server from the current session, which is also installed via RDP?

Question

RDP

There is a problem. The user works from home, remotely, and wants to connect via RDP to a server in another branch from his session, but cannot. There is such error:

And such piece not at one user.

At the same time, if you work on the same computer under the same user locally, i.e. internally, then connecting to a remote server in another branch occurs without problems.

As a result, while users use a very inconvenient crutch - they ask their colleagues to log in to their computer at the workplace, connect to the server, and only then they connect remotely to their computers and work.

It is very uncomfortable.

I don't understand how to solve this.

The server version in a Windows Server 2012R2 branch.

This is the error that goes in the "Application" logs:

Faulting Application Name: mstsc.exe, Version: 6.1.7601.24543, Timestamp: 0x5df1b0d3 Faulting Module
Name: rohos_cp.dll, Version: 3.9.0.0, Timestamp 0x5bfc4d71 Exception
Code: 0xc0000005 Error
Offset: 0x00033200 Faulting Process ID
: 0x3dc
Faulting application path: 0x01d7a4b76712d84b Faulting application
path: C:\Windows\system32\mstsc.exe Faulting
module path: C:\Windows\system32\rohos_cp.dll
Report code: a58d983b-10aa-11ec-9640-ac220b299330

I.e. obviously here in the subject is also the Rohos Logon Key software, which we use for two-factor authorization.
I already wrote technical support for Rojos, but suddenly someone came across and will answer faster.

Answer 1

And what OS and clients do users have at home and at work?
1. Your particular user has Windows 7 SP1 and the RDP client is most likely version 8.0. Nested (multi-hop) RDP sessions are not supported in this combination .
2. You can update the RDP client for users on home systems to version 8.1 (if they have Windows 7). Installation order - KB2574819, KB2830477, KB2857650, KB2913751
3. Alternatively, raise a separate session to the server in the branch

Answer 2

without 2 factor check... at least 3 "nested" RDPs work for me, though I have a "patched" version of the RDP dll