Keyboard doesn't work when jumping in RDM

Hello Andrew,

Regarding the keyboard issue I wasn't able to reproduce the issue. If I understand correctly when you mean the "2nd Box" This is the RDP session on the Jump server, right?

Did you try to recreate the two sessions, directly in RDM 13.0.6 to see if it's working?
What OS is the Jump host and does RDM on the Jump host is also RDM 13.0.6 or 11.5.4?

Best regards,

Yes, the 2nd box is the RDP session on the jump host.

Yes, I've tried with and without jumping in RDM 13.0.6 -- without meaning two manual RDM connections: local to jump host, then jump host to 2nd box. Results for without jumping are mixed -- the keyboard works fine for me but NOT for my coworkers.

As with any bug report, you may need to ignore some of the data points that are unhelpful for debugging.

Timeline w/ version info:
* All boxes had version 11.5.4 until recently -- local and jump host.
* Jump host was updated first to 13.0.6.
* Keyboard input stopped working on the second RDP connection from the jump host.
* Local versions were updated to 13.0.6, per recommendation of customer support.
* Keyboard input still doesn't work consistently.

OS info:
* Local boxes are all Windows 7
* Jump host is Server 2008 R2 Standard
* 2nd boxes are Server 2012 R2 Standard

Random note:
I have a hunch it is related to the new style of windows UI (typical start orb opens the full-screen tiles menu).

Hi,

On your Windows 7 computer as well as on the remote server, could you try the following;

Let me know if that help.

I've confirmed "Turn on Filter Keys" was already disabled on many boxes:
* My local box
* 3 or 4 jump hosts
* 5 or 6 remote boxes (the host after jumping)

So that doesn't appear to be related. What other ideas do you have?

Attached is a screenshot of my workaround to "fix" the keyboard not working:
* Right click the jump host's task bar

When you go back to the 2nd host tab, everything works fine.

Hi,

We had a similar issue with another customer "Robert B" and here is the solution that works for him?

Have upgraded my RDP/mstsc to version 8.1 , which has resolved the issue:
KB’s must be installed in the following order: KB2574819, KB2830477, KB2857650, KB2913751, KB2923545


Best regards,

Ahhh. That's a start.

Do these need to be installed on all boxes -- local, jump hosts, and remote hosts?

Hi,

Based on the customer information we received, you only need to perform these steps on your local computer.

That being said, it could be a good idea to confirm that the Jump and the remote host have MSTSC 8.1 if the issue is still there.

Best regards,

Hi David

I currently have the same issue.
Updating my local MSTSC is n/a since I'm running Windows 10.
The jump host is an older machine, however (Win 2008 R2) But currently I'm unable to upgrade, depending on others to do that

The workaround with the taskbar works for me, however only for 1 machine. If I'm connecting to 2 machines through the same jump host, I can use the taskbar trick to focus keyboard on the first subentry. but as I close it, the 2nd one cannot get any input whatsoever.

if I start typing, the input goes to the Searchbox of the RDM in jump host, see picture.
the 2nd entry is so much frozen that I have to use a normal mstsc from the jump host to reconnect, then logoff (keyboard works in that manual mstsc but that is not the intention for me buying the RDM)..



Regards, Ben van Zanten

@Ben van Zanten


What version of RDM are you using?

Just to test, could you please enable/disable the "Grab the Keyboard Input" setting at the bottom right of RDM?



Best regards,

Thanks Mark for your quick reply
I'm running 13.6.7.0 on my local machine. The jump server was 13.6.6.0 I believe...
I did try the grab keyboard input on both my local machine and in the jump host, but that did not help (or make it even worse, have to test that further).

The good news, however is that our management server we use as jump host is scheduled for upgrade/replacement to a WS2016 next week already, so I'll test then, and come back with the result.
the current jump server was a WS2008R2 and its installed MSTSC version was 6.1 so the upgrade should help.

Regards, Ben

Hello,

Thank you for your reply.

Please let us know of your findings with the newer versions


Best regards,