Cheryl Lomedico 3 Posted October 17, 2017 Share Posted October 17, 2017 "server" is Win 10 "client" is Mac OS X Sierra During 1st round of troubleshooting, I opened port 24810. This worked fine yesterday. Today, it is not working. Saw a posting that also needs 24800. Did this and still not working. Win 10 (hostname: SUP-601) is green but Mac (GOS-1345-FTE) looks like it connects but just spins. Log files: SUP-601 (windows 10) ----------------------- [ Core ] [2017-10-17T10:59:56] DEBUG: active sides: 4 [ Core ] [2017-10-17T10:59:56] DEBUG: active sides: 4 [ Core ] [2017-10-17T10:59:56] DEBUG: desk Default window is 0x00070716 [ Core ] [2017-10-17T10:59:56] DEBUG: switched to desk "Default" [ Core ] [2017-10-17T10:59:56] DEBUG: desktop is now accessible [ Core ] [2017-10-17T10:59:56] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1 [ Core ] [2017-10-17T10:59:56] NOTE: started server, waiting for clients [ Core ] [2017-10-17T10:59:56] DEBUG: event queue is ready [ Service ] [2017-10-17T10:59:57] debug: failed report: dest = 16558, ips = 129.21.227.14 [ Service ] [2017-10-17T10:59:57] debug: local profile modified, id=7848 [ Service ] [2017-10-17T10:59:57] debug: comparing profiles, id=7848 this=v9 other=v9 [ Service ] [2017-10-17T10:59:57] debug: profile screen test result changed, screenId=16558 success=``->`` failed=``->`129.21.227.14` [ Service ] [2017-10-17T10:59:57] debug: handling new report from connectivity tester, screenId=16558 successfulIp= lastServerId=15518 [ Service ] [2017-10-17T10:59:57] debug: finished connectivity test [ Core ] [2017-10-17T10:59:56] DEBUG: add pending events to buffer [ Core ] [2017-10-17T10:59:56] DEBUG: screen "SUP-601" shape changed [ Service ] [2017-10-17T11:00:03] debug: comparing profiles, id=7848 this=v9 other=v9 [ Service ] [2017-10-17T11:00:03] debug: profile screen test result changed, screenId=16558 success=``->`` failed=`129.21.227.14`->`` [ Service ] [2017-10-17T11:00:03] debug: profile screen active changed, screenId=15518 false->true [ Service ] [2017-10-17T11:00:03] debug: new screens detected (1), preparing connectivity test [ Service ] [2017-10-17T11:00:03] debug: profile changed, storing local copy [ Service ] [2017-10-17T11:00:03] debug: comparing profiles, id=7848 this=v9 other=v9 [ Service ] [2017-10-17T11:00:03] debug: profile screen status changed, screenId=15518 Connected->Connecting [ Service ] [2017-10-17T11:00:03] debug: profile changed, storing local copy [ Service ] [2017-10-17T11:00:03] debug: comparing profiles, id=7848 this=v9 other=v9 [ Service ] [2017-10-17T11:00:03] debug: profile has not changed, no action needed [ Service ] [2017-10-17T11:00:03] debug: comparing profiles, id=7848 this=v9 other=v9 [ Service ] [2017-10-17T11:00:03] debug: profile screen status changed, screenId=15518 Connecting->Connected [ Service ] [2017-10-17T11:00:03] debug: profile changed, storing local copy [ Service ] [2017-10-17T11:00:15] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [ Service ] [2017-10-17T11:00:15] debug: connectivity test failed for 129.21.227.14:24810 Â GOS-1345-FTE (Mac os X sierra) ----------------- [ Config ] [2017-10-17T11:00:09] ERROR: failed to start crash handler: Couldn't verify crash dump directory: No such file or directory [ Config ] [2017-10-17T11:00:09] INFO: log filename: /Users/cmwacc/Library/Preferences/Symless/Synergy/synergy.log [ Config ] [2017-10-17T11:00:09] DEBUG: connecting to service [ Config ] [2017-10-17T11:00:09] DEBUG: connected to service [ Config ] [2017-10-17T11:00:10] DEBUG: new added screen pos: 257 161 [ Config ] [2017-10-17T11:00:11] DEBUG: Profile ID: 7848 name: default [ Config ] [2017-10-17T11:00:11] DEBUG: current version is update to date [ Config ] [2017-10-17T11:00:11] DEBUG: requesting profile snapshot [ Service ] [2017-10-17T11:00:11] debug: sending last profile snapshot [ Service ] [2017-10-17T11:00:11] debug: config ui opened, forcing connectivity test [ Service ] [2017-10-17T11:00:11] debug: new screens detected (2), preparing connectivity test [ Service ] [2017-10-17T11:00:11] debug: starting connectivity test [ Service ] [2017-10-17T11:00:11] debug: handling local profile screen set changed, mode=client [ Service ] [2017-10-17T11:00:14] debug: failed report: dest = 15518, ips = 129.21.227.7 [ Service ] [2017-10-17T11:00:14] debug: local profile modified, id=7848 [ Service ] [2017-10-17T11:00:14] debug: comparing profiles, id=7848 this=v9 other=v9 [ Service ] [2017-10-17T11:00:14] debug: profile screen test result changed, screenId=15518 success=``->`` failed=``->`129.21.227.7` [ Service ] [2017-10-17T11:00:14] debug: handling new report from connectivity tester, screenId=15518 successfulIp= lastServerId=15518 [ Service ] [2017-10-17T11:00:14] debug: finished connectivity test [ Service ] [2017-10-17T11:01:18] debug: tcp client connect error: Operation timed out [ Service ] [2017-10-17T11:01:18] debug: connectivity test failed for 129.21.227.7:24810 [ Service ] [2017-10-17T11:01:26] debug: tcp client connect error: Operation timed out [ Service ] [2017-10-17T11:01:26] debug: connectivity test failed for 129.21.227.7:24810 Â Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted October 31, 2017 Synergy Team Share Posted October 31, 2017 Finally, Synergy 2Â beta5 is here! Could you give it a try? Get the latest version:Â Synergy-v2.0.0-beta5 Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now