|
Some users were having this issue, so I figured I'd post the answer (below). |
|
Update: Also, see answer by ApexSciences (using 32-bit version over 64-bit version). The problem is that the GUI can't connect to the service, most likely because it's not running. Old versions of the service are sometimes not removed (this is a bug). To workaround this problem, run the following command as administrator:
Then reinstall the latest version of Synergy. I have been using version 1.38 and today it started with this problem. I tried to uninstall and then install the latest version and now I have Access to Syng denied and on the Synergy setup the log is giving: Error: ipc connection error, connection refusted Note: contting to service............ As not being the most computer savy I am not sure of how to do the suggest fix. Any help would be appreciated. (PS I tried to post a question but it never showed up)
(04 Jan, 13:21)
cvierret
|
|
On my side, I also faced the error "ipc connection error, connection refused".
After activating the debug log, I saw I just needed to declare the client in the server configuration : |
|
Go to Task Manager, Services Tab, Scroll down to "Synergy" and make sure the status is "Running" If the status is "Stopped", right click it and hit "Start Service" |
|
I came up with a solution for WinXP SP2, we have a certain application that disallows the upgrade to SP3. When installing 1.4.10, right click the installer, install as admin, and UNCHECK the "protect from viruses" checkbox. Worked flawlessly for me after many failed attempts to install. I was getting the repetitive "ipc connection refused". Now it's perfect. One more addition after doing a second install on sp2 you need to add two dll files in windows/system32. Msvcp100.dll and msvcr100.dll . You should be able to find it in the system32 folder of a neighboring xpsp3 machine! Cheers!
(12 Mar, 13:31)
mckenziealexr
|
|
I have Win 7 64 on server and a fresh install of Windows XP SP2 32 Bit. Installed Synergy. Would not connect. Installed Service Pack 3 and updates, uninstalled Synergy, then re-installed Synergy. Connected up right after and is working great. Seems to require SP3. |
|
I had this issue as well after installing 1.4.10 to work with a new Client (Windows 7 x64 server with Windows XP x86 client). I made the mistake of not looking clearly and accidently downloading the 7zip installer (named synergy.exe) from an ad. After that point IE refused to open, nor would Windows Update. As such the installer was not able to add items to the Start Menu and also missed DLLs that are needed. I had to reformat and reinstall Windows on the client (where I was getting the error). This time I ran all available Windows Updates first. Then downloaded Synergy (correctly the first-time). Then it installed and connected just fine. |
|
I have exactly the same problem on a brand new installation of Windows XP SP3 32bit. It will not connect not matter what, brand new version of synergy downloaded today (5 Dec 2012). From my experience it has nothing to do with SP2. It will not work under SP3 either... I guess the installation has to do something with it since I didn't see a service running either. I guess I was wrong donating before trying out the software. Uninstalling from both computers. What a waste of my time... |
|
I was experiencing this problem on a fresh install of Windows XP SP2. Installing Service Pack 3, uninstalling Synergy, then re-installing Synergy is the solution that worked for me. I do not believe that the current version of Synergy works with Windows XP SP2 and requires SP3 to work properly. Sounds likely -- we don't test on SP2.
(25 Oct '12, 12:26)
nbolton ♦♦
|
So after that headache, I just said "screw it" and ... re-installed the x32 versions on all the machines, client and server alike and poof! It works just fine! is it possible that the x64 version has some other problems that prevent it from working even on x64 machines??
Thank you for proposing this solution. This solved my connection issues with the service on my 64bit machine. I wouldn't last more than a few hours before I had to reinstall.
(09 Jun, 09:57)
Richard
|