Howard Jones 0 Posted January 4, 2016 Share Posted January 4, 2016 Synergy 1.7.5 on Windows 7 - I get an error message: "FATAL: failed to start server: cannot bind address: The specified address is not available from the local machine" Thing is, I didn't specify the address. In fact, I can't see how to do that in the config file or UI. So Synergy is picking a non-existent address and then failing to bind to it! I do have quite a few network interfaces, and a few of them don't actually go anywhere (loopback or VM-related interfaces). There's nothing I could see in the manual to say what the bold address in the list means, but the one in bold is a VM-related NIC, not an actual LAN connection, in case it's relevant. I'm manually entering the (correct) IP for the server on my client, not auto-config. This all did work when I first installed Synergy, but now fails reliably, even across reboots. Any ideas? I don't understand how it can find the IP of an interface, and then say that it doesn't exist! Link to post Share on other sites
Animesh Pathak 0 Posted January 8, 2016 Share Posted January 8, 2016 The network interface ordering could be in play here. Try whats suggested in the following thread: viewtopic.php?f=9&t=52 HTH. Link to post Share on other sites
Howard Jones 0 Posted January 11, 2016 Author Share Posted January 11, 2016 Nope, still the same thing after moving the LAN interface to the top of the list. And actually, the interface in bold (I guess this is the one advertised with autoconfig?) is still a different VMware virtual interface. I'm not using autoconfig, so that's not really an issue, but the failure to bind obviously is! Link to post Share on other sites
Popular Post Rob Hawkins 2 Posted November 28, 2016 Popular Post Share Posted November 28, 2016 I had the same problem but it was self-inflicted. I corrected the IP address in "Interface" in "Edit>Settings" to fix it. Â http://symless.com/forum/viewtopic.php?f=19&t=917&p=2750#p6389 2 Link to post Share on other sites
_gh_ 0 Posted March 25, 2020 Share Posted March 25, 2020 My problem was that although the screen was showing the correct (new DHCP) address inside settings it was still the previous IP address in the interface. Link to post Share on other sites
Ameet 0 Posted September 6, 2020 Share Posted September 6, 2020 Placed a tick on "Enable Auto Config". Stop and Start again. This worked for me ....hopefully helps others. Cheers Link to post Share on other sites
JackLH 0 Posted January 4, 2022 Share Posted January 4, 2022 In version 1.14-2, I had to go to Edit | Preferences | Network IP and update the IP to the new IP address of my network interface (recently changed) despite the correct IPs showing on the main screen. (Intuitively you'd think this would be a setting found under the "Server Configuration" button and not under "Preferences"--but I suppose it's a preference to have it work or not.) Link to post Share on other sites
Jamil 0 Posted November 23, 2023 Share Posted November 23, 2023 On 1/5/2022 at 4:04 AM, JackLH said: In version 1.14-2, I had to go to Edit | Preferences | Network IP and update the IP to the new IP address of my network interface (recently changed) despite the correct IPs showing on the main screen. (Intuitively you'd think this would be a setting found under the "Server Configuration" button and not under "Preferences"--but I suppose it's a preference to have it work or not.) This has solved my problem too. But shouldn't it pickup when the address change on the interface. Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now