John Munsch

Local network and VPN interaction breaking Synergy 2.0?

5 posts in this topic

The previous version of Synergy handled my situation quite well. I have a machine at home which is not on a work VPN but is on my home wi-fi network. I also have a work laptop which is on the same wi-fi network but on the work VPN. When I fire up Synergy it refers to the home machine as imac.local (much as with the previous version of Synergy) but the work machine is referred to as sschrate-1.corp.<my work domain>.ad.

At a guess, since I'm accessing the Symless login over the VPN on one machine and not via the VPN on the other, the two machines cannot see each other despite sharing the same wi-fi network. In the previous version, they didn't attempt to make their connection via the Internet and it worked correctly. At least, that's my guess.

John

[Core] [2017-07-13T15:40:30] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:30] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:31] ERROR: [2017-07-13T15:40:31] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:31] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:31] DEBUG: retry in 1 seconds

[Core] [2017-07-13T15:40:32] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[ UI ] [2017-07-13T15:40:32] ERROR: [2017-07-13T15:40:32] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:32] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:33] ERROR: [2017-07-13T15:40:33] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:33] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:33] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:34] ERROR: [2017-07-13T15:40:34] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:34] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:34] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:35] ERROR: [2017-07-13T15:40:35] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:35] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:35] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:36] ERROR: [2017-07-13T15:40:36] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:36] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:36] DEBUG: retry in 1 seconds

[Core] [2017-07-13T15:40:37] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[ UI ] [2017-07-13T15:40:37] ERROR: [2017-07-13T15:40:37] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:37] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:38] ERROR: [2017-07-13T15:40:38] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:38] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:38] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:39] ERROR: [2017-07-13T15:40:39] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:39] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:39] DEBUG: retry in 1 seconds

[Core] [2017-07-13T15:40:40] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[ UI ] [2017-07-13T15:40:40] ERROR: [2017-07-13T15:40:40] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:40] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:41] ERROR: [2017-07-13T15:40:41] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:41] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:41] DEBUG: retry in 1 seconds

[Core] [2017-07-13T15:40:42] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[ UI ] [2017-07-13T15:40:43] ERROR: [2017-07-13T15:40:42] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:43] DEBUG: retry in 1 seconds

[Core] [2017-07-13T15:40:44] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[ UI ] [2017-07-13T15:40:44] ERROR: [2017-07-13T15:40:44] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:44] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:45] ERROR: [2017-07-13T15:40:45] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:45] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:45] DEBUG: retry in 1 seconds

[ UI ] [2017-07-13T15:40:46] ERROR: [2017-07-13T15:40:46] WARNING: failed to connect to server: Connection refused

[Core] [2017-07-13T15:40:46] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

[Core] [2017-07-13T15:40:46] DEBUG: retry in 1 seconds

[Core] [2017-07-13T15:40:47] NOTE: connecting to '192.168.0.179': 192.168.0.179:24800

 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @John Munsch. I am currently checking with our developers about this. I'll get back with you on this on Monday.

Share this post


Link to post
Share on other sites

Hi, 
Just chiming in. 
I'm on the same boat.

Looking forward to updates on this.

Share this post


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

Hi, 
Just chiming in. 
I'm on the same boat.

Looking forward to updates on this.

I was able to login both on the VPN and on Synergy 2.0. I use Tunnelblick making sure not all IPv4 traffic are routed to the VPN. I suspect your VPN doesn't allow connections from the port Synergy uses.

Share this post


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

I was able to login both on the VPN and on Synergy 2.0. I use Tunnelblick making sure not all IPv4 traffic are routed to the VPN. I suspect your VPN doesn't allow connections from the port Synergy uses.

I don't think that's the case @xxx2310 since @John Munsch said that it worked with the previous version. Looks more to me like his VPN does not allow communication to local LAN machines which would look like to be machines on a different subnet.

As mentioned in other threads, our developers will be adding an interface to allow manual selection of network interface feature that would allow users to choose as to which network interface they'd want their machines to have a connection from and to.

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