#1
|
||||
|
||||
![]()
Introduction
A very small number of individuals have recently reported that when they attempt to access SecureCRT (running on Linux) through an RDP/VNC connection, the keyboard mapping is incorrect. Meanwhile, when accessing SecureCRT directly on the Linux machine (not through a remote RDP/VNC connection) the keyboard works just fine. If you find yourself in a similar situation, here's some background info and steps you can consider taking to resolve the problem. Symptoms Here's a description of what has been reported:
Cause: This problem is caused by RDP/VNC client/server implementations that are not implemented/configured to support the XKEYBOARD extension.
Possible Fixes: While SecureCRT cannot force an RDP/VNC client/server implementation to support the XKEYBOARD extension that Qt requires, there are some steps you can take to potentially resolve the problem:
__________________
Jake Devenport VanDyke Software Technical Support YouTube Channel: https://www.youtube.com/vandykesoftware Email: support@vandyke.com Web: https://www.vandyke.com/support |
![]() |
Tags |
knowledgebase , rdp , securecrt , vnc |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|