Jun
25
Synergy 1.3.1 - WARNING: failed to connect to server: Time Out
Posted by john in help, windows

I’ve been using Synergy for just over 3 months now and simply love it. I use to use a KVM but found the image quality to be really bad when using it.

For anyone whose been having the error “WARNING: failed to connect to server: Time Out”. Try changing the connect to name on the client machine to the IP of the server. For some reason my Windows PC name was not working but the IP connected instantly.

You may even want to manually set your IP to always be that number so it will never change when the DHTP tried to issue a new one.

Hope this helps some one else out there.

- John

Update: Also if you’re using a VPN and your connection to the server machine gets dropped, you must disconnect from the VPN in order to reconnect. This was causing some headackes for me a while back.

Also, if you’re having trouble with Synergy capitalizing characters or holding down the Ctrl key, this post should help you out.

8 Responses to “Synergy 1.3.1 - WARNING: failed to connect to server: Time Out”

PR Says:

Synergy IS simply wonderful. I have used it for over a year and after replacing one machine received the error. The IP address worked instantly. Thank you for posting!

[Reply]

Brandon Says:

I have been using synergy for several months now and I must say it is awesome. I use it along with a kvm because I use dual display for one of the machines. However just today I could not get them to reconnect so I did as described above and instantly I am up and running again.

Thanks!
Brandon

[Reply]

David Says:

I had exactly the same problem, after a period of unreliability from Synergy. It seemed to have acquired a mind of its own. Had it running with one PC with two monitors and a second with one monitor and it originally worked seamlessly over the three screens with no problem but the program started working intermittently and then suddenly decided to give up completely, only displaying the green circle icon without the “lightning” connected symbol in the middle, together with the “Synergy 1.3.1 - WARNING: failed to connect to server: Timed Out” error on the client PC. I tried re-installing but no joy. The cure given by “john” worked instantly, although I did have an instance of a jerky cursor on the client screen only afterwards, (something I`ve seen before), which seemed to be cured by a reboot. Anyone know what`s going on here and does the author know? I did post on the Source Forge Synergy help forum, but had no responses. I will probably post the answer there for anyone in the same boat.

[Reply]

john reply on June 17th, 2008:

I beleive the problem has less to do with Synergy and more to do with Windows networking. The problem is the server PC does not know what IP to assign to the other machine based on the PC’s name. So by using the IP, you are by passing that.

[Reply]

David Says:

Ah, yes, but surely that begs the question as to why it worked quite happily in the previous configuration (i.e.name and not IP address) for the best part of a year before deciding not to work. Why does the server PC also not need that modification? My set-up is now working quite happily with a mix-and-match. If it ain`t broke, don`t fix it - I shall leave well enough alone :-) Regards to all.

[Reply]

Mike Carlson Says:

Hope there is someone at the other end of this to solve my problem. Think I have hooked up the computers properly but it does not work. The server says
FATAL: failed to startserver: cannot bind address: WSAEINVAL. The client says WARNING: failed to connect to server: address not found for: Michael. Anyone able to diagnose and solve this issue? It would be greatly appreciated. Thanks.

[Reply]

Grim Says:

if you have tried the above and are still havening problems make sure to disable windows firewall or route thru tcp and udp port 24800 (that worked for me)

[Reply]

john reply on November 13th, 2008:

I would recommend disabling the Windows firewall either way. It only seems to get in the way.

[Reply]

Leave a Reply