Error ipc connection error connection refused

Windows IPC connection error #235

Server: Windows 10 Pro 1709

Client: macOS Mojave 10.14.2

I am unable to build Barrier on macOS. I was able to build it just fine Windows. When the program is created, finder puts a prohibited sign on the icon telling me that the program is incomplete or damaged. I also inspected the package’s contents and there is nothing in there accept the app icon.

Here is a Pastebin of what happens when I run the script:
https://pastebin.com/V2iAwWge

I have noticed that there is a fatal error saying «fatal: not a git repository (or any of the parent directories): .git». I am thinking this is the cause but have no clue on how to fix it.

What I do to produce this is simply dropping the script in the terminal and running it.

• When did the problem start to occur? When I ran the script.
• Is there a way to work around it? Unknown
• Does this bug prevent you from using Barrier entirely? Yes

The text was updated successfully, but these errors were encountered:

Any reason for building barrier yourself instead of using the .dmg we provide for 2.11?

I am doing 2.2 because I have been unable to use macOS as the client. It will say «Barrier is starting. » but will never actually run. I have read that if I build 2.2 I should not have this issue. I have also tried making mac the server and my pc the host but the barrier still does not work with transferring the mouse even though it says they are running and connected.

I ran into that too when making debug builds on osx, Try this

Go into build/bundle/ and edit build_installer.sh. This script is responsible for populating Barrier.app with everything it needs and generating the .dmg file.

Near the top remove or comment out the following

I also stop it from making the dmg as the debug build are too big for it causing the process to error out and leave the temp dmg image mounted. You can stop it by putting an exit right before the following block in the script (near the bottom).

Then run the script.

You saved the day @jwestfall69 I have both Windows and macOS on 2.2! Oddly enough now on both ends it is saying «Barrier is starting.» again. But I am getting different errors than I had before I build 2.2.

Error on Windows:

INFO: connecting to service.
ERROR: ipc connection error, code=19
ERROR: ipc connection error, connection refused

WARNING: failed to connect to server: Timed out
/Users/user/Downloads/barrier-master/src/lib/barrier/ClientApp.cpp,303
NOTE: connecting to ‘192.168.7.40’: 192.168.7.40:24800
/Users/user/Downloads/barrier-master/src/lib/client/Client.cpp,143
INFO: OpenSSL 1.0.2q 20 Nov 2018
/Users/user/Downloads/barrier-master/src/lib/net/SecureSocket.cpp,851

I double checked my Windows firewall just to be safe and I have allowed barrier, barriers, and barrierc as well.

EDIT:
I forgot to enable to the service on Windows and now it is running fine but still produces errors. But macOS is still not running.

Источник

P1Repair Blog

Helping the Do-It-Yourselfer

Synergy ipc connection error, connection refused Windows 8 & RaspberryPi

Using Synergy to share a mouse and keyboard between Windows 8 and Raspberry PI

I wanted to install the popular keyboard sharing software Synergy between my Windows 8 PC and a Raspberry PI running Linux. I was just starting to learn Linux and needed to get this keyboard/mouse sharing working so I could start getting used to this new (for me) OS. Unfortunately I ran into a problem making a connection between the two PCs. Not knowing my way around Linux or the Raspberry PI made it very difficult to troubleshoot…. ironically it ended up being an issue with Windows 8 Synergy software!

ipc connection error, connection refused

2013-07-07T21:01:39 NOTE: connecting to ‘192.168.0.100’: 192.168.0.100:24800
/build/synergy-E0XzMY/synergy-1.3.8/src/lib/client/CClient.cpp,115
2013-07-07T21:01:39 WARNING: failed to connect to server: Connection refused
/build/synergy-E0XzMY/synergy-1.3.8/src/cmd/synergyc/synergyc.cpp,274
2013-07-07T21:01:39 DEBUG: retry in 1 seconds

NOTE: connecting to service… ERROR:

ipc connection error, connection refused

The problem ended up being an issue with the Synergy software itself on the Windows machine. I have Windows 8 64 bit and I logically installed Synergy for 64 bit. That ended up being a big mistake. Maybe the 64 bit version is useful on some setup, but apparently not with the RaspberryPI.

Solution:

Uninstalling the 64 bit version and downloading the 32 bit version of Synergy solved the problem.
After that it was easy as PI to set up Synergy between the two PCs! Especially since I learned a lot about both Linux and the Raspberry PI in my search for a solution.

If you are looking for instructions to set up Synergy on Linux I suggest this page

I installed both synergy and quicksynergy:

At that point you can just type quicksynergy to start the easy setup. For setting up a client just click the [Use] tab, enter the IP address of the host/server and then enter raspberrypi as the screen name. This is a great way to make sure everything is working correctly. After that you can just start synergy in client mode with ‘synergyc -f ’

Next – Running Synergy automatically at desktop startup

Synergy isn’t too helpful if it’s not running and you have no keyboard on the Raspberry PI to get it running…… since I was planning on always using the built in desktop for the PI I decided to have Synergy auto start with the desktop.

Step 1.

Open a Terminal session on the Pi. /home/pi. If you are not in the directory /home/pi , change to it by typing:

Then cd to the .config directory by typing:

The ‘.’ at the start of the folder name is for hidden folders that will not show up normally.

Step 2.

Create a new directory inside .config called ‘autostart’.

cd into that new directory by typing:

Step 3.

All that remains is to edit a new configuration file. So type the following command to open the nano editor on the new file:

Edit the contents of the file with the following text.

Replace the ip address in line 4 with the ip address of your synergy server PC

Type ctrl-X and then Y to save the changes to the file.

Thats all there is to it. The next time you reboot, synergy will restart in client mode automatically. At this point you should be able to connect your USB wifi adapter directly to the RaspberryPI and free up any ports used for the mouse and keyboard….. Yeah!

If you are looking for a keyboard sharing application for Windows only I highly recommend Input Director
I have been using Input Director for over 4 years on 2 Windows PCs at my work. It’s free and I found it very easy to set up with many useful features… and stable!

Источник

ProgrammerAH

Programmer Guide, Tips and Tutorial

Synergy 1.4.12 “ipc connection error, connection refused” and other issues

Installation steps and tutorials, a search on the Internet without saying a few points need to pay attention to the problem

1. I suggest you download the latest version of Synergy, because the operation of the latest version has been greatly simplified and many bugs have been solved

2. The two versions should be consistent. If they are not consistent, all kinds of weird problems will occur

Example: Your server has 64-bit Synergy installed while your client has 32-bit Synergy installed

3
.”ipc connection error, connection refused”

“Failed to connect to Server: Protocol Error from Server “error prompt

I encountered a situation that worked the first time it was configured, but didn’t work the next day when it was restarted. The client kept reporting this error when connecting

My configuration environment: My server synergys is MAC and my Synergyc is WIN7

The reason was that I used syner1.4.10 version of synergy1.4.10 inexplicably after synergy1.4.10 was installed before and restarted. The server and client versions failed to match, so I kept reporting this error

Solution: Delete synergy from previous releases completely, and don’t be distracted

4. The inconsistency between the protocols of the Server and the Client will also result in the problems described above. For example, the Client chooses the “encryption protocol”, while the Server chooses other protocols, which can be seen in the configuration

If you have any questions, please leave a message to discuss

Источник

Can I run Synergy Client on Windows without installing it?

I have a machine to which I do not have Administrator rights. I tried building Synergy and putting together a folder with EXE’s and DLL’s, but it complains that the connection is refused (on the client) and won’t connect to the server. Is there a way to create a run folder, so that we can avoid needing to run Windows Installer?

The error log in the window (without even clicking Start to connect the client) is:

I assume it is trying to connect to synergyd.exe as a Windows service? Of course I don’t have permissions to create/start a service.

4 Answers 4

I was able to get the client to connect by copying the files from the synergy install directory from the server to the client and running synergyc from the client’s command prompt.

No, there is no portable version any more (thanks phil for answering).

This expands on @RobHerms answer with step-by-step instructions. This worked just fine for me on a limited account.

1. Download the Synergy MSI installer
2. Run this from windows command line to extract the files: msiexec /a PathToMSIfile /qb TARGETDIR=PathToTargetFolder
3. You’ll find synergyc.exe in your target folder path.
4. If you want to enable SSL, you need to put a TrustedServers.txt file with the server fingerprint in this path: C:UsersUSER_NAMEAppDataLocalSynergySSLFingerprintsTrustedServers.txt
5. Create a shortcut to synergyc.exe with the appropriate flags. Mine looks like this: «C:UsersUSER_NAMEPortableAppsSynergyPortablesynergyc.exe» -1 —enable-crypto —name PreSetClientName x.x.x.x

You can register synergyd.exe with the Windows service framework with the following steps

1. Open an admin command prompt (elevated)
2. Navigate to the directory your synergy executables are in
3. Run: synergyd.exe /install

If you fire up the Services snap in (or just run services.msc from the command line) you should notice it is now registered and running.

After that, restart your clients and you should be good to go 🙂

Источник

Synergy connection with windows 8 client

I just acquired a Dell XPS 12 ultrabook, with a flipping touchscreen. I like it, but only want to use the (small) touch screen when I’m away from home. I’d rather use synergy to control my new laptop from my desktop.

At first, it worked fine. I had an install window in the background on the laptop, and whenever that window came into focus, the client would stop moving the mouse in response to the server. I assume that’s because install windows require administrator privileges, and thus synergy can’t command such windows. This confused me at first, so I made a number of changes while this was going on, and have a hard time pinpointing what ultimately broke synergy.

At some point, perhaps when the background install finished or when I upgraded the server synergy version to 1.4.11, the client and the server both became unable to connect. For example, on the client:

with a similar message on the server. The status bar on the bottom of both windows would read «Synergy is starting.» and the stop/start button would read «stop». I get the impression the server never gets started and the client never connects.

In this setup, the client was the XPS 12 laptop was a Windows 8 64 bit box running Synergy v1.4.11, and the server is a home-built desktop running Windows 7 64 bit and Synergy v1.4.11. I’ve tried with and without passwords enabled for synergy, I’ve tried disabling firewalls, I’ve tried both the 32 bit and 64 bit versions of Synergy, and nothing helps, or even produces a visible difference in behavior. Telling the client to connect to a bogus server IP address also produces no visible change in behavior — it’s as if the server isn’t even there.

Both client and server report, in the log,

over and over again, whether the client or server is «started» or «stopped». I don’t know what this means, and I would like to. Is «ipc» inter-process communication? Is that even a network problem? Several past posts have suggested using the 32 bit version instead of 64 or reinstalling synergy.

Running the synergy server v1.4.10 from Ubuntu 13.04 produces better server-side results, but no connection. The dialog box is similar, but no warning about ipc, and when I click «start» it says

Then the configuration checkboxes for «server» and «client» etc. all gray out, and the status bar reports «Synergy is running (desktop mode). Version 1.4.11 is now available, visit website [link]». This is in contrast to «Synergy is starting.» on Windows.

I haven’t had a chance to install an Ubuntu partition on the laptop, but suspect better results. In the mean time, I don’t know what else to try, beyond restricting myself to Ubuntu (I’m not religious about operating systems; I need both).

Источник

Using Synergy to share a mouse and keyboard between Windows 8 and Raspberry PI

I wanted to install the popular keyboard sharing software Synergy between my Windows 8 PC and a Raspberry PI running Linux. I was just starting to learn Linux and needed to get this keyboard/mouse sharing working so I could start getting used to this new (for me) OS. Unfortunately I ran into a problem making a connection between the two PCs.  Not knowing my way around Linux or the Raspberry PI made it very difficult to troubleshoot…. ironically it ended up being an issue with Windows 8 Synergy software!

ipc connection error, connection refused

2013-07-07T21:01:39 NOTE: connecting to ‘192.168.0.100’: 192.168.0.100:24800
/build/synergy-E0XzMY/synergy-1.3.8/src/lib/client/CClient.cpp,115
2013-07-07T21:01:39 WARNING: failed to connect to server: Connection refused
/build/synergy-E0XzMY/synergy-1.3.8/src/cmd/synergyc/synergyc.cpp,274
2013-07-07T21:01:39 DEBUG: retry in 1 seconds

NOTE: connecting to service… ERROR:

The problem ended up being an issue with the Synergy software itself on the Windows machine. I have Windows 8 64 bit and I logically installed Synergy for 64 bit. That ended up being a big mistake. Maybe the 64 bit version is useful on some setup, but apparently not with the RaspberryPI.

Solution:

Uninstalling the 64 bit version and downloading the 32 bit version of Synergy solved the problem.
After that it was easy as PI to set up Synergy between the two PCs! Especially since I learned a lot about both Linux and the Raspberry PI in my search for a solution. 

If you are looking for instructions to set up Synergy on Linux I suggest this page

I installed both synergy and quicksynergy:

sudo apt-get install synergy

sudo apt-get install quicksynergy

At that point you can just type quicksynergy to start the easy setup. For setting up a client just click the [Use] tab, enter the IP address of the host/server and then enter raspberrypi as the screen name. This is a great way to make sure everything is working correctly. After that you can just start synergy in client mode with ‘synergyc -f <server IP address>’ 

Next – Running Synergy automatically at desktop startup

Synergy isn’t too helpful if it’s not running and you have no keyboard on the Raspberry PI to get it running…… since I was planning on always using the built in desktop for the PI I decided to have Synergy auto start with the desktop.

Then cd to the .config directory by typing:

cd into that new directory by typing:

If you are looking for a keyboard sharing application for Windows only I highly recommend Input Director
I have been using Input Director for over 4 years on 2 Windows PCs at my work. It’s free and I found it very easy to set up with many useful features… and stable!

You have encountered the same problems with installing the latest version of Synergy 1.4.12 as I did. If you have encountered the same problems as I did, I hope you can take less detour

Installation steps and tutorials, a search on the Internet without saying a few points need to pay attention to the problem

1. I suggest you download the latest version of Synergy, because the operation of the latest version has been greatly simplified and many bugs have been solved

2. The two versions should be consistent. If they are not consistent, all kinds of weird problems will occur

Example: Your server has 64-bit Synergy installed while your client has 32-bit Synergy installed

3
.”ipc connection error, connection refused”

“Failed to connect to Server: Protocol Error from Server “error prompt

I encountered a situation that worked the first time it was configured, but didn’t work the next day when it was restarted. The client kept reporting this error when connecting

My configuration environment: My server synergys is MAC and my Synergyc is WIN7

The reason was that I used syner1.4.10 version of synergy1.4.10 inexplicably after synergy1.4.10 was installed before and restarted. The server and client versions failed to match, so I kept reporting this error

Solution: Delete synergy from previous releases completely, and don’t be distracted

4. The inconsistency between the protocols of the Server and the Client will also result in the problems described above. For example, the Client chooses the “encryption protocol”, while the Server chooses other protocols, which can be seen in the configuration

If you have any questions, please leave a message to discuss

I just acquired a Dell XPS 12 ultrabook, with a flipping touchscreen. I like it, but only want to use the (small) touch screen when I’m away from home. I’d rather use synergy to control my new laptop from my desktop.

At first, it worked fine. I had an install window in the background on the laptop, and whenever that window came into focus, the client would stop moving the mouse in response to the server. I assume that’s because install windows require administrator privileges, and thus synergy can’t command such windows. This confused me at first, so I made a number of changes while this was going on, and have a hard time pinpointing what ultimately broke synergy.

At some point, perhaps when the background install finished or when I upgraded the server synergy version to 1.4.11, the client and the server both became unable to connect. For example, on the client:

NOTE: starting the client
NOTE: config file: XXXXXX
NOTE: log level: NOTE

with a similar message on the server. The status bar on the bottom of both windows would read «Synergy is starting.» and the stop/start button would read «stop». I get the impression the server never gets started and the client never connects.

In this setup, the client was the XPS 12 laptop was a Windows 8 64 bit box running Synergy v1.4.11, and the server is a home-built desktop running Windows 7 64 bit and Synergy v1.4.11. I’ve tried with and without passwords enabled for synergy, I’ve tried disabling firewalls, I’ve tried both the 32 bit and 64 bit versions of Synergy, and nothing helps, or even produces a visible difference in behavior. Telling the client to connect to a bogus server IP address also produces no visible change in behavior — it’s as if the server isn’t even there.

Both client and server report, in the log,

NOTE: connecting to service...
ERROR: ipc connection error, connection refused

over and over again, whether the client or server is «started» or «stopped». I don’t know what this means, and I would like to. Is «ipc» inter-process communication? Is that even a network problem? Several past posts have suggested using the 32 bit version instead of 64 or reinstalling synergy.

Running the synergy server v1.4.10 from Ubuntu 13.04 produces better server-side results, but no connection. The dialog box is similar, but no warning about ipc, and when I click «start» it says

NOTE: stopping synergy desktop process
NOTE: starting server
NOTE: config file: /tmp/qt_temp.TT2295
NOTE: log level: NOTE
2013-05-01T00:44:24 NOTE: started server, waiting for clients
    /build/buildd/synergy-1.4.10/src/lib/synergy/CServerApp.cpp,612

Then the configuration checkboxes for «server» and «client» etc. all gray out, and the status bar reports «Synergy is running (desktop mode). Version 1.4.11 is now available, visit website [link]». This is in contrast to «Synergy is starting.» on Windows.

I haven’t had a chance to install an Ubuntu partition on the laptop, but suspect better results. In the mean time, I don’t know what else to try, beyond restricting myself to Ubuntu (I’m not religious about operating systems; I need both).

Edventures in Normalcy

Была ли эта страница полезной?

0 / 5 — 0 рейтинги

В Synergy Q & A есть несколько ответов на этот вопрос. Кто-нибудь из них работал на вас?

http://synergy-foss.org/osqa/questions/1862/why-do-i-see-the-ipc-connection-error-connection-refused-error

Кажется, есть несколько потенциальных причин:

1) Вы обновили Synergy, и у нового графического интерфейса возникли проблемы с подключением к фоновой службе. Это можно исправить, открыв командную строку с правами администратора и выполнив команду

sc delete synergy

Затем переустановите последнюю версию.

2) Или вы используете Windows 7 32-бит? Если вы случайно установили 64-разрядную версию Synergy, графический интерфейс запустится, но фоновая служба не запустится (это 64-разрядный код). Даже пользователи 64-битной Windows сообщили, что запуск 32-битной версии работает для них лучше; у них были проблемы с 64-битной, так что попробуйте.

Если все остальное в порядке, наконец, попробуйте запустить службу вручную, нажав Windows-R, а затем в диалоговом окне «Выполнить» введите services.msc . Найдите сервис синергии в списке и скажите его «Пуск». Если при запуске появляются ошибки, вы сможете увидеть их здесь и опубликовать с дополнительной информацией.