Server IP on client Synergy configs not saving

[Scott B 0]

"Server IP" configured on the client Synergy settings not saving after I reboot the Mac.

SERVER - Windows 7 v10.12.5 64bit OS - running V1.8.8-stable-25a8cb2 Synergy

CLIENT - macOS Sierra - running v1.8.8-stable-25a8cb2 Synergy

both connected via Ethernet to same LAN segment. 

[Paul Suarez 1]

Have you already added Synergy as a log-in item on your Mac?

[jlepage 0]

Scott B: are you entering the server name or the server IP?

I was having a similar problem. 

I have an Ubuntu system as my server, clients are Win7 and MacOS Sierra (10.12.6).

In the past I was able to save a server _name_ (as opposed to server IP) on my Mac, and this still works on my Win7 client.  However, on Mac I must now use the IP (not the server _name_).  Entering the server _name_ works fine in the session, but on reboot the server name has been forgotten.  

Once the server IP is entered and saved, it works fine.  Further attempts to save the server _name_ (rather than the server IP) fail, and only the server IP is ever retained.  

[Nick Bolton 359]

Hello,

Please could you email us? [email protected]

I posted something earlier about forum support...

https://symless.com/forums/topic/3756-were-improving-our-tech-support/

Thanks,
Nick

[Alex V 0]

On 6/23/2017 at 4:45 PM, Scott B said:

"Server IP" configured on the client Synergy settings not saving after I reboot the Mac.

SERVER - Windows 7 v10.12.5 64bit OS - running V1.8.8-stable-25a8cb2 Synergy

CLIENT - macOS Sierra - running v1.8.8-stable-25a8cb2 Synergy

both connected via Ethernet to same LAN segment. 

I have the exact same issue 
(except using macOS High Sierra)

 

[Robert H 0]

This is a problem that has been in Synergy since early versions. I've been using Synergy since 2006. Full disclosure, I bought v2 but don't use it; it has another host of issues, some of these 1.8 issues may be resolved.

Every instance of Synergy I've ever had, I've had this issue as you describe. Settings like the server for the client or, even more annoyingly, the license. So I cannot even connect until I get my license code on that machine again, and re-insert it so I can connect via SSL. I've considered just ditching the UI and sticking to command line, using scripts to start/stop etc, but not sure how that would work. So, I've purchased some 10GigE cards so I can just X Forwarding between my workstations, since Synergy is wonky. Look- I'm not saying Synergy is wonky on just a handful of platforms. Here's some math:
- I started using Synergy in 2006
- I've never had less than 3 machines
- None of my workstations have ever gone more than two years without a fresh install, new hardware, etc.

Thus I've had issues with saving configuration on probably more than 36 installs. Nothing complicated about my setup. Over the years I've stuck to Arch, Debian and Fedora; main stream distributions. I don't hack the software or try to do something with it other than the basics. I don't modify the default settings except to occasionally disable clipboard sharing.

I think Synergy is a great idea, but I would say 1/10 times you start it you're going to have to *something*.