Quantcast
Channel: Synergy Q&A - latest questions
Viewing all articles
Browse latest Browse all 1341

Connection between Windows 7 and OS X 10.6.8 suddenly stopped working

$
0
0

I've been using Synergy for quite awhile without issue between a Windows 7 Synergy client and OS X 10.6.8 Synergy server. Suddenly, last night it stopped working. I was running 1.4.12 on both nodes. The connection from Windows 7 appears to be established but, according to the log, after 15 seconds or so it times out. On the Mac, the log doesn't show any connection from a client. Here's what I've tried so far:

  • Updating to 1.4.14 on both client and server (unsuccessful)
  • Disable firewalls on both client and server (unsuccessful)
  • ping from Windows to Mac (successful)
  • ssh from Windows to Mac (successful)
  • Telnet from Windows 7 to Mac on port 24800 (connection appears to be established)
  • Telnet from Mac to localhost on port 24800 (connection appears to be established)
  • Telnet from Linux system to Mac on port 24800 (connection appears to be established)
  • Change port from 24800 to 10000 (unsuccessful)
  • Change Mac ip address to static instead of DHCP (unsuccessful)
  • Disable encryption (unsuccessful)
  • Reverse client/server roles. Windows 7 as server and Mac as client (unsuccessful)
  • Completely uninstall Synergy on both computers, reboot, re-install (unsuccessful)

With debug logging enabled I observed the following:

  • Windows 7 as server
    • a connection was established
    • "hello" message was sent from Windows 7 to OS X
    • waiting for response and then timeout (apparently no response received)
    • On OS X log, a connection is established but no further communications.
  • OS X as server

    • client established a connection
    • waited for "hello" message
    • timeout
    • On OS X log, no connection message appears.

It appears that Synergy on the Mac has just stopped communicating (even after deleting Synergy, rebooting and starting a new version). As far as I can tell nothing else changed on either system when the problem occurred. It just stopped working and hasn't worked since. Any help would be greatly appreciated.


Viewing all articles
Browse latest Browse all 1341

Trending Articles