gee4vee

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

41 posts in this topic

Great work gee4vee! Good beta testing.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

My Mac server -> Windows 7 client connection wasn't working at all until I followed these steps. Now it's working great though!

  • Like 1

Share this post


Link to post
Share on other sites

Pretty annoyed here as I did this during the work day and now have no connection to my laptop.

Followed the troubleshooting guide (disabled firewall, restart service, F12, etc.) to no avail. I then turned my firewall back on and actually set up rules for Synergy to be allowed. Rebooted. Recycled service many times.

Looks like my desktop can see my laptop (192.168.1.6) but my laptop cannot see my desktop (192.168.1.13)? Why is my laptop not responding when it was working fine on 1.8.8.

Log from my main desktop:

[ Config  ] [2017-10-12T15:57:41] ERROR: failed to start crash handler: Couldn't verify crash dump directory: The system cannot find the file specified
[ Config  ] [2017-10-12T15:57:41] INFO: log filename: C:/Users/Ilya/AppData/Local/Symless/Synergy/synergy.log
[ Config  ] [2017-10-12T15:57:41] DEBUG: connecting to service
[ Config  ] [2017-10-12T15:57:41] DEBUG: connected to service
[ Config  ] [2017-10-12T15:57:41] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-12T15:57:42] DEBUG: Profile ID: 7141 name: default
[ Config  ] [2017-10-12T15:57:42] DEBUG: current version is update to date
[ Config  ] [2017-10-12T15:57:42] DEBUG: requesting profile snapshot
[ Service ] [2017-10-12T15:57:42] debug: connecting websocket
[ Service ] [2017-10-12T15:57:42] error: can't send profile snapshot, not yet received from cloud
[ Service ] [2017-10-12T15:57:43] debug: websocket connected
[ Service ] [2017-10-12T15:57:43] debug: comparing profiles, id=-1 this=v-1 other=v14
[ Service ] [2017-10-12T15:57:43] debug: profile id changed, -1->7141
[ Service ] [2017-10-12T15:57:43] debug: profile name changed, ->default
[ Service ] [2017-10-12T15:57:43] debug: profile server changed, -1->14075
[ Service ] [2017-10-12T15:57:43] debug: profile screen set changed, added=2 removed=0
[ Service ] [2017-10-12T15:57:43] debug: new screens detected (2), preparing connectivity test
[ Service ] [2017-10-12T15:57:43] debug: profile changed, storing local copy
[ Service ] [2017-10-12T15:57:43] debug: handling local profile server changed, mode=unknown thisId=14075 serverId=14075 lastServerId=-1
[ Service ] [2017-10-12T15:57:43] debug: starting core server process
[ Service ] [2017-10-12T15:57:43] debug: starting core process with command: C:\Program Files\Synergy\synergys.exe -f --no-tray --debug DEBUG --name Orion --enable-drag-drop --profile-dir C:\Users\Ilya\AppData\Local\Symless\Synergy --log synergy.log -c C:\Users\Ilya\AppData\Local\Symless\Synergy\synergy.conf --address :24800
[ Service ] [2017-10-12T15:57:43] debug: core process started, id=4496
[ Service ] [2017-10-12T15:57:43] debug: handling local profile screen set changed, mode=server
[ Service ] [2017-10-12T15:57:43] debug: starting core server process
[ Service ] [2017-10-12T15:57:43] debug: process already running, attempting to stop
[ Service ] [2017-10-12T15:57:43] debug: stopping core process
[ Service ] [2017-10-12T15:57:43] debug: core process exited: code=1 expected=true
[ Service ] [2017-10-12T15:57:43] debug: core process shutdown complete
[ Service ] [2017-10-12T15:57:43] debug: starting core process with command: C:\Program Files\Synergy\synergys.exe -f --no-tray --debug DEBUG --name Orion --enable-drag-drop --profile-dir C:\Users\Ilya\AppData\Local\Symless\Synergy --log synergy.log -c C:\Users\Ilya\AppData\Local\Symless\Synergy\synergy.conf --address :24800
[ Service ] [2017-10-12T15:57:43] debug: core process started, id=10092
[ Core    ] [2017-10-12T15:57:43] INFO: drag and drop enabled
[ Core    ] [2017-10-12T15:57:43] DEBUG: opening configuration "C:\Users\Ilya\AppData\Local\Symless\Synergy\synergy.conf"
[ Core    ] [2017-10-12T15:57:43] DEBUG: configuration read successfully
[ Core    ] [2017-10-12T15:57:43] DEBUG: screen shape: 0,0 1920x1080
[ Core    ] [2017-10-12T15:57:43] ERROR: failed to get desktop path, no drop target available, error=2
[ Core    ] [2017-10-12T15:57:43] DEBUG: window is 0x000a0c1a
[ Core    ] [2017-10-12T15:57:43] DEBUG: adopting new buffer
[ Core    ] [2017-10-12T15:57:43] DEBUG: opened display
[ Core    ] [2017-10-12T15:57:43] DEBUG: active sides: 2
[ Core    ] [2017-10-12T15:57:43] DEBUG: active sides: 2
[ Core    ] [2017-10-12T15:57:43] DEBUG: desk Default window is 0x00090c06
[ Core    ] [2017-10-12T15:57:43] DEBUG: switched to desk "Default"
[ Core    ] [2017-10-12T15:57:43] DEBUG: desktop is now accessible
[ Core    ] [2017-10-12T15:57:43] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1
[ Core    ] [2017-10-12T15:57:43] NOTE: started server, waiting for clients
[ Core    ] [2017-10-12T15:57:43] DEBUG: event queue is ready
[ Core    ] [2017-10-12T15:57:43] DEBUG: add pending events to buffer
[ Core    ] [2017-10-12T15:57:43] DEBUG: screen "Orion" shape changed
[ Service ] [2017-10-12T15:57:43] debug: comparing profiles, id=7141 this=v14 other=v14
[ Service ] [2017-10-12T15:57:43] debug: profile screen status changed, screenId=14075 Connected->Connecting
[ Service ] [2017-10-12T15:57:43] debug: profile changed, storing local copy
[ Service ] [2017-10-12T15:57:44] debug: comparing profiles, id=7141 this=v14 other=v14
[ Service ] [2017-10-12T15:57:44] debug: profile has not changed, no action needed
[ Service ] [2017-10-12T15:57:44] debug: comparing profiles, id=7141 this=v14 other=v14
[ Service ] [2017-10-12T15:57:44] debug: profile screen status changed, screenId=14075 Connecting->Connected
[ Service ] [2017-10-12T15:57:44] debug: profile changed, storing local copy
[ Service ] [2017-10-12T15:57:50] debug: comparing profiles, id=7141 this=v14 other=v14
[ Service ] [2017-10-12T15:57:50] debug: profile screen active changed, screenId=14076 false->true
[ Service ] [2017-10-12T15:57:50] debug: new screens detected (1), preparing connectivity test
[ Service ] [2017-10-12T15:57:50] debug: starting connectivity test
[ Service ] [2017-10-12T15:57:50] debug: profile changed, storing local copy
[ Service ] [2017-10-12T15:57:53] debug: failed report: dest = 14076, ips = 5.5.4.179,192.168.1.6
[ Service ] [2017-10-12T15:57:53] debug: local profile modified, id=7141
[ Service ] [2017-10-12T15:57:53] debug: comparing profiles, id=7141 this=v14 other=v14
[ Service ] [2017-10-12T15:57:53] debug: profile screen test result changed, screenId=14076 success=``->`` failed=``->`5.5.4.179,192.168.1.6`
[ Service ] [2017-10-12T15:57:53] debug: handling new report from connectivity tester, screenId=14076 successfulIp= lastServerId=14075
[ Service ] [2017-10-12T15:57:53] debug: finished connectivity test
[ Service ] [2017-10-12T15:58:04] 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-12T15:58:04] debug: connectivity test failed for 192.168.1.6:24810
[ Service ] [2017-10-12T15:58:04] 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-12T15:58:04] debug: connectivity test failed for 5.5.4.179:24810

 

Log from my laptop:

[ Config  ] [2017-10-12T15:57:47] ERROR: failed to start crash handler: Couldn't verify crash dump directory: The system cannot find the file specified
[ Config  ] [2017-10-12T15:57:47] INFO: log filename: C:/Users/i.kolodiychik/AppData/Local/Symless/Synergy/synergy.log
[ Config  ] [2017-10-12T15:57:47] DEBUG: connecting to service
[ Config  ] [2017-10-12T15:57:47] DEBUG: connected to service
[ Config  ] [2017-10-12T15:57:48] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-10-12T15:57:49] DEBUG: current version is update to date
[ Config  ] [2017-10-12T15:57:49] DEBUG: Profile ID: 7141 name: default
[ Config  ] [2017-10-12T15:57:49] DEBUG: requesting profile snapshot
[ Service ] [2017-10-12T15:57:49] debug: connecting websocket
[ Service ] [2017-10-12T15:57:49] error: can't send profile snapshot, not yet received from cloud
[ Service ] [2017-10-12T15:57:50] debug: websocket connected
[ Service ] [2017-10-12T15:57:50] debug: comparing profiles, id=-1 this=v-1 other=v14
[ Service ] [2017-10-12T15:57:50] debug: profile id changed, -1->7141
[ Service ] [2017-10-12T15:57:50] debug: profile name changed, ->default
[ Service ] [2017-10-12T15:57:50] debug: profile server changed, -1->14075
[ Service ] [2017-10-12T15:57:50] debug: profile screen set changed, added=2 removed=0
[ Service ] [2017-10-12T15:57:50] debug: new screens detected (2), preparing connectivity test
[ Service ] [2017-10-12T15:57:50] debug: starting connectivity test
[ Service ] [2017-10-12T15:57:50] debug: profile changed, storing local copy
[ Service ] [2017-10-12T15:57:50] debug: handling local profile server changed, mode=unknown thisId=14076 serverId=14075 lastServerId=-1
[ Service ] [2017-10-12T15:57:50] debug: starting core client process
[ Service ] [2017-10-12T15:57:50] error: aborting client start, no successful connectivity test results
[ Service ] [2017-10-12T15:57:50] debug: handling local profile screen set changed, mode=client
[ Service ] [2017-10-12T15:57:50] debug: comparing profiles, id=7141 this=v14 other=v14
[ Service ] [2017-10-12T15:57:50] debug: profile screen active changed, screenId=14076 false->true
[ Service ] [2017-10-12T15:57:50] debug: new screens detected (1), preparing connectivity test
[ Service ] [2017-10-12T15:57:50] debug: profile changed, storing local copy
[ Service ] [2017-10-12T15:57:53] debug: failed report: dest = 14075, ips = 192.168.1.13
[ Service ] [2017-10-12T15:57:53] debug: local profile modified, id=7141
[ Service ] [2017-10-12T15:57:53] debug: comparing profiles, id=7141 this=v14 other=v14
[ Service ] [2017-10-12T15:57:53] debug: profile screen test result changed, screenId=14075 success=``->`` failed=``->`192.168.1.13`
[ Service ] [2017-10-12T15:57:53] debug: handling new report from connectivity tester, screenId=14075 successfulIp= lastServerId=14075
[ Service ] [2017-10-12T15:57:53] debug: finished connectivity test
[ Service ] [2017-10-12T15:58:11] 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-12T15:58:11] debug: connectivity test failed for 192.168.1.13:24810



If I try to re-arrange my computers, Sync2 crashes on my main PC (the server). Can recreate this at will.

Faulting application name: synergy2.exe, version: 0.0.0.0, time stamp: 0x59b9380d
Faulting module name: synergy2.exe, version: 0.0.0.0, time stamp: 0x59b9380d
Exception code: 0xc0000005
Fault offset: 0x0000000000083160
Faulting process id: 0x3eec
Faulting application start time: 0x01d34393a6c4a012
Faulting application path: C:\Program Files\Synergy\synergy2.exe
Faulting module path: C:\Program Files\Synergy\synergy2.exe
Report Id: 896a69f9-fda8-4f23-aa15-053309f88def
Faulting package full name: 
Faulting package-relative application ID: 

 

Edited by Ilya

Share this post


Link to post
Share on other sites

Also, both the client (left - laptop) and server (right - desktop) are green in my Synergy windows. Still nothin.

Share this post


Link to post
Share on other sites

I'm thinking it's firewall because I can't disable my domain firewall (only public and private). So, then I tried disconnecting my work VPN thinking that would be put me into one of the other 'networks', no difference. Can't get this to work no matter what I do.

Getting really close to just going back to 1.8.8 and never updating.

EDIT: It was a port issue. I allowed that port through my main PC's firewall and all is well. Used this thread as the suggestion:

 

Edited by Ilya

Share this post


Link to post
Share on other sites
14 hours ago, caveguy said:

added port 24810 inbound and outbound rules to windows firewall on both systems and mouse is working now as is cut and paste of text.

 

no way should you completely turnoff your firewall as directed !

Thanks,

Finally got it to work.

Can confirm, you need to add both outbound & inbound rules for port 24810, on both (all) computers.

And, yeah, you'd have to be an idiot to disable firewall completely.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks a lot but this make the on boarding really difficult.

Share this post


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

Thanks,

Finally got it to work.

Can confirm, you need to add both outbound & inbound rules for port 24810, on both (all) computers.

And, yeah, you'd have to be an idiot to disable firewall completely.

I second that. I would only turn off Firewall for a minute or so for preliminary testing. Your solution is perfect. Thanks, great beta testing. We're hoping this is handled automatically in beta 5. 

Share this post


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

Thanks,

Finally got it to work.

Can confirm, you need to add both outbound & inbound rules for port 24810, on both (all) computers.

And, yeah, you'd have to be an idiot to disable firewall completely.

You don't need the rules set on BOTH, just the server.

My server is my home desktop PC, and my other machine is my work laptop (I work from home) which is associated with a company domain so a lot of settings are locked out (damned GPO). I am unable to configure Windows firewall on that machine...so ALL of my firewall related changes have been done ONLY on my PC which is acting as the server.

That being said, after getting it to work yesterday (day 1), when I fired up my laptop today it was back to not working (day 2).

I had to recycle the Synergy service manually on both machines (with the Synergy windows closed on both machines) in order for it to 're-sync'.

Also, I only added the main Synergy executable to my PC's firewall rules, not the other applications. I'm going to try that now to see if on Monday (next time my work laptop is turned on) if everything auto connects.

Edited by Ilya

Share this post


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

You don't need the rules set on BOTH, just the server.

My server is my home desktop PC, and my other machine is my work laptop (I work from home) which is associated with a company domain so a lot of settings are locked out (damned GPO). I am unable to configure Windows firewall on that machine...so ALL of my firewall related changes have been done ONLY on my PC which is acting as the server.

That being said, after getting it to work yesterday (day 1), when I fired up my laptop today it was back to not working (day 2).

I had to recycle the Synergy service manually on both machines (with the Synergy windows closed on both machines) in order for it to 're-sync'.

Also, I only added the main Synergy executable to my PC's firewall rules, not the other applications. I'm going to try that now to see if on Monday (next time my work laptop is turned on) if everything auto connects.

To make it easier for the community, I exported the firewall rules from the registry. Simply run this to import said rules (assuming - which I believe is 'hard corded' - that Synergy is installed in the same place for you as it was for me.

Synergy staff, you can test this file to verify it's authenticity and either edit the post with your approval, etc. I'm not trying to scare people. Just making it easier.

** Note: PLEASE BACKUP YOUR REGISTRY IF YOU ARE AT ALL UNEASY ABOUT THIS **
Google Drive Link: https://drive.google.com/file/d/0BzjVb0QlbsKENUMzN2p3TUtJMHM/view?usp=sharing

  • Like 1

Share this post


Link to post
Share on other sites

See this thread for additional firewall discussion:

 

Share this post


Link to post
Share on other sites
31 minutes ago, Ilya said:

You don't need the rules set on BOTH, just the server.

My server is my home desktop PC, and my other machine is my work laptop (I work from home) which is associated with a company domain so a lot of settings are locked out (damned GPO). I am unable to configure Windows firewall on that machine...so ALL of my firewall related changes have been done ONLY on my PC which is acting as the server.

That being said, after getting it to work yesterday (day 1), when I fired up my laptop today it was back to not working (day 2).

I had to recycle the Synergy service manually on both machines (with the Synergy windows closed on both machines) in order for it to 're-sync'.

Also, I only added the main Synergy executable to my PC's firewall rules, not the other applications. I'm going to try that now to see if on Monday (next time my work laptop is turned on) if everything auto connects.

That might as well be true.

I did it on my secondary computer first then on the one acting as server. I haven't tested it other way around.

However I don't think it makes much of a difference for the final product (just for beta testers), because the final release will have to include opening both inbound and outbound traffic for port 24810, and it will most likely apply this on any installed app (on server or secondary computer).

Also, with F12 you can change the role of the current computer, so it would, in that case, need to be implemented on that computer.

But thanks for sharing that.

Edited by Something

Share this post


Link to post
Share on other sites
7 minutes ago, Something said:

That might as well be true.

I did it on my secondary computer first then on the one acting as server. I haven't tested it other way around.

However I don't think it makes much of a difference for the final product (just for beta testers), because the final release will have to include opening both inbound and outbound traffic for port 24810, and it will most likely apply this on any installed app (on server or secondary computer).

Also, with F12 you can change the role of the current computer, so it would, in that case, need to be implemented on that computer.

But thanks for sharing that.

For sure.

Regular users shouldn't have to touch their firewall once this product is stable and being sold as such. It's just for us early adopters.

Share this post


Link to post
Share on other sites

Thanks i had the same issue and this fix worked for me !

Share this post


Link to post
Share on other sites

I only created all of them as inbound rules and it seems to work fine. I.e. I don't seem to need the outbound.

Also, given that we can all agree that turning the firewall off is suicidal, could the official Beta troubleshooting guide be updated with these instructions? At minimum, a link to this thread perhaps? I'm guessing lots of people see "turn off the firewall" and throw their hands up. It's not such a big deal to add a few rules though.

This is the guide I mean: https://symless.com/synergy-2-beta4-troubleshooting

Edited by mdg
  • Like 1

Share this post


Link to post
Share on other sites

Ilya,

Thanks for all the great work. For right now, I am only going to 'like' your post with the coded import. If there are users that feel comfortable and understand the concept then they are on their own.

As to adding the firewall info to the original troubleshooting guide made by Nick, moderators don't have the capability to modify that, but I am going to add it to one of the other 'stickies' at the top of the forum, Preliminary Troubleshooting, started by Kelvin Tran.

  • Like 1

Share this post


Link to post
Share on other sites

I posted about this back in September when beta4 was first released. But that will have dropped down the thread list now.

I took a look at Ilya's file. It is fine and doesn't contain anything bad. However it does add exceptions for both the programs and the port. It is not necessary to do both. My preference is to add program exceptions. I have added some additional information to the sticky.

  • Like 1

Share this post


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

I posted about this back in September when beta4 was first released. But that will have dropped down the thread list now.

I took a look at Ilya's file. It is fine and doesn't contain anything bad. However it does add exceptions for both the programs and the port. It is not necessary to do both. My preference is to add program exceptions. I have added some additional information to the sticky.

Fair enough. Hopefully the new information will help some folks.

Share this post


Link to post
Share on other sites

I use my Windows 10 as the "server" and the Mac OS as the "client". Added the port 24810 to the firewall on the "server". Successfully connected.

Did not have to add it to the firewall on the Mac.

Edited by Cheryl Lomedico

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