WALTER WRIGHT 0 Posted February 15, 2017 Author Share Posted February 15, 2017 Connected - Mouse does not move to client screens. Windows 10 desktop 64bit as server. Galaxy Tab Pro 64bit Win 10 as client & Lenovo Thinkpad Win 7 32bit as client. Not sure how to fix. Link to post Share on other sites
Jeremy Bullis 0 Posted February 15, 2017 Share Posted February 15, 2017 Having the same problem but only with my Fedora 25 client pc. Synergy is working, but the mouse cursor will not appear. I am running 1.8.7 server on win7 and have a win7 and win10 client that work fine. I did try to downgrade synergy on the Fedora client to 1.8.5 but that did not fix the issue. Also tried disabling clipboard or file/drag/drop features but also no dice. Link to post Share on other sites
Tim Stefanski 0 Posted March 7, 2017 Share Posted March 7, 2017 Was there a solution for this ? I am having this same issue with fedora 25 server and win 7 client, both server and client are running V1.8.8-1 stable. Link to post Share on other sites
Rex Terry 2 Posted March 10, 2017 Share Posted March 10, 2017 I had the same experience. When arranging the clients on the Server Configuration screen, be sure you have located them adjacent to the Server. The Synergy Screen showed the clients as connected, but I just couldn't get the cursor to go there. My experience was that at first I could not move the cursor to the client, then I could onely move it from the opposite or wrong side of the server. After I rearranged the icons adjacent to the Server all worked perfectly. Again, I thank Karen Williams and Nick Bolton for their very kind assistance. Link to post Share on other sites
Jason Butterworth 0 Posted November 6 Share Posted November 6 Sorry to say but its RC3 and this issue has come back. All screens are adjacent to each other with the green bar between them. Mouse cursor will not switch to the remote screen. Link to post Share on other sites
Jason Butterworth 0 Posted November 6 Share Posted November 6 Log indicates remote client constantly disconnects. Link to post Share on other sites
Jason Butterworth 0 Posted November 6 Share Posted November 6 Solved it. Reset the remote config and it seems to have solved the problem. 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