Ray Barbieri 1 Posted October 19, 2017 Share Posted October 19, 2017 (edited) I think the s/w got confused by having windows 10 hyper-v on one of the two machines. In the logs I can see the second computer trying to connect to the first computer's "public" IP. I've turned off that interface, re-installed but since everything is stored in the cloud, it still keeps trying to connect to that. There are no controls so no way to remove the info on the cloud. Machine 1 logs: https://synergy-logs.symless.com/2017-10-19/8228-2017-10-18T18-49-09.log Machine 2 logs: https://synergy-logs.symless.com/2017-10-19/8228-2017-10-18T19-02-12.log Both are on same subnet and connected to same switch. Edited October 19, 2017 by Ray Barbieri Added 2nd log file Link to post Share on other sites
Jaxon 0 Posted October 19, 2017 Share Posted October 19, 2017 I have basically the same problem on a laptop that also runs VMware pro. Link to post Share on other sites
Ray Barbieri 1 Posted October 20, 2017 Author Share Posted October 20, 2017 I believe the information in the cloud is incorrect and would like a mechanism to remove/clear that information so I can start over from scratch. For now, I am forced to go back to Synergy 1 as I have to use these systems and there's no solution available yet. 1 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