Joseph Hada

Looks like its connected, but nothing

24 posts in this topic

I downloaded it on two windows 10 systems.  I started it on both and each gets a window with two green boxes that seem to represent each computer.  Can't tell for sure because the names start the same but the boxes don't display enough characters to tell the difference.  That aside, there are no more buttons showing nor options to click to start it working.  Don't know what else to do with it.  What am I missing?

Also, it doesn't seem to know that one computer has an external monitor attached.  Any help is greatly appreciated.

Share this post


Link to post
Share on other sites

Joseph,

first off, let them sit a few minutes. the initial connection to the cloud is not immediate. the delay could be up to about 5 minutes, but not more. after that, shut down both computers and restart them. if you are still no-go, go to the top of the early access part of the forum and look over the sticky posts. They will give you better insights into troubleshooting.

Next, go to the troubleshooting guide recently posted by Kelvin Tran:

let us know of your progress

Share this post


Link to post
Share on other sites
6 hours ago, Joseph Hada said:

Also, it doesn't seem to know that one computer has an external monitor attached.  Any help is greatly appreciated.

The icon won't show two monitors, just the relative position of one computer to the other (the mouse motion works as you'd expect.)

Share this post


Link to post
Share on other sites

I'm having the same issue, it shows both of my win 10 pcs but no way to use the mouse.

I already reinstalled, restarted and still nothing.

There is a command i'm supposed to do?

Share this post


Link to post
Share on other sites

Have you both disabled the firewall, as explained here: https://symless.com/synergy-2-beta4-troubleshooting

Generally, if you're seeing both machines, but they aren't connecting to one another, it's a problem with the firewall or networking. You can try to telnet to the server port from one machine to the other (need to figure out what port it's running on--usually something around 24800 in the logs) to prove that you have connectivity between machines.

Share this post


Link to post
Share on other sites

I had Synergy 1.8 running on 2 Windows 10 Pro machines. I installed the 2.0 beta 4 and it no longer works, i.e. can't share keyboard and mouse. If I bring up the Synergy 2.0 client on both machines, it shows the 2 machines and both are green. If I hit F12 on one machine I can see the reconfiguration happening on the other machine and vice versa. I've tried turning off the firewall on one or both the machines. I've rebooted both machines (multiple times). I've uninstalled and re-installed. Nothing works.

On both machines I see the following failures/errors in the log files. In both cases I can see a failure trying to connect to port 24810 on the other (192.168.1.14 and 192.168.1.17) along with 3 other connection failures. That would seem to imply a firewall issue but, as I said, this was working with 1.8 and I tried explicitly turning off both the firewalls. (I also checked and there were exceptions listed for the Synergy and Synergy 2.0 applications.)

[ Service ] [2017-10-09T14:27:00] debug: comparing profiles, id=4381 this=v9 other=v9
[ Service ] [2017-10-09T14:27:00] debug: profile screen status changed, screenId=8769 Connecting->Connected
[ Service ] [2017-10-09T14:27:00] debug: profile changed, storing local copy
[ Service ] [2017-10-09T14:27:01] debug: failed report: dest = 8786, ips = 10.0.75.1,172.18.193.225,172.22.80.1,192.168.1.17
[ Service ] [2017-10-09T14:27:01] debug: local profile modified, id=4381
[ Service ] [2017-10-09T14:27:01] debug: comparing profiles, id=4381 this=v9 other=v9
[ Service ] [2017-10-09T14:27:01] debug: profile screen test result changed, screenId=8786 success=``->`` failed=``->`10.0.75.1,172.18.193.225,172.22.80.1,192.168.1.17`
[ Service ] [2017-10-09T14:27:01] debug: handling new report from connectivity tester, screenId=8786 successfulIp= lastServerId=8769
[ Service ] [2017-10-09T14:27:01] debug: finished connectivity test
[ Service ] [2017-10-09T14:27:19] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-09T14:27:19] debug: connectivity test failed for 192.168.1.17:24810
[ Service ] [2017-10-09T14:27:19] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-09T14:27:19] debug: connectivity test failed for 172.18.193.225:24810
[ Service ] [2017-10-09T14:27:19] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-09T14:27:19] debug: connectivity test failed for 10.0.75.1:24810
[ Service ] [2017-10-09T14:27:19] debug: tcp client connect error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[ Service ] [2017-10-09T14:27:19] debug: connectivity test failed for 172.22.80.1:24810
[ Service ] [2017-10-09T14:27:38] debug: comparing profiles, id=4381 this=v9 other=v9
[ Service ] [2017-10-09T14:27:38] debug: profile screen test result changed, screenId=8786 success=``->`` failed=`10.0.75.1,172.18.193.225,172.22.80.1,192.168.1.17`->``
[ Service ] [2017-10-09T14:27:38] debug: profile changed, storing local copy

 

Share this post


Link to post
Share on other sites

Does anyone from Symless read these posts? This is the absolutely worst beta experience ever. The product doesn't work at all, there's no way to debug it and there's absolutely no support from the developer. How do I get my money back?

Share this post


Link to post
Share on other sites
3 hours ago, Ken Rider said:

Does anyone from Symless read these posts? This is the absolutely worst beta experience ever. The product doesn't work at all, there's no way to debug it and there's absolutely no support from the developer. How do I get my money back?

Email: [email protected]

beta4 has fundamental networking problems, and I'd encourage you to try again when beta5 drops. 

You can see in your log output that connections are being attempted on various IP addresses, likely reported as "live" on either machine at one point in time. beta4 has problems making sense of your machine configuration, particularly when you're using a VPN or other virtual networks. You can use a telnet client to connect from one machine to the other on the indicated ports (looks like 24810) to confirm that you don't have firewall issues, but if you're able to manually connect, but the server-client aren't finding one another, then it would appear you're simply a victim of beta4.

If you can confirm that the firewall isn't in the way, and you've followed the setup instructions pinned at the top of the forum, your only hope with beta4 seems to be to restart server/client until they find one another.

Share this post


Link to post
Share on other sites

The client install, at the moment, does not open the windows firewall properly for Synergy 2 or the Windows firewall does not deal .  So you will need to either:

a) Add Inbound Rules for Synergyd, synergyc, and synergys and allow all program wise on both clients

b) Add inbound rule for 24810 on both sides.

I also found Windows 10 Defender will warn your system is insecure.  I had this come up and when I restored settings, it removed the firewall entries, so you have to add it back in.

 

 

Share this post


Link to post
Share on other sites

When you say you have tried turning off both firewall, what exactly are you doing? I ask this not to imply that you do not know what you are doing, but say that you may have to do other things. When I was first having issues I disabled my third party security software's firewall, but it had been also using the Windows Firewall framework for some basic functions, so I had to manually disable/tweak them both before I was able to connect.

Share this post


Link to post
Share on other sites

I also just gave synergy 2 a try,

my experience was identical to the thread creator. I connected a MacBook Pro with a Windows 10 Machine, both have two screens over each other (Laptop + Screen) and are connected to a WIFI network. Synergy 1 works fine, except that I have always to move the mouse over the top screens to the other computer, so I had the hope Synergie 2 has better multi monitor support. 

But after installing Synergy2 and authenticating at Synergy, in the App only appear two green cubes, the App is very unsatisfying. Right now Symless propose the beta to power users which want to give the beta4 a try. But the only thing I see after I start the App is a Windows with two "devices?" which are green so I think everything is ok. But nothing else works and no options to troubleshoot or do anything there from the Application side. 

Share this post


Link to post
Share on other sites
8 hours ago, JDDoesIT said:

When you say you have tried turning off both firewall, what exactly are you doing? I ask this not to imply that you do not know what you are doing, but say that you may have to do other things. When I was first having issues I disabled my third party security software's firewall, but it had been also using the Windows Firewall framework for some basic functions, so I had to manually disable/tweak them both before I was able to connect.

I only have and turned off the Windows Firewall (domain, private and public even though I was only using a private network).

Share this post


Link to post
Share on other sites

Hi,

I only needed to open port 24810 in firewall for inbound and outbound rules. No need to shutdown the whole firewall. Each time I open my computers, I need to restart the Synergy service and the program. After that it's working great.

 

Thanks,

Share this post


Link to post
Share on other sites
2 hours ago, Paganasia said:

I only needed to open port 24810 in firewall for inbound and outbound rules.

That appears to have fixed it for me. Before, I could only get it to work from Mac -> Windows, not the other way.

So configuration needs works, plus the mouse is a little jumpy on the Mac. Hopefully beta5 will work much better.

Share this post


Link to post
Share on other sites

So I am working around it for myself temporarily, but the solutions aren't going to make anyone happy.  First, Mouse without borders.  It connected and worked much more easily but the the mouse movement was still not smooth 100% of the time.  Logitech has another option where you use a usb dongle paired with a network connection to control multiple computers.  I haven't tried it but I'm thinking it isn't as smooth as one would hope due to combination usb and networking.  Now if it was a keyboard and mouse that came with multiple dongles, one for each computer with a selector switch on the keyboard with no use of a network it might be pretty effective with no lag.  For now, I am going to use a 4 computer usb selector switch I got on Amazon.  But it still this scenario doesn't allow simply moving the mouse off one screen and onto another from another system.   I have paid for Synergy twice I think, I support them, and I really hope they iron this out.  Once synergy works smoothly across multiple computers with no lag I will come back to it and be very excited to do so.

 

Share this post


Link to post
Share on other sites

I have a Mouse and Keyboard where I can select to which device it connects. But you absolutely cant compare it. Synergy allows you to use multiple computers as if it's only one. Copy, Paste works and you just have to leave the edge of the screen to switch devices. Physically toggling the connected device is so uncomfortable and slow, it's just a different way of working. Why are you not just using synergy 1 until the issues are resolved?

Share this post


Link to post
Share on other sites

I agree it is much better and I want it to work. Mouse lag is the issue on using the first version.  Same as my complaint with Mouse without borders.  Plus, it seems to be a pain when I bring home my surface and dock it and it doesn't always reconnect to synergy or mouse without borders for that matter.  I was hoping 2 would improve on these issues.  My goal is to be completely free of the extra keyboard and mouse on desk.  If my computers were all stationary it might be ok but until then I'll deal with a physical switch as it allows flash drives to transfer with the push of the same button.

Share this post


Link to post
Share on other sites

Are you sure the mouse lag is not introduced by your network? I use Synergy at work, and it doesn't have any issues regarding lags with two laptops connected to a company wifi. If your wifi is too crowded or the network is too unreliable, you can also try to physically connect both devices with a fixed Lan cable. 

Share this post


Link to post
Share on other sites

Synergy 2 Beta 5 on my MacBookPro OSX 10.11 (El Capitan) says now "There was a problem connecting to the background service. Retry"  

Retry does restart the App, but the message stays, also a reboot did not resolve the issue. When checking for the "synergy-service" in the Activity Monitor I can't find the service at all.

Share this post


Link to post
Share on other sites
Here is the log
[ Config  ] [2017-10-31T13:40:37] INFO: log filename: /Users/fxx/Library/Preferences/Symless/Synergy/synergy.log
[ Config  ] [2017-10-31T13:40:37] DEBUG: connecting to background service
[ Config  ] [2017-10-31T13:40:38] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-31T13:40:37] error: rpc connect failed: connect: Connection refused
[ Config  ] [2017-10-31T13:40:40] DEBUG: current version is update to date
[ Config  ] [2017-10-31T13:40:42] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:40:47] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:40:52] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:40:57] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:41:02] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:41:06] DEBUG: restarting app with: /Applications/Synergy.app/Contents/MacOS/synergy-config 
[ Config  ] [2017-10-31T13:41:07] INFO: log filename: /Users/fxx/Library/Preferences/Symless/Synergy/synergy.log
[ Config  ] [2017-10-31T13:41:07] DEBUG: connecting to background service
[ Config  ] [2017-10-31T13:41:07] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-31T13:41:07] error: rpc connect failed: connect: Connection refused
[ Config  ] [2017-10-31T13:41:09] DEBUG: current version is update to date
[ Config  ] [2017-10-31T13:41:16] INFO: log filename: /Users/fxx/Library/Preferences/Symless/Synergy/synergy.log
[ Config  ] [2017-10-31T13:41:16] DEBUG: connecting to background service
[ Config  ] [2017-10-31T13:41:17] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-31T13:41:16] error: rpc connect failed: connect: Connection refused
[ Config  ] [2017-10-31T13:41:18] DEBUG: current version is update to date
[ Config  ] [2017-10-31T13:41:20] DEBUG: restarting app with: /Applications/Synergy.app/Contents/MacOS/synergy-config 
[ Config  ] [2017-10-31T13:41:20] INFO: log filename: /Users/fxx/Library/Preferences/Symless/Synergy/synergy.log
[ Config  ] [2017-10-31T13:41:20] DEBUG: connecting to background service
[ Config  ] [2017-10-31T13:41:21] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-31T13:41:20] error: rpc connect failed: connect: Connection refused
[ Config  ] [2017-10-31T13:41:23] DEBUG: current version is update to date
[ Config  ] [2017-10-31T13:41:25] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:41:30] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:41:35] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:41:40] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:41:45] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:41:50] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:41:55] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:42:00] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:42:05] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:42:10] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:42:15] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:42:20] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:42:25] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:42:36] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:42:50] INFO: log filename: /Users/fxx/Library/Preferences/Symless/Synergy/synergy.log
[ Config  ] [2017-10-31T13:42:50] DEBUG: connecting to background service
[ Config  ] [2017-10-31T13:42:51] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-31T13:42:50] error: rpc connect failed: connect: Connection refused
[ Config  ] [2017-10-31T13:42:53] DEBUG: current version is update to date
[ Config  ] [2017-10-31T13:42:53] DEBUG: restarting app with: /Applications/Synergy.app/Contents/MacOS/synergy-config 
[ Config  ] [2017-10-31T13:42:53] INFO: log filename: /Users/fxx/Library/Preferences/Symless/Synergy/synergy.log
[ Config  ] [2017-10-31T13:42:53] DEBUG: connecting to background service
[ Config  ] [2017-10-31T13:42:53] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-31T13:42:53] error: rpc connect failed: connect: Connection refused
[ Config  ] [2017-10-31T13:42:55] DEBUG: current version is update to date
[ Config  ] [2017-10-31T13:42:58] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:43:03] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:43:08] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:43:13] debug: rpc keep alive failed
[ Config  ] [2017-10-31T13:43:18] debug: rpc keep alive failed

Share this post


Link to post
Share on other sites

Could you take a look at this file?

~/Library/Synergy/synergy-service.log

Share this post


Link to post
Share on other sites

The latest log of ~/Library/Synergy/synergy-service.log contains only data from last week. 

 

[2017-10-26T14:45:22] debug: tcp client connect error: Operation timed out
[2017-10-26T14:45:22] debug: connectivity test failed for 192.168.56.1:24810
[2017-10-26T14:45:22] debug: tcp client connect error: Operation timed out
[2017-10-26T14:45:22] debug: connectivity test failed for 10.11.12.1:24810
[2017-10-26T14:45:22] debug: tcp client connect error: Operation timed out
[2017-10-26T14:45:22] debug: connectivity test failed for 10.0.75.1:24810
[2017-10-26T14:45:48] debug: comparing profiles, id=9579 this=v8 other=v8
[2017-10-26T14:45:48] debug: profile screen active changed, screenId=19677 true->false
[2017-10-26T14:45:48] debug: profile changed, storing local copy
[2017-10-26T14:54:11] debug: core process exited: code=0 expected=false

Share this post


Link to post
Share on other sites

Looks like the service is crashing. We're working on a fix, should be ready tomorrow.

  • Thanks 1

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