github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #118] MacOS 10.13.6 and Windows 10 not working in either direction #92

New issue

Closed

opened 2026-05-05 05:14:18 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:14:18 -06:00

Owner

Originally created by @cornercase on GitHub (Aug 23, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/118

Operating Systems

Computer A: MacOS 10.13.6
Computer B: Windows 10 Pro ver 1 (build 17143.228) with current patches

Barrier Version

Mac - 2.1.0-RELEASE-8b69f9fe
Windows - 2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

Install Barrier fresh on both machines.
Pick one as the server, allow auto client setup on the other
Notice that the screen auto config pops up on server, select a screen location
Mouse never moves between screens

I tried it with both Mac and Windows as server, it does not matter. Same behavior either way.

Other info

The windows program never progresses past "Barrier is starting," while the Mac version will say "Barrier is running" after starting.

I also tried disabling the firewall on both machines and running as administrator on windows.

When did the problem start to occur? Always
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? Yes

Put anything else you can think of here.

Originally created by @cornercase on GitHub (Aug 23, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/118 ### Operating Systems ### Computer A: MacOS 10.13.6 Computer B: Windows 10 Pro ver 1 (build 17143.228) with current patches ### Barrier Version ### Mac - 2.1.0-RELEASE-8b69f9fe Windows - 2.1.0-RELEASE-0b2dfd80 ### Steps to reproduce bug ### 1. Install Barrier fresh on both machines. 2. Pick one as the server, allow auto client setup on the other 3. Notice that the screen auto config pops up on server, select a screen location 4. Mouse never moves between screens I tried it with both Mac and Windows as server, it does not matter. Same behavior either way. ### Other info ### The windows program never progresses past "Barrier is starting," while the Mac version will say "Barrier is running" after starting. I also tried disabling the firewall on both machines and running as administrator on windows. * When did the problem start to occur? Always * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? Yes Put anything else you can think of here.

gitea-mirror closed this issue

2026-05-05 05:14:19 -06:00

gitea-mirror commented

2026-05-05 05:14:22 -06:00

Author

Owner

@cornercase commented on GitHub (Aug 25, 2018):

It turns out there was a secondary firewall running on one machine, so once I opened the port, the problem vanished.

@cornercase commented on GitHub (Aug 25, 2018): It turns out there was a secondary firewall running on one machine, so once I opened the port, the problem vanished.

gitea-mirror commented

2026-05-05 05:14:24 -06:00

Author

Owner

@Vrak commented on GitHub (Sep 5, 2018):

What port did you open? How can I determine which port I need to open (if it's different)?

[edit]
Nevermind. I got it working without needing to know a port number.
The extra firewall was on my windows machine. I added an exception for barriers.exe (Barrier server) to both of the Windows firewalls

@Vrak commented on GitHub (Sep 5, 2018): What port did you open? How can I determine which port I need to open (if it's different)? [edit] Nevermind. I got it working without needing to know a port number. The extra firewall was on my windows machine. I added an exception for `barriers.exe` (Barrier server) to both of the Windows firewalls

No labels

Rows
Columns