Quantcast
Viewing all articles
Browse latest Browse all 1341

Keyboard doesn't work with Synergy 1.4.10, OS X 10.8 Server, Windows 8 Pro Client

(This sounds like a dup of several other questions on this site; unfortunately, they all deal with older versions of the operating systems, and I couldn't "translate" the suggested fixes...)

Environment: Synergy 1.4.10, OS X 10.8.2 Mountain Lion server. Windows 8 Pro client (final release, not Consumer Preview, in case that matters).

After configuring Synergy, I'm able to move the mouse on my Windows 8 client machine, but most keyboard input is ignored. Keyboard input that isn't ignored includes the Command/Windows key, which launches the Start screen, and alt/option, which would normally enable keyboard access to the Windows menu bar, shift, and control (only known because of the Debug2 messages; see below). Alphanumerics, arrow keys, shortcut keys, etc., all don't work. (At least the ones that I've tried.)

So far this sounds like Mac Server Keyboad does not work on Windows Client, except that I do have access for assistive devices enabled (now found at System Preferences > Accessibility).

I also found Keyboard not working at PC (client) from OSX 10.8 (server), but my client machine isn't a Mac running Bootcamp, and I don't know what alternate keyboard to try on Windows 8. I have tried using the U.S. Extended and U.S. Extended - PC keyboard layouts on the Mac, but those have had no affect.

I also found the Using Synergy with Mountain Lion and Windows 8 blog. I've followed the suggested setup, and it still doesn't work. The ports match on the client and server (otherwise the mouse wouldn't work), Synergy is getting through the respective firewalls (otherwise the mouse wouldn't work), and my network allows traffic (otherwise the mouse wouldn't work ;-).

Finally, I've enabled Debug2 level logging on the Mac Server. As best as I can determine, it isn't sending keyboard events at all:

# mouse move messages...
DEBUG2: writef(DMMV%2i%2i)
DEBUG2: wrote 8 bytes
DEBUG2: msg from "win8": CNOP
DEBUG2: no-op from
DEBUG2: mouse move +836,+529
DEBUG2: onMouseMoveSecondary -4,+4
DEBUG2: move on win8 to 674,167
DEBUG2: send mouse move to "win8" 674,167

# Client/server sync messages?
DEBUG2: msg from "win8": CALV
DEBUG2: msg from "win8": CNOP
DEBUG2: no-op from
DEBUG2: checking clipboard
DEBUG2: flags: 0
DEBUG2: checking clipboard
DEBUG2: flags: 0
DEBUG2: checking clipboard
DEBUG2: flags: 0
DEBUG2: writef(CALV)
DEBUG2: wrote 4 bytes

# Pressing the Command key
DEBUG1: event: Key event kind: 12, keycode=55
DEBUG1: mask: 100108
DEBUG1: new mask: 0x0010
DEBUG1: onKeyDown id=61419 mask=0x0010 button=0x0038
DEBUG1: send key down to "win8" id=61419, mask=0x0010, button=0x0038
DEBUG2: writef(DKDN%2i%2i%2i)
DEBUG2: wrote 10 bytes
DEBUG2: msg from "win8": CNOP
DEBUG2: no-op from
DEBUG1: event: Key event kind: 12, keycode=55
DEBUG1: mask: 0100
DEBUG1: new mask: 0x0000
DEBUG1: onKeyUp id=61419 mask=0x0000 button=0x0038
DEBUG1: send key up to "win8" id=61419, mask=0x0000, button=0x0038
DEBUG2: writef(DKUP%2i%2i%2i)
DEBUG2: wrote 10 bytes
DEBUG2: msg from "win8": CNOP
DEBUG2: no-op from
DEBUG2: checking clipboard
DEBUG2: flags: 0
DEBUG2: checking clipboard
DEBUG2: flags: 0

Looking through the output, the only buttons that are listed in onKeyDownmessages are 0x003b (alt) 0x003c (control), 0x0038 (command), 0x0039 (shift). No other keys are sent.

Suggestions on how to fix this? Thanks.


Viewing all articles
Browse latest Browse all 1341

Trending Articles