mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #55] Issue between Windows #43
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @massimo0315 on GitHub (May 30, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/55
II start the program on a PC the server and on the other the client, the connection seems to be successful but remains on: "Barrier is starting". The association between the devices is detected, but beyond the association you can not do anything else. In the log this appears in random:
[2018-05-30T13: 26: 23] ERROR: ipc connection error, code = 19
[2018-05-30T13: 26: 23] ERROR: ipc connection error, connection refused
I due pc hanno entrambi Windows 10 aggiornato all'ultima versione mentre barrier è l'ultima versione(2.1.0)
@massimo0315 commented on GitHub (May 30, 2018):
Now I've: failed to get desktop path, no drop target available, error=2
@shuklaalok7 commented on GitHub (May 31, 2018):
Almost similar thing happening between a Windows server and macOS client. See #53.
@massimo0315 commented on GitHub (Jun 6, 2018):
is there any way to solve?
@KaNe23 commented on GitHub (Aug 7, 2018):
I got this error, when the barrier service was not running on windows and was somehow not automatically starting. That's why the IPC (inter process communication) was not working.
The error:
failed to get desktop path, no drop target available, error=2is not fatal, have this one as well and everything works fine.
The other trouble I had, was the windows firewall, I basically added all execution files in the barrier
folder to the allowed applications and it worked.
@walker0643 commented on GitHub (Sep 8, 2018):
Hi @massimo0315 -
Like @KaNe23 said, this error is due to the barrierd service not running. From your Services window (start, run, "services.msc") right-click the Barrier service and left-click Start from the popup menu. To save yourself grief in the future you could change the property "Startup type" to "Automatic" for the Barrier service by double-clicking on the Barrier line, making that change in the drop-down box, and clicking the OK button.
I would be interested to know why the service wasn't started automatically? Did you build barrier from source or use an installer? Anything else you could share about why the service didn't start?
Closing for now. Please reopen if you feel the issue hasn't been resolved. Thanks.
@stevesobol commented on GitHub (Apr 13, 2019):
I have the same issue on Windows 10 Pro x64, connecting to macOS 10.14.3.
With the Mac as the server, I can share the Mac's keyboard and mouse with the Win10 laptop, but I'm trying to share the Win10 laptop's mouse and keyboard, and that isn't working.
@iserl commented on GitHub (Apr 24, 2019):
Bro its becuase barrierD isnt running trust me dude
(edit) Just wanted to say that this wasn't a reply to you, stevesobol, but rather showing that it isn't necessarily that the service isn't started. Im pretty sure whats happening is that the service itself breaks, and requires reinstallation.
@stevesobol commented on GitHub (Apr 24, 2019):
Yeah, I should have commented again when I got it working. Sorry (and thanks for the advice).
That wasn't my problem. There are three or four binaries - and I whitelisted the wrong one in Windows Firewall.
barriers.exewhas what I needed to whitelist.@ZeroBudgetDevelopments commented on GitHub (Mar 2, 2020):
dont know if anybody has solved this but i had a nightmare of night to solve it the way i made it work was by going to settings on the barrier server interface and clicking it then going to the networking part in the ip address change this to the exact address given by the barrier server app exit settings and reload or restart barrier do this for every network you use and viola your problems shoul be solved it took me all night to crack this i use my home network and my mobile hotspot network now i know i have to change the ip in the app i should be all good :)
@wxsgt commented on GitHub (Jun 23, 2021):
Running the Server on Win 10 Starts fine, Client on Win 10 will not start getting this error. Just installed today, manually allowed all barrier exe files through firewall and the barrier service will not start. The path links to barrierd but im getting a 193: 0xc1 error which means its not connecting through for some reason.
@yoshisatose commented on GitHub (Jul 2, 2021):
I had the same issue but solved it.
https://bobcares.com/blog/error-193-0xc1-service-fails-to-start/
In my case, my system drive (C:) had a file (not a folder) named "Program". When I removed this file from the system drive, I could start the barrier service.
@wxsgt commented on GitHub (Jul 2, 2021):
That was exactly it thank you!