Dylan Kraklan

Connection between Windows / Linux not working

17 posts in this topic

Hello,

 

I've been using synergy for years and have never had an issue, until last night that is. I'm running a windows 10 pc with 3 monitors and a linux mint netbook with 2 monitors, this configuration has worked for weeks until last night. I don't know what changed but now i'm getting all sorts of issues. I'm posting the logs below, all help will be much appreciated.

 

Windows 10 - Server

[2016-08-20T14:13:43] INFO: starting server
[2016-08-20T14:13:43] INFO: config file: C:/Users/dell/AppData/Local/Temp/qt_temp.em4952
[2016-08-20T14:13:43] INFO: log level: INFO
[2016-08-20T14:13:43] INFO: service command updated
[2016-08-20T14:13:44] INFO: starting new process
[2016-08-20T14:13:44] INFO: activeDesktop:Default
[2016-08-20T14:13:44] INFO: starting new process
[2016-08-20T14:13:44] INFO: drag and drop enabled
[2016-08-20T14:13:44] NOTE: started server, waiting for clients
[2016-08-20T14:13:44] INFO: watchdog status: ok
[2016-08-20T14:13:45] INFO: OpenSSL 1.0.2 22 Jan 2015
[2016-08-20T14:13:45] NOTE: accepted client connection
[2016-08-20T14:13:54] ERROR: failed to accept secure socket
[2016-08-20T14:13:54] INFO: client connection may not be secure
[2016-08-20T14:13:56] INFO: OpenSSL 1.0.2 22 Jan 2015
[2016-08-20T14:13:56] NOTE: accepted client connection
[2016-08-20T14:14:05] ERROR: failed to accept secure socket
[2016-08-20T14:14:05] INFO: client connection may not be secure
[2016-08-20T14:14:06] INFO: OpenSSL 1.0.2 22 Jan 2015
[2016-08-20T14:14:06] NOTE: accepted client connection
[2016-08-20T14:14:13] INFO: service command updated
[2016-08-20T14:14:14] INFO: process started but command is empty, shutting down
[2016-08-20T14:14:15] ERROR: failed to accept secure socket
[2016-08-20T14:14:15] INFO: client connection may not be secure
[2016-08-20T14:14:17] INFO: got ipc shutdown message
[2016-08-20T14:14:17] NOTE: stopped server
[2016-08-20T14:14:17] INFO: process 11680 was shutdown gracefully

 

Linux-Mint - Client

NOTE: starting client
NOTE: config file: /tmp/qt_temp.Ti3256
NOTE: log level: INFO
2016-08-20T14:13:45 NOTE: started client
/build/synergy-CUL4K_/synergy-1.6.2/src/lib/synergy/ClientApp.cpp,407
2016-08-20T14:13:45 NOTE: connecting to '192.168.1.145': 192.168.1.145:24800
/build/synergy-CUL4K_/synergy-1.6.2/src/lib/client/Client.cpp,149
2016-08-20T14:13:56 NOTE: disconnected from server
/build/synergy-CUL4K_/synergy-1.6.2/src/lib/synergy/ClientApp.cpp,324
2016-08-20T14:13:56 NOTE: connecting to '192.168.1.145': 192.168.1.145:24800
/build/synergy-CUL4K_/synergy-1.6.2/src/lib/client/Client.cpp,149
2016-08-20T14:14:07 NOTE: disconnected from server
/build/synergy-CUL4K_/synergy-1.6.2/src/lib/synergy/ClientApp.cpp,324
2016-08-20T14:14:07 NOTE: connecting to '192.168.1.145': 192.168.1.145:24800
/build/synergy-CUL4K_/synergy-1.6.2/src/lib/client/Client.cpp,149
NOTE: stopping synergy desktop process

 

 

 

If you need any more information please let me know and I'll provide it

Share this post


Link to post
Share on other sites

AN update, i've uninstalled and re installed on both machines, i can't seem to get the configs to wipe on either, so I reinstalled the OS completely on the linux machine but having issues getting rid of the config on the windows 10 machine.

Share this post


Link to post
Share on other sites

Can you post the log from the Linux machine as well?

The windows config appears to say that he process ends gracefully.

Waiting for your reply.

Avishay.

Share this post


Link to post
Share on other sites

Anyone else have any thoughts on this still not able to figure this one out...

Share this post


Link to post
Share on other sites

have been trying to connect three win 10 machines using SSL using the latest version 1.8.x and have essentially the same issue.... works ok as long as you don't use SSL .... but that is not the point....they need to fix the problem.... since I upgraded from ver 1.5.x I can't connect using SSL.... I checked to make sure SSL was enabled on all machines (Control panel... internet options.... Advanced ) makes no difference... but interesting that your logs looks similar to mine

Share this post


Link to post
Share on other sites

I have the same problem. My server is a Windows 10 and client is a Ubuntu 16.04. The only difference is my error is as follows:

 

Server - Windows 10

[2016-09-01T16:14:39] NOTE: started server, waiting for clients
[2016-09-01T16:14:39] INFO: watchdog status: ok

 

Client - Ubuntu 16.04

[2016-09-01T16:14:35] NOTE: connecting to '198.168.8.207': 198.168.8.207:24801 
[2016-09-01T16:14:35] INFO: OpenSSL 1.0.1f 6 Jan 2014 
[2016-09-01T16:14:51] WARNING: failed to connect to server: Timed out 
[2016-09-01T16:14:52] NOTE: connecting to '198.168.8.207': 198.168.8.207:24801 
[2016-09-01T16:14:52] INFO: OpenSSL 1.0.1f 6 Jan 2014 
[2016-09-01T16:15:08] WARNING: failed to connect to server: Timed out 
[2016-09-01T16:15:09] NOTE: connecting to '198.168.8.207': 198.168.8.207:24801 
[2016-09-01T16:15:09] INFO: OpenSSL 1.0.1f 6 Jan 2014

Share this post


Link to post
Share on other sites

I'm also experiencing this issue. Ubuntu 14.04 is running the server, and Windows 7 is the client. Works fine without SSL, but when I enable SSL it doesn't work at all.

 

Then I tried killing the server and reconnecting the client. It appears to work for a moment, and I get mouse and keyboard on both systems. Then all of a sudden it dies with the client reporting that it's unable to establish a secure socket.

Share this post


Link to post
Share on other sites

I had the problem yesterday and fixed it. I think what happened was that when I upgraded I had to re-register the license on the Windows machine. Then I had to set the SSL checkbox again. Also, if the logs aren't giving you enough information you can change the logging level in the settings. Debug, debug 1 and debug 2 provide a lot more information. I recommend setting it back when you've resolved the problem.

Share this post


Link to post
Share on other sites

I can confirm as well that disabling ssh on both client and server makes Synergy work just fine, and that enabled there are all kinds of connection errors.

 

My client is running Ubuntu 15.10 x64

server is running Windows 10

 

Things worked just fine prior to 1.82 build of Synergy. Then I had some troubles that did not seem to have any parallels online. I waited a few weeks to see if anything had changed. I'm now running a nightly build, and found this forum post that seems to mirror my own problems.

Share this post


Link to post
Share on other sites

Same behaviour here. No connection with SSL. Connection without SSL.

Ubuntu 16.04 Server

Windows 7 Client

Share this post


Link to post
Share on other sites

No sure everyone has the same issue but running the wizzard again on both machines worked for me...

Share this post


Link to post
Share on other sites

Having a similar issue:

Server

- Xubuntu 16.04

- using v1.8.7 stable 64bit

 

Client

- Windows 8.1

- using v1.8.7 stable 64bit

 

On the client, the "Use SSL Encryption" setting is grayed out.

 

If I turn off SSL on the server, it connects. If it's turned on then the client won't connect, it errors with this (which repeats every minute or so):

[2017-01-24T10:03:04] INFO: OpenSSL 1.0.2g 1 Mar 2016

[2017-01-24T10:03:20] ERROR: ssl error occurred (system call failure)

[2017-01-24T10:03:20] ERROR: eof violates ssl protocol

[2017-01-24T10:03:20] ERROR: failed to accept secure socket

[2017-01-24T10:03:20] INFO: client connection may not be secure

Share this post


Link to post
Share on other sites

On original set up I had windows as server and linux mint 18 as client.Permission is asked for on the original set-up. Could not get it to work. So I set the linux mint as server and windows 10 as client. It asked for permission again, it worked. I think permissions have got to be allowed for each computer and the only way to do it is to swap server to client. At the moment I am using linux mint as server, but if I swap them back it also works

Share this post


Link to post
Share on other sites

I tried John's workaround (changing the server to my linux machine), but the settings for the Linux (Ubuntu) version requires a password with the SSL encryption and the Windows version requires no password making SSL impossible between the two versions. I'd like my money back, or someone from the company telling me they are working on a fix.

Edited by Austin K Gatlin

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