Help save net neutrality! Learn more.
Close

#1256 Shift / Backspace key not detect to VMware and Remote Desktop with 64 bit VNC server

open
nobody
None
5
2015-03-09
2013-06-21
tongkai
No

Setting:
PC A: Windows 7 64 bit, install tightvnc 64 bit, remote to "PC B"
PC B: Windows 7 64 bit, install tightvnc 64 bit, enable Remote Desktop, VM Workstation "PC D"
PC C: Windows 7 32 bit, install tightvnc 32 bit, remote to "PC B"
PC D: Windows XP 32 bit VM under PC B

Tightvnc version tested: 2.7.1, 2.7.7 both 32 & 64 bit

symptom:
I usually remote to PC B with PC A, but find that I cannot use Shift / Backspace key inside VM workstation windows when remote under PC B,

Keyboard normal when direct VNC from PC A to PC D

Shift / Backspace key not work when PC A Remote Desktop to PC B then click inside VM workstation or direct remote desktop to PC B

PC C do not have any problem when VNC or remote desktop to PC B and PC D

try uninstall tightvnc in PC A and install 32 bit tightvnc, cannot slove the problem
try uninstall tightvnc in PC B and install 32 bit tightvnc, key work again

so now the workaround is I reinstall all system with 32 bit tightvnc

Discussion

  • tongkai

    tongkai - 2013-06-21

    more testing:
    use teamviewer to access PC B and the VM inside (PC D), NO keyboard error.

    its seems that if you have VM in a PC, you need to use 32 bit VNC to make it "work" with the VM inside .

    this error only happen if you mix using remote desktop and VNC and VM, VNC to VNC have NO error

     
  • Michael Ridenour

    I have further information on this. After installing a number of different combinations of versions I have discovered the following.

    It started with v2.7.1: When remoting from "PC A" to "PC B", then starting Remote Desktop on "PC B" to connect to a terminal server, it will type all caps, plus backspace, tab, and caps keys do not work.

    With 2.7.3 through 2.7.10 (current): When remoting from "PC A" to "PC B", then starting Remote Desktop on "PC B" to connect to a terminal server, it will type in lower case, but backspace, tab, and caps keys do not work. If you turn on Caps Lock it will type capitals.

    It does not matter what version of TightVNC the local machine is running; the problem is on the remote machine.

    This all worked properly through the 2.6 series. As stated by tongkai, installing 32 bit TightVNC on a 64 bit system will allow these functions to work properly, and is a valid workaround.

     
  • Duane

    Duane - 2013-12-18

    I second this analysis - NONE of the 2.7 series will pass characters other than a-z, A-Z, 0-9. Basically, no shift, backspace or control characters when relaying a connection to RDP.

    Michael has a very accurate description..... When remoting from "PC A" to "PC B", then starting Remote Desktop on "PC B" to connect to a terminal server, it will type in lower case, but backspace, tab, and caps keys do not work. If you turn on Caps Lock it will type capitals.

     
  • Duane

    Duane - 2013-12-18

    PS - In my case, PC-A (Win7) opens TightVNC 2.7.10 session to PC-B (Win7). Then, on PC-B, open RDP session to PC-C (Win7 Virtual client running on Xen 6.2 Server).

    Althought PC-C is a virt, it appears that RDP to ANY Win7 pc fails to pass the keys. I believe the problem is relaying the keys from VNC to the RDP Client window on PC-B.

     
  • pdh0710

    pdh0710 - 2014-04-15

    (Please excuse my English)
    My setting is... server:win7x64, client:win7x64, both installed tightvnc 2.7.10 64bit. VirtualBox is also installed at server, and there's a win7x32 guest machine in VirtualBox.
    When I tried client -> server -> VirtualBox -> guest win7x32, the backspace key did not act at all on guest win7x32.
    So I'm now using another vnc program and no backspace key problem. Although the another vnc has other problems, the backspace key problem is more serious.

     
  • Anonymous - 2015-03-09

    I too am having this issue. My company happens to be a software vendor so though I am an admin on my own network, I am not an admin on our clients' networks and so I cannot install VNC nor open ports on our customers' servers. Many of our customers use VPN software that does not establish a connection when the connecting PC is being accessed through MS built-in RDP. When working from home, I must remote into my work PC through VNC, and then connect to the customers VPNs and RDP into their servers. It is a real pain having to switch on and off caps lock and use Left + Del to backspace.

     

Log in to post a comment.