gee4vee

[Performed troubleshooting] Just upgraded to 2.0.0-beta4, no connectivity

41 posts in this topic

On 10/11/2017 at 2:36 PM, bigbear3001 said:

I needed to permit synergys.exe to "Outbound Rules" (Domain + Private) in Windows 10 before the connection test was successful.

I did not add Outbound, however, did add the rest of the Synder exe's as indicated for inbound on both endpoints.  Working!

Share this post


Link to post
Share on other sites

Soo....

This is interesting....

Now the port to open is 24800

Why the change?

Had to re-configure the firewall rules to get the Synergy2 to work again.

Share this post


Link to post
Share on other sites

It uses a number of different ports. This is why program-based exceptions are better. See the sticky for full details. 

Share this post


Link to post
Share on other sites

I ditched the beta... it stopped working.... I went back to 1.8 and works fine for now... 

Willing to try the next update ....

Share this post


Link to post
Share on other sites

At the moment, I am still having connection issues between Client and Server.  Even with the firewall completely disabled.  Both client and server show green, but connection test between the two are showing 'successful' then 'failed'.

Quote

[ Service ] [2017-10-20T08:20:35] debug: profile changed, storing local copy

[ Service ] [2017-10-20T08:20:35] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:20:35] debug: profile has not changed, no action needed

[ Service ] [2017-10-20T08:20:35] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:20:35] debug: profile screen status changed, screenId=1225 Connecting->Connected

[ Service ] [2017-10-20T08:20:35] debug: profile changed, storing local copy

[ Service ] [2017-10-20T08:20:42] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:20:42] debug: profile screen active changed, screenId=1224 false->true

[ Service ] [2017-10-20T08:20:42] debug: new screens detected (1), preparing connectivity test

[ Service ] [2017-10-20T08:20:42] debug: starting connectivity test

[ Service ] [2017-10-20T08:20:42] debug: profile changed, storing local copy

[ Service ] [2017-10-20T08:20:42] debug: connectivity test passed for 192.168.1.20:24810

[ Service ] [2017-10-20T08:20:45] debug: successful report: dest = 1224, ips = 192.168.1.20

[ Service ] [2017-10-20T08:20:45] debug: local profile modified, id=637

[ Service ] [2017-10-20T08:20:45] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:20:45] debug: profile screen test result changed, screenId=1224 success=``->`192.168.1.20` failed=``->``

[ Service ] [2017-10-20T08:20:45] debug: handling new report from connectivity tester, screenId=1224 successfulIp=192.168.1.20 lastServerId=1225

[ Service ] [2017-10-20T08:20:45] debug: finished connectivity test

Vice versa to my server at 192.168.1.10...  This seem to all happen around  the 16th or 17th of this month.  Only thing I seem to see was discovering my router was 'down' and required me to reboot it.  After reboot, synergy 2 was unresponsive to connections despite saying it was connected and having network connectivity.

Share this post


Link to post
Share on other sites
8 minutes ago, Keiichi25 said:

At the moment, I am still having connection issues between Client and Server.  Even with the firewall completely disabled.  Both client and server show green, but connection test between the two are showing 'successful' then 'failed'.

Vice versa to my server at 192.168.1.10...  This seem to all happen around  the 16th or 17th of this month.  Only thing I seem to see was discovering my router was 'down' and required me to reboot it.  After reboot, synergy 2 was unresponsive to connections despite saying it was connected and having network connectivity.

I would:

1) Re-enable your firewall and input the rules as mentioned before.
2) Close Synergy 2.0 on both machines
3) Recycle 'synergy' service on both machines
4) Open Synergy 2.0 on both machines
5) Press F12 on the machine you want to be the server, possibly 2-3 times

Then try.

Share this post


Link to post
Share on other sites

No go:

Quote

[ Service ] [2017-10-20T08:41:28] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:41:28] debug: profile server changed, 1225->1224

[ Service ] [2017-10-20T08:41:28] debug: profile screen test result changed, screenId=1224 success=``->`` failed=`192.168.1.20`->``

[ Service ] [2017-10-20T08:41:28] debug: profile changed, storing local copy

[ Service ] [2017-10-20T08:41:28] debug: handling local profile server changed, mode=server thisId=1225 serverId=1224 lastServerId=1225

[ Service ] [2017-10-20T08:41:28] debug: starting core client process

[ Service ] [2017-10-20T08:41:28] error: aborting client start, no successful connectivity test results

[ Service ] [2017-10-20T08:41:28] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:41:28] debug: profile screen status changed, screenId=1224 Connected->Connecting

[ Service ] [2017-10-20T08:41:28] debug: profile changed, storing local copy

[ Service ] [2017-10-20T08:41:29] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:41:29] debug: profile screen status changed, screenId=1224 Connecting->Connected

[ Service ] [2017-10-20T08:41:29] debug: profile changed, storing local copy

[ Service ] [2017-10-20T08:41:33] 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-20T08:41:33] debug: connectivity test failed for 192.168.1.20:24810

[ Service ] [2017-10-20T08:41:37] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:41:37] debug: profile has not changed, no action needed

[ Service ] [2017-10-20T08:41:40] debug: comparing profiles, id=637 this=v18 other=v18

[ Service ] [2017-10-20T08:41:40] debug: profile has not changed, no action needed

 

Share this post


Link to post
Share on other sites
6 minutes ago, Keiichi25 said:

No go:

 

Did you only do the .exe rules or the port rule too?

Looks like you're having a port issue:

"connectivity test failed for 192.168.1.20:24810"

Share this post


Link to post
Share on other sites

Okay... Added Port Fix and seems to work now.  Seems weird that this would work, but when I had both firewalls down, it did not work.

Suggestion - Option to force a refresh/restart of service via the Synergy window instead of this or a force re-test.  I still don't understand how allowing the port, but not the application unless it was one of the other 2 listed.  I only dealt with the Synergy2 and Synergys apps.

I also don't understand what changed so drastically, as I was working fine until the day of my router going boom for no reason and doing a windows update, thinking it was related.

Edited by Keiichi25
  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, Keiichi25 said:

Okay... Added Port Fix and seems to work now.  Seems weird that this would work, but when I had both firewalls down, it did not work.

Suggestion - Option to force a refresh/restart of service via the Synergy window instead of this or a force re-test.  I still don't understand how allowing the port, but not the application unless it was one of the other 2 listed.  I only dealt with the Synergy2 and Synergys apps.

I also don't understand what changed so drastically, as I was working fine until the day of my router going boom for no reason and doing a windows update, thinking it was related.

I second having more menu's buttons on the Synergy window. Having to open services, etc. is just needless typing and clicking. Everything needed should be a button or option in the Synergy app itself.

Glad you got it working again!

Share this post


Link to post
Share on other sites
13 minutes ago, Keiichi25 said:

I still don't understand how allowing the port, but not the application unless it was one of the other 2 listed.  I only dealt with the Synergy2 and Synergys apps.

You need the other exe as well. In fact synergyc and synergyd do most of the heavy lifting. Synergy2 is just the GUI. More in the sticky.

 

Share this post


Link to post
Share on other sites

Yes, as noted though, nothing really changed on my setup until this week when the router went stupid.

Narrowing it down, I have my router rebooting on Wednesday morning, but the router seemed to have an issue on the reboot.  I rebooted it again and then noticed my issue with Synergy.

But I have been on Synergy 2.0 beta 4 for months and the firewall issue wasn't there since I initially set it up and I rebooted my computers several times before.  So the oddness of this was perplexing me and also trying to flip off the firewall to go further still also perplexed me when it did nothing.

I think I have tweaked it now on both ends, dropping the port allowance and enabling all 4 exes for incoming and outbound (Had to put in outbound for it to 'talk' again with the other computer).

Share this post


Link to post
Share on other sites

Remember guys, this is a BETA and there will be more functionality in the finished product. They have not implemented any of the "other" features yet.

 

I was getting the same issue today with the program working on 3 different machines and then after not using it for a while it disconnected and wouldn't reconnect without adding the port to a Win Server 2012 machine(client).

Share this post


Link to post
Share on other sites
On 10/9/2017 at 11:41 PM, Fridgey said:

Same experience for me. After installing on my desktop and laptop, I could see both machines in the app but I couldn't get it to work until I manually added the following rules to the windows firewall

%ProgramFiles%\Synergy\synergys.exe
%ProgramFiles%\Synergy\synergyd.exe
%ProgramFiles%\Synergy\synergyc.exe
%ProgramFiles%\Synergy\synergy2.exe

I was having issues on my machines with intermittent connectivity.

I found that one machine was seeing the connection as a private network (server) while the other was seeing it as public. They are on the same network.

After correcting made sure that the above programs were all listed in BOTH the Windows Firewall and the third party security program that I use.

Fingers crossed that this minimizes the connection issues that I have been having.

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