Bobby Thompson

Quit & Restart Synergy???

9 posts in this topic

It's very common for me to need to quit and restart the synergy 1 app to 'fix' a problem...

 

For example when I first log in every morning, I'm unable to access the client system running Synergy 1.  That system shows a failed connection attempt message repeatedly pop up every couple seconds.  When this occurs the ONLY fix I have is to stop & start Synergy on the client system...

 

I have other issues though the day that leave me frequently needing to restart synergy (some of which I reported in the past but gave up on and have simply lived with after I failed to get anywhere with support)...

 

As far as I can tell so far, Synergy 2 is no less prone to this than Synergy 1 was, so am I supposed to reboot my system multiple times a day from now on???

Share this post


Link to post
Share on other sites

Bobby, what OS do you use? If Win, have you 'permitted' all three Synergy exe files?

Share this post


Link to post
Share on other sites

I don't know what yo mean by "Permitted" but in the case of Synergy 1 my main system is Windows 7 the client(s) are Mac OS...

So only the host system uses an exe...  It's the Mac copy that I must quit and restart

 

As far as I know all needed permission have been granted on all systems...

Share this post


Link to post
Share on other sites

I'm getting an error trying to access that link..

 

That said, I would have to assume it is allowed through the firewall as the specific issue in question is always fixed by stoping & starting the client on the Mac system (without making any changes to synergy on the Windows side).

Share this post


Link to post
Share on other sites

Also, I was reminded of another today (I'm back in 1.8.8)...

 

If my main (Windows 7) system becomes locked (i.e. ctrl-alt-del to login) and I move the cursor off the screen on to one of the Mac systems, I can NEVER regain control of my Windows system short of either force restarting it, or stopping & starting Synergy on the two Mac systems (so all clients become disconnected from the server).

 

Obviously I opt for the second as it won't risk a corrupted system by force-powering off.  While I haven't verified this happens in 2.0, if it does this will leave me forced to reboot both systems in place of just quitting & re-launching...

Edited by Bobby Thompson

Share this post


Link to post
Share on other sites

I've had that happen on version 1. When I start Win 10, entering login info and move the mouse over past the edge of the monitor, the cursor gets lost out there in the somewhere. I've always just manually restarted the Win box and been more careful not to jostle the mouse. I never thought of stopping the Synergy on the Linux machine. Hmmm. I may have to try to reproduce this... but not today.

Share this post


Link to post
Share on other sites

Here is a snippit from my log this morning...

 

This is one of the situations where I have to quit & start synergy on my client to get it working again:

 

[2017-10-16T08:42:57] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-10-16T08:42:57] INFO: accepted secure socket
[2017-10-16T08:42:57] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD
[2017-10-16T08:42:57] NOTE: accepted client connection
[2017-10-16T08:42:57] ERROR: invalid message from client "shcmmbt.shc.net": DINF
[2017-10-16T08:42:57] NOTE: new client disconnected
[2017-10-16T08:42:59] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-10-16T08:42:59] INFO: accepted secure socket
[2017-10-16T08:42:59] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD
[2017-10-16T08:42:59] NOTE: accepted client connection
[2017-10-16T08:42:59] ERROR: invalid message from client "shcmmbt.shc.net": DINF
[2017-10-16T08:42:59] NOTE: new client disconnected
[2017-10-16T08:43:01] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-10-16T08:43:01] INFO: accepted secure socket
[2017-10-16T08:43:01] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD
[2017-10-16T08:43:01] NOTE: accepted client connection
[2017-10-16T08:43:01] ERROR: invalid message from client "shcmmbt.shc.net": DINF
[2017-10-16T08:43:01] NOTE: new client disconnected
[2017-10-16T08:43:03] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-10-16T08:43:03] INFO: accepted secure socket
[2017-10-16T08:43:03] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD
[2017-10-16T08:43:03] NOTE: accepted client connection
[2017-10-16T08:43:03] ERROR: invalid message from client "shcmmbt.shc.net": DINF
[2017-10-16T08:43:03] NOTE: new client disconnected
[2017-10-16T08:43:05] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-10-16T08:43:05] INFO: accepted secure socket
[2017-10-16T08:43:05] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD
[2017-10-16T08:43:05] NOTE: accepted client connection
[2017-10-16T08:43:05] ERROR: invalid message from client "shcmmbt.shc.net": DINF
[2017-10-16T08:43:05] NOTE: new client disconnected

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