C S Posted October 11, 2017 Share Posted October 11, 2017 I've been playing with Windows firewall rules, as I do not like services listening unnecessarily on what Windows calls "Public" connections. I've found a few interesting behaviors with 2.0 Beta 4, with a Windows 10 server and Windows 7 client. 1. By default, the Synergy installer permits synergy2 and synergys to listen on All connection types. Changing this to "Domain and Private" causes the client and server to fail to find each other, even when all my interfaces are in the Private zone. 2. I have to manually permit synergyd.exe to accept connections on all zones on the server, otherwise the client cannot connect. The installer should take care of this firewall addition. Can anyone else duplicate the behavior of #1? I've seen #2 documented elsewhere in the forum. I have not needed to permit synergyc to listen. Link to comment Share on other sites More sharing options...
GranPaSmurf Posted October 15, 2017 Share Posted October 15, 2017 c s, is your issue resolved? I'm looking through older unanswered posts. This thread has some in-depth Win firewall work: https://symless.com/forums/topic/4312-performed-troubleshooting-just-upgraded-to-200-beta4-no-connectivity/#comment-17610 Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted October 31, 2017 Synergy Team Share Posted October 31, 2017 Finally, Synergy 2 beta5 is here! Could you give it a try? Get the latest version: Synergy-v2.0.0-beta5 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.