Phil Posted June 26, 2016 Author Share Posted June 26, 2016 FYI I had this error just now having upgraded and it turns out the solution was to notice that windows 10 had changed one of the systems to thinking its network was public rather than private. This meant that it was being blocked by windows firewall, changing it back to private meant I got a warning when starting synergy and the option to allow access which I selected - problem now fixed. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.