Jump to content

beta 2.0.0.-beta4 - want connect to second pc


BARTRON

Recommended Posts

Hi, i have laptop and desktop,

 

i can see laptop connected on both synergy laptop and desktop

desktop cant connect moving green bar

my desktop ip is 192.168.7.10
my laptop ip is 192.168.7.16

log:
 

[ Config  ] [2017-09-16T20:55:05] ERROR: failed to start crash handler: Couldn't verify crash dump directory: No such file or directory

[ Config  ] [2017-09-16T20:55:05] INFO: log filename: /Users/bartron/Library/Preferences/Symless/Synergy/synergy.log

[ Config  ] [2017-09-16T20:55:05] DEBUG: connecting to service

[ Config  ] [2017-09-16T20:55:05] DEBUG: connected to service

[ Config  ] [2017-09-16T20:55:05] DEBUG: new added screen pos: 257 161

[ Config  ] [2017-09-16T20:55:07] DEBUG: Profile ID: 649 name: default

[ Config  ] [2017-09-16T20:55:07] DEBUG: requesting profile snapshot

[ Config  ] [2017-09-16T20:55:07] DEBUG: current version is update to date

[ Service ] [2017-09-16T20:55:07] debug: sending last profile snapshot

[ Service ] [2017-09-16T20:55:07] debug: config ui opened, forcing connectivity test

[ Service ] [2017-09-16T20:55:07] debug: new screens detected (2), preparing connectivity test

[ Service ] [2017-09-16T20:55:07] debug: starting connectivity test

[ Service ] [2017-09-16T20:55:07] debug: handling local profile screen set changed, mode=client

[ Service ] [2017-09-16T20:55:07] debug: tcp client connect error: Host is down

[ Service ] [2017-09-16T20:55:07] debug: connectivity test failed for 192.168.7.16:24810

[ Service ] [2017-09-16T20:55:10] debug: failed report: dest = 1246, ips = 10.253.0.6,10.253.2.3,10.253.4.2,10.253.5.3,10.253.6.2,10.254.0.138,172.16.253.6,192.168.7.16

[ Service ] [2017-09-16T20:55:10] debug: local profile modified, id=649

[ Service ] [2017-09-16T20:55:10] debug: comparing profiles, id=649 this=v2 other=v2

[ Service ] [2017-09-16T20:55:10] debug: profile screen test result changed, screenId=1246 success=``->`` failed=``->`10.253.0.6,10.253.2.3,10.253.4.2,10.253.5.3,10.253.6.2,10.254.0.138,172.16.253.6,192.168.7.16`

[ Service ] [2017-09-16T20:55:10] debug: handling new report from connectivity tester, screenId=1246 successfulIp= lastServerId=1246

[ Service ] [2017-09-16T20:55:10] debug: finished connectivity test

[ Service ] [2017-09-16T20:56:10] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:10] debug: connectivity test failed for 192.168.7.16:24810

[ Service ] [2017-09-16T20:56:10] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:10] debug: connectivity test failed for 172.16.253.6:24810

[ Service ] [2017-09-16T20:56:10] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:10] debug: connectivity test failed for 10.254.0.138:24810

[ Service ] [2017-09-16T20:56:10] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:10] debug: connectivity test failed for 10.253.6.2:24810

[ Service ] [2017-09-16T20:56:10] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:10] debug: connectivity test failed for 10.253.5.3:24810

[ Service ] [2017-09-16T20:56:10] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:10] debug: connectivity test failed for 10.253.4.2:24810

[ Service ] [2017-09-16T20:56:10] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:10] debug: connectivity test failed for 10.253.2.3:24810

[ Service ] [2017-09-16T20:56:10] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:10] debug: connectivity test failed for 10.253.0.6:24810

[ Service ] [2017-09-16T20:56:23] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:23] debug: connectivity test failed for 172.16.253.6:24810

[ Service ] [2017-09-16T20:56:23] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:23] debug: connectivity test failed for 10.254.0.138:24810

[ Service ] [2017-09-16T20:56:23] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:23] debug: connectivity test failed for 10.253.6.2:24810

[ Service ] [2017-09-16T20:56:23] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:23] debug: connectivity test failed for 10.253.5.3:24810

[ Service ] [2017-09-16T20:56:23] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:23] debug: connectivity test failed for 10.253.4.2:24810

[ Service ] [2017-09-16T20:56:23] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:23] debug: connectivity test failed for 10.253.2.3:24810

[ Service ] [2017-09-16T20:56:23] debug: tcp client connect error: Operation timed out

[ Service ] [2017-09-16T20:56:23] debug: connectivity test failed for 10.253.0.6:24810

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...