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

41 posts in this topic

gee4vee 3

Just wanted to post this in case it helps others. I found that if I added all the Synergy 2 processes (synergy2.exe, synergyc.exe, synergyd.exe, synergys.exe) to Windows Firewall (in both public and private networks), I was able to connect with my MBP laptops. It only worked having all of them added. By default only some of them get added.

Share this post

Link to post

Share on other sites

Ilya 1

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.

Share this post

Link to post

Share on other sites

Ilya 1

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:

Share this post

Link to post

Share on other sites

Ilya 1

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.

Share this post

Link to post

Share on other sites

Allan Jackson 5

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'.

That was my experience as well. When I got into work this morning, it was broken again. I restarted the computer that just slept overnight (the other computer was off), and then it started working again.

2

Share this post

Link to post

Share on other sites

Ilya 1

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.

Share this post

Link to post

Share on other sites

Something 1

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.

Share this post

Link to post

Share on other sites

Ilya 1

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

James Osborn 2

It took me a while to find this thread. My W10 firewall is enforced on by group policy so I couldn't even test the "turn it off" method. Adding the firewall exceptions solved my problem too.

One thing to note in my case: The server machine Desktop Icon went GREEN immediately, but the client Desktop Icon stayed dark. Some kind of communication was possible because it showed the same way on the client. And it responded to rearrangement of the two desktops on either server or client. The logs showed that it was failing connectivity tests which cleared with the firewall exceptions on the server. Then BOTH Desktop Icons went GREEN.

I understand the principle behind making the user interface super clean and automatic. But when it doesn't work, it is kind of frustrating and leaves the user wondering WTF is going on. Had I known even the simple fact that both icons must turn GREEN, I would have been better off. I thought the highlighting was showing which was the server (not exactly). How about highlighting right there on the ultra simple UI what the problem is? Like in my case highlight the client Desktop Icon in RED and use a tooltip hover to provide helpful information like: "The client is unable to connect to the server"?

2

Share this post

Link to post

Share on other sites

mdg 1

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.

Share this post

Link to post

Share on other sites

GranPaSmurf 107

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.

1

Share this post

Link to post

Share on other sites

IT Troll 22

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.

1

Share this post

Link to post

Share on other sites

Ilya 1

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.