Mattias Posted March 18, 2018 Share Posted March 18, 2018 For some reason, synergy 2.0.7 tries to connect to 192.168.56.1 which is an ip that none of my computers is associated with. It might have been one of my virtual network interfaces, but disabling that interface, clearing configs and restarting the service doesn't do anything. Is there a way for me to force it to use the "correct" network interface? Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted March 18, 2018 Synergy Team Share Posted March 18, 2018 It attempts to connect to all IPs, so you can safely ignore the .56.1 attempt. What problem are you experiencing? Have you contacted our support team yet? https://symless.com/contact/customer-support Link to comment Share on other sites More sharing options...
Mattias Posted March 18, 2018 Author Share Posted March 18, 2018 The problem is that I can't establish a connection between my computers. One shows up as green on both computers, the other doesn't. Link to comment Share on other sites More sharing options...
Mattias Posted March 18, 2018 Author Share Posted March 18, 2018 Ok, finally solved it. The real problem wasn't with the network "ERROR" messages as you said, but with the display "WARNING" ones. The real problem was that the service, running as a different user, didn't have access to the X session. Running "xhost +" as mentioned in this comment fixed it for me: https://symless.com/forums/topic/4510-problem-connecting-to-auto-config-service/?do=findComment&comment=19819 Is there a way I can do this without opening up my xsession for every host? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.