Share this post

Link to post

Share on other sites

Paul Suarez 2

Label doesn't really matter @Jeff W.. You can just press any keyboard buttons or mouse buttons on your Windows 10 machine and it'll inform the client machine(s) to treat you as the server. If that doesn't work, try pressing F12 while Synergy's interface is up.

Share this post

Link to post

Share on other sites

ZERO 0

I had the same problem what i did was i delete the application data on both ends then stated up the server first then the client for windows the location of the profile data is C:\Users\YourUserName\AppData\Local\Symless Hope that helps also please note that you can only use the mouse from the server not from client to server

Share this post

Link to post

Share on other sites

Jeff W. 0

today I first ran into the "issue with your version is out of support" and found that somebody was actually able to find the download link since support doesn't seem to care about responding to anybody. after getting that part fixed I then then tried the above and no luck, did a full removal of the software and re-installed with no luck.

It does look like this new version the F12 button does actually work now as I can see it in the logs where before it did nothing.

but still it doesn't work. If I make the Macbook the server then I am able to take the mouse/keyboard from the Macbook to the windows machine though.

I really want this to work but is very frustrating, I'm not really mad at any support person... just wish you had more support rep's available to your customers.

as you can tell your customer base also wants this to work due to the amount of posts on your support site.

Share this post

Link to post

Share on other sites

Jeff W. 0

another update - completely removed Synergy v2 off both my Mac and Windows box and downloaded a fresh installer of 1.8(synergy-v1.8.8-stable-25a8cb2-Windows-x64.msi & synergy-v1.8.8-stable-25a8cb2-MacOSX-x86_64.dmg) to try and get back to a stable build and actually experienced the same issue. started going through firewall logs, etc. since I figured maybe there was a related issue. found some people experiencing the same issue in v1.8.8 so I went down to v1.8.7 on my windows box and voila it works.

This info could probably be useful to your devs as whatever they find to fix 1.8 will probably fix v2.

Share this post

Link to post

Share on other sites

Paul Suarez 2

Hi @Jeff W.. It would be best to wait for the fix our developers are working on since there's an ongoing issue with the v2 Beta right now. ETA will be tomorrow.

11 hours ago, Paul Suarez said:

I'm really sorry for the late reply on this everyone. The whole team is aware of the problem now. Our developers are on the move and confirmed that it'll be fixed tomorrow. Please bear with us on this.