wazer

Synergy 2 not working between 2 machines.

7 posts in this topic

Wazer, both win, right? First check that scroll--lock is off on both sides. then run through the Troubleshooting guide stickies at the top of the forum. Start here: 

https://symless.com/forums/topic/4167-preliminary-troubleshooting/

If you are Win><Win give special attention to the Windows Firewall settings on both sides:

 

https://symless.com/forums/topic/4208-how-to-use-with-windows-firewall/#comment-17610

Keep us posted on your progress

 

 

Share this post


Link to post
Share on other sites

Just paid and downloaded Synergy 2 Beta (Synergy_v2.0.0-beta4_b987-042356d4) and have it loaded on two Windows 10 Systems. One running build 1703 and the other running Consumer preview 1709. Synergy 1.87 worked fine. Both were loaded on fresh installs (uninstalled old and rebooted).

Synergy 2 sees both systems but do not switch between them.

Server Log:

Quote

017-10-10T18:51:22] INFO: drag and drop enabled

[ Core ] [2017-10-10T18:51:22] DEBUG: opening configuration "C:\Users\PlexAdmin\AppData\Local\Symless\Synergy\synergy.conf"

[ Core ] [2017-10-10T18:51:23] DEBUG: configuration read successfully

[ Core ] [2017-10-10T18:51:23] ERROR: failed to get desktop path, no drop target available, error=2

[ Core ] [2017-10-10T18:51:23] DEBUG: screen shape: -1280,0 3200x1200 (multi-monitor)

[ Core ] [2017-10-10T18:51:23] DEBUG: window is 0x00080210

[ Core ] [2017-10-10T18:51:23] DEBUG: adopting new buffer

[ Core ] [2017-10-10T18:51:23] DEBUG: opened display

[ Core ] [2017-10-10T18:51:23] DEBUG: active sides: 10

[ Core ] [2017-10-10T18:51:23] DEBUG: active sides: 10

[ Core ] [2017-10-10T18:51:23] DEBUG: desk Default window is 0x0006018a

[ Core ] [2017-10-10T18:51:23] DEBUG: switched to desk "Default"

[ Core ] [2017-10-10T18:51:23] DEBUG: desktop is now accessible

[ Core ] [2017-10-10T18:51:23] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1

[ Core ] [2017-10-10T18:51:23] NOTE: started server, waiting for clients

[ Service ] [2017-10-10T18:51:24] debug: comparing profiles, id=5679 this=v20 other=v20

[ Service ] [2017-10-10T18:51:24] debug: profile screen status changed, screenId=11146 Connected->Connecting

[ Service ] [2017-10-10T18:51:24] debug: profile changed, storing local copy

[ Core ] [2017-10-10T18:51:23] DEBUG: event queue is ready

[ Core ] [2017-10-10T18:51:23] DEBUG: add pending events to buffer

[ Core ] [2017-10-10T18:51:23] DEBUG: screen "MYSVR" shape changed

[ Service ] [2017-10-10T18:51:26] debug: comparing profiles, id=5679 this=v20 other=v20

[ Service ] [2017-10-10T18:51:26] debug: profile screen status changed, screenId=11146 Connecting->Connected

[ Service ] [2017-10-10T18:51:26] debug: profile changed, storing local copy

[ Config ] [2017-10-10T18:51:39] INFO: Sending log file...

[ Config ] [2017-10-10T18:51:41] INFO: Upload path: https://synergy-logs.symless.com/2017-10-10/5687-2017-10-10T18-51-40.log

Client Log:

Quote

[ Config  ] [2017-10-10T18:51:09] ERROR: failed to start crash handler: Couldn't verify crash dump directory: The system cannot find the file specified
[ Config  ] [2017-10-10T18:51:09] INFO: log filename: C:/Users/Richard/AppData/Local/Symless/Synergy/synergy.log
[ Config  ] [2017-10-10T18:51:09] DEBUG: connecting to service
[ Config  ] [2017-10-10T18:51:10] DEBUG: connected to service
[ Config  ] [2017-10-10T18:51:13] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-10T18:51:15] DEBUG: current version is update to date
[ Config  ] [2017-10-10T18:51:15] DEBUG: Profile ID: 5679 name: default
[ Config  ] [2017-10-10T18:51:15] DEBUG: requesting profile snapshot
[ Service ] [2017-10-10T18:51:15] debug: connecting websocket
[ Service ] [2017-10-10T18:51:16] error: can't send profile snapshot, not yet received from cloud
[ Service ] [2017-10-10T18:51:17] debug: websocket connected
[ Service ] [2017-10-10T18:51:17] debug: comparing profiles, id=-1 this=v-1 other=v19
[ Service ] [2017-10-10T18:51:17] debug: profile id changed, -1->5679
[ Service ] [2017-10-10T18:51:17] debug: profile name changed, ->default
[ Service ] [2017-10-10T18:51:17] debug: profile server changed, -1->11146
[ Service ] [2017-10-10T18:51:17] debug: profile screen set changed, added=2 removed=0
[ Service ] [2017-10-10T18:51:17] debug: new screens detected (2), preparing connectivity test
[ Service ] [2017-10-10T18:51:17] debug: starting connectivity test
[ Service ] [2017-10-10T18:51:17] debug: profile changed, storing local copy
[ Service ] [2017-10-10T18:51:17] debug: handling local profile server changed, mode=unknown thisId=11151 serverId=11146 lastServerId=-1
[ Service ] [2017-10-10T18:51:17] debug: starting core client process
[ Service ] [2017-10-10T18:51:17] error: aborting client start, no successful connectivity test results
[ Service ] [2017-10-10T18:51:17] debug: handling local profile screen set changed, mode=client
[ Service ] [2017-10-10T18:51:20] debug: failed report: dest = 11146, ips = 192.168.1.110
[ Service ] [2017-10-10T18:51:20] debug: local profile modified, id=5679
[ Service ] [2017-10-10T18:51:20] debug: comparing profiles, id=5679 this=v19 other=v19
[ Service ] [2017-10-10T18:51:20] debug: profile screen test result changed, screenId=11146 success=``->`` failed=``->`192.168.1.110`
[ Service ] [2017-10-10T18:51:20] debug: handling new report from connectivity tester, screenId=11146 successfulIp= lastServerId=11146
[ Service ] [2017-10-10T18:51:20] debug: finished connectivity test
[ Service ] [2017-10-10T18:51:38] 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-10T18:51:38] debug: connectivity test failed for 192.168.1.110:24810
[ Service ] [2017-10-10T18:51:41] debug: comparing profiles, id=5679 this=v19 other=v20
[ Service ] [2017-10-10T18:51:41] debug: profile screen test result changed, screenId=11146 success=``->`` failed=`192.168.1.110`->``
[ Service ] [2017-10-10T18:51:41] debug: profile screen position changed, screenId=11151 347,146->264,204
[ Service ] [2017-10-10T18:51:41] debug: profile changed, storing local copy
[ Service ] [2017-10-10T18:51:41] debug: handling local profile screen position changed, mode=client
[ Service ] [2017-10-10T18:51:47] debug: comparing profiles, id=5679 this=v20 other=v20
[ Service ] [2017-10-10T18:51:47] debug: profile screen status changed, screenId=11146 Connected->Connecting
[ Service ] [2017-10-10T18:51:47] debug: profile changed, storing local copy
[ Service ] [2017-10-10T18:51:49] debug: comparing profiles, id=5679 this=v20 other=v20
[ Service ] [2017-10-10T18:51:49] debug: profile screen status changed, screenId=11146 Connecting->Connected
[ Service ] [2017-10-10T18:51:49] debug: profile changed, storing local copy

Hooked up physical KVM until issue resolved. I will leave them running for debugging purposes.

I really miss the configuration screen in version one. You feel like your doing something; automatic is not "easier" to an admin.

Share this post


Link to post
Share on other sites

Richard, Win 2 Win setup should be working well with beta 4. Check out the stickies at the top of the forum for troubleshooting tips. My first suspicion would be Windows Firewalls. check out this: 

https://symless.com/forums/topic/4208-how-to-use-with-windows-firewall/#comment-17610

Also, that first connection with the Symless cloud server is not instant. it may take a couple of minutes. if 5 have gone by, something else is broken. Let us know your progress.

Share this post


Link to post
Share on other sites

I am getting the same issue, I have 1 PC and 1 Mac, I have tried adding exceptions to my firewall on my PC and disabling it completely, neither worked. I see both computers and my PC is lit green. Strangely if i move the mouse and keyboard to the mac and hit F-12(i believe that tries to force that machine to be the server they will not connect)

Share this post


Link to post
Share on other sites

This should be no issue with Windows to Windows. I have checked the firewalls and synergy 2.0 is already there. I have even disabled them both like Chase did. No luck. I remember having to turn encrypted connection off on Synergy 1 (to be stable)...is that the same here?

Where can I set hotkeys like in version 1?

Share this post


Link to post
Share on other sites

When the Synergy beta 4 makes a connection with the Symless cloud server, it reads the credentials on both and makes a secure (SSL) connection. 

Synergy beta 4 is not Synergy 2. it is an incompletely developed test version for beta testers to try and report back about. Many users have 'bought in' to the beta program and stepped back to the stable version 1 waiting for the full version 2 or to test the next beta, beta 5. They still, of course still have a financial consideration for the final version of Synergy 2. It should be on the market about the end of the year.

That said, the goal of Synergy 2 is that a user installs it and it auto-configures and works without the user having to intervene. Even to select a server.

There will be access to a console for administrative control for specific cases, but most users won't ever see it.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now