Leaderboard

I get it, it's 5$ and the 1st synergy was good so i was glad to pay just to encourage continued development. But what in the............. did you guys do??? The is at the idea stage not at Beta..... Look at the picture I took. It looks nothing, or should I say has none of the features you mention already having. No bugs either, which is great, but it also doesnt do anything. Ok, im done making fun at this disaster, and I do this because i want you guys to succeed but remember one thing, logitech has stepped on your turf with their MX2. Their mouse does it a lot better, much simpler

Switched back to v1.8.8 which is perfectly smooth. The beta 4 feels like it's trying to stop or slow down at every horizontal line on the monitor or something like that. It's not usable to work with. Waiting for beta 5 now...

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.

It doesn't. It's a totally separate code base. Synergy Core is a different binary to everything else.

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

Having donated for Nicks rent years ago, i bought licenses of synergy1 twice for myself later, and today i paid for again for synergy2. And guess what? It feels good. Synergy is tremendously useful. If i met Nick on the street, i would happily buy him beer and pizza. Even if i don't use the synergy2 features yet (needs -ehem- debugging...), paying $15 today is a (very small) investment in the continued development of the software. So please don't haggle over "lifetime access" - just buy the symless folks a pizza now and then. :-)

Hi, I went back in the firewall section and added a rew on both computer for the in and out to allow port 24810 at all level, restart services and synergy on both computer. It's now working. Thanks,

Using Linux Mint Mate as server, and Windows 10 as client I have Synergy2 working.... semi automatically! Only one keyboard & mouse required. Basically because I'me talking about 2 home computers (not work stuff) so I set Windows 10 to start without the login screen ( not advised if you're using it at work) - and put Synerg2 desktop app short cut in the startup folder - so my Windows computer (client) just needs switching on. When I do this then Synergy (the service) is automatically running, and so is Synergy the desktop app. Now my Linux computer -when I turn that on, there

Support/Feature Request: My network URL filter was stopping synergyd from accessing 165.227.29.181:8081 because that site had not been categorized. I see that's at Digital Ocean, so I assume the IP address could change. What is the URL or hostname which is accessed by synergyd, so that those of us behind corporate firewalls can permit the traffic through without having to chase future IP address changes? Are there other URLs or hostnames/ports/protocols which the processes access which need to be whitelisted on edge-facing firewalls? For reference, I installed Synergy 2.0, saw a good TCP/

I'm a fan of the automatic (what we call JFW) configuration and haven't yet felt there were any settings I wanted/needed to adjust. The one thing that has dogged me a bit, particularly when debugging VPN "why doesn't it JFW?" issues has been a lack of insight into the IP that the machine is reporting for itself, and the IP it receives from the Symless server for the location of it's client(s)/server. Even a simple right-click-on-machine "info" panel would help greatly with debugging, particularly the address(es):port(s) that have been autoconfigured.