[GH-ISSUE #145] Connection issue because of security constraint #116

New issue

Open

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

gitea-mirror commented

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

Owner

Originally created by @quma4419 on GitHub (Oct 7, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/145

Operating Systems

Server: macOS 10.14

Client: Windows 7

Barrier Version

2.1.0

Steps to reproduce bug

Start the "server".
Start the "client".
Connection cannot be established.

Other info

The OS version doesn't really matter in this case.
The macOS machine provides the keyboard and mouse, so it has to be started as a "server".
The macOS machine has the firewall enabled and configured to block all incoming traffic. This is intentional. So please do not respond with "turn off your firewall" or "add a firewall exception".
The macOS machine is a client machine, that means it is not supposed to listen on ports, handle external network traffic and do server stuff. That means that it should not be necessary to penetrate the firewall or (even worse) to shut it down.
The goal is to control a Windows PC with the peripherals from a macOS laptop. This means (in a simple way) that input commands are transferred to the Windows PC. This shouldn't require that my laptop must become a server.

The question is:

Will there be a version in the future where it is possible to establish the connection the other way around so that the machine (which provides the keyboard and mouse) can connect to the other machine(s) (that provides the machine and the screens)?

You can interpret this as a feature request if you like.

Originally created by @quma4419 on GitHub (Oct 7, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/145 ### Operating Systems ### Server: macOS 10.14 Client: Windows 7 ### Barrier Version ### 2.1.0 ### Steps to reproduce bug ### 1. Start the "server". 2. Start the "client". 3. Connection cannot be established. ### Other info ### * The OS version doesn't really matter in this case. * The macOS machine provides the keyboard and mouse, so it has to be started as a "server". * The macOS machine has the firewall enabled and configured to block all incoming traffic. This is intentional. So please do not respond with "turn off your firewall" or "add a firewall exception". * The macOS machine is a client machine, that means it is not supposed to listen on ports, handle external network traffic and do server stuff. That means that it should not be necessary to penetrate the firewall or (even worse) to shut it down. * The goal is to control a Windows PC with the peripherals from a macOS laptop. This means (in a simple way) that input commands are transferred to the Windows PC. This shouldn't require that my laptop must become a server. The question is: Will there be a version in the future where it is possible to establish the connection the other way around so that the machine (which provides the keyboard and mouse) can connect to the other machine(s) (that provides the machine and the screens)? You can interpret this as a feature request if you like.