github-starred/barrier

Fork 0

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

[GH-ISSUE #193] Impossible to connect linux client to windows server #158

New issue

Closed

opened 2026-05-05 05:27:08 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

2026-05-05 05:27:08 -06:00

Owner

Originally created by @YoannBrillet on GitHub (Dec 7, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/193

Operating Systems

Server: Windows 10 1803

Client: Kali Linux 2018.4

Barrier Version

2.1.0 (client and server)

Steps to reproduce bug

Start server on windows
Start client on linux with IP address of the server
connection timeout

Other info

Firewall rules open on the windows
and fun fact but if the server is on the linux and the client on the windows it works (but not what I want)

Originally created by @YoannBrillet on GitHub (Dec 7, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/193 ### Operating Systems ### Server: Windows 10 1803 Client: Kali Linux 2018.4 ### Barrier Version ### 2.1.0 (client and server) ### Steps to reproduce bug ### 1. Start server on windows 2. Start client on linux with IP address of the server 3. connection timeout ### Other info ### Firewall rules open on the windows and fun fact but if the server is on the linux and the client on the windows it works (but not what I want)

gitea-mirror closed this issue

2026-05-05 05:27:11 -06:00

gitea-mirror commented

2026-05-05 05:27:13 -06:00

Author

Owner

@dayne commented on GitHub (Dec 8, 2018):

I'm doing this every day.

I've got two setups with same version of barrier:

Linux Client -> Windows 10 Server (has the keyboard & mouse)
Linux Client -> Mac OSX Server (has k&M)

Double check server is running, the port is open, and the client is able to connect to the port.

On the linux box verify you can connect to port 24800 on the windows box using the nc tool:

nc -vz 192.168.56.1 24800

Correct output would be: Connection to 192.168.56.1 24800 port [tcp/*] succeeded!

If that doesn't work then you need to keep debugging the server/port/network.

@dayne commented on GitHub (Dec 8, 2018): I'm doing this every day. I've got two setups with same version of barrier: * Linux Client -> Windows 10 Server (has the keyboard & mouse) * Linux Client -> Mac OSX Server (has k&M) Double check server is running, the port is open, and the client is able to connect to the port. On the linux box verify you can connect to port 24800 on the windows box using the `nc` tool: `nc -vz 192.168.56.1 24800` Correct output would be: `Connection to 192.168.56.1 24800 port [tcp/*] succeeded!` If that doesn't work then you need to keep debugging the server/port/network.

gitea-mirror commented

2026-05-05 05:27:15 -06:00

Author

Owner

@AngelJA commented on GitHub (Dec 8, 2018):

Did you test if it works if you disable the Windows firewall completely? I just set this up and had issues, but I found that the rule that Windows adds automatically is for barrier.exe instead of barriers.exe. Changing that allowed me to connect with the firewall on.

@AngelJA commented on GitHub (Dec 8, 2018): Did you test if it works if you disable the Windows firewall completely? I just set this up and had issues, but I found that the rule that Windows adds automatically is for barrier.exe instead of barriers.exe. Changing that allowed me to connect with the firewall on.

gitea-mirror commented

2026-05-05 05:27:17 -06:00

Author

Owner

@YoannBrillet commented on GitHub (Dec 8, 2018):

I just test it, modified firewall rules and the log say "process exited with error code: 9"
btw the linux server now denied a connection from the windows client to.
I'll see to uninstall and re install both client and server tomorrow. (maybe a sneaky update problem)

@YoannBrillet commented on GitHub (Dec 8, 2018): I just test it, modified firewall rules and the log say "process exited with error code: 9" btw the linux server now denied a connection from the windows client to. I'll see to uninstall and re install both client and server tomorrow. (maybe a sneaky update problem)

gitea-mirror commented

2026-05-05 05:27:22 -06:00

Author

Owner

@dayne commented on GitHub (Dec 9, 2018):

You might go through the debugging steps I just laid out in another similar issue open right now.

See this message for verifying Windows is seeing the server running on that port.

https://github.com/debauchee/barrier/issues/190#issuecomment-445582840

@dayne commented on GitHub (Dec 9, 2018): You might go through the debugging steps I just laid out in another similar issue open right now. See this message for verifying Windows is seeing the server running on that port. https://github.com/debauchee/barrier/issues/190#issuecomment-445582840

gitea-mirror commented

2026-05-05 05:27:24 -06:00

Author

Owner

@dario-pedro commented on GitHub (Dec 11, 2018):

I'm having the same problem. When I run my Linux machine as server, it detect my windows machine, but the mouse and keyboard is not being shared.

Any ideas?

@dario-pedro commented on GitHub (Dec 11, 2018): I'm having the same problem. When I run my Linux machine as server, it detect my windows machine, but the mouse and keyboard is not being shared. Any ideas?

gitea-mirror commented

2026-05-05 05:27:26 -06:00

Author

Owner

@silvanocerza commented on GitHub (Dec 12, 2018):

I had the same issue, I solved it by opening TCP port 24800 on Windows Firewall.

Open Windows Defender Firewall with Advanced Security, you can search from Start, then Inbound Rules > New Rule, then follow the steps.

@silvanocerza commented on GitHub (Dec 12, 2018): I had the same issue, I solved it by opening TCP port 24800 on Windows Firewall. Open Windows Defender Firewall with Advanced Security, you can search from Start, then Inbound Rules > New Rule, then follow the steps.

gitea-mirror commented

2026-05-05 05:27:28 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Dec 12, 2018):

Sorry for the super late response...I moved and only set my computer back up recently. We have a wiki page that details how to open up the port (at least on windows 10).

https://github.com/debauchee/barrier/wiki/Adding-Barrier-to-the-Windows-Firewall

@AdrianKoshka commented on GitHub (Dec 12, 2018): Sorry for the super late response...I moved and only set my computer back up recently. We have a wiki page that details how to open up the port (at least on windows 10). https://github.com/debauchee/barrier/wiki/Adding-Barrier-to-the-Windows-Firewall

gitea-mirror commented

2026-05-05 05:27:29 -06:00

Author

Owner

@abhagsain commented on GitHub (Mar 12, 2021):

I had the same issues. After an hour of searching Internet, I got it working.

Barrier was picking up the wrong IP Address which was my Ethernet IP Address. Thanks to Ians Answer

So make sure you run ipconfig on the server, in my case, it's Windows 10
and see the correct IP Address Under Wireless LAN adapter Wi-Fi IPV4 address.

Make sure you give the same Screen Name

In my case, the name is mac (Windows 10 Screenshot)

Mac OS Screenshot

I had problems if my Wifi is set to password-protected (which is just my mobile hotspot). So to get around that I made it public and limited the connections to it.

That's it. I hope it helps somebody :)

@abhagsain commented on GitHub (Mar 12, 2021): I had the same issues. After an hour of searching Internet, I got it working. 1. Barrier was picking up the wrong IP Address which was my Ethernet IP Address. Thanks to [Ians Answer][1] ![image](https://user-images.githubusercontent.com/36589645/110890719-93f8b000-8316-11eb-987d-b073582cc173.png) So make sure you run `ipconfig` on the server, in my case, it's **Windows 10** and see the correct IP Address Under **Wireless LAN adapter Wi-Fi** IPV4 address. ![image](https://user-images.githubusercontent.com/36589645/110890917-ecc84880-8316-11eb-9e02-50a7e35cac38.png) 2. Make sure you give the same **Screen Name** In my case, the name is **mac** (Windows 10 Screenshot) ![image](https://user-images.githubusercontent.com/36589645/110891136-652f0980-8317-11eb-897a-8eef8b51d562.png) Mac OS Screenshot ![image](https://user-images.githubusercontent.com/36589645/110891374-e1295180-8317-11eb-98dd-03c9520001e0.png) I had problems if my Wifi is set to password-protected (which is just my mobile hotspot). So to get around that I made it public and limited the connections to it. That's it. I hope it helps somebody :) [1]: https://stackoverflow.com/a/40995643/8885198

gitea-mirror commented

2026-05-05 05:27:31 -06:00

Author

Owner

@AbdulrahmanHashem commented on GitHub (Jun 7, 2024):

it's not impossible i solved it by installing bonjur you'll find it in the store under the name "avahi"
that fixed the problem for me.

@AbdulrahmanHashem commented on GitHub (Jun 7, 2024): it's not impossible i solved it by installing bonjur you'll find it in the store under the name "avahi" that fixed the problem for me.

gitea-mirror commented

2026-05-05 05:27:32 -06:00

Author

Owner

@mahian commented on GitHub (Jan 5, 2025):

I'm trying to connect barrier but the give the disconnected error in the barrier log after some time I uncheck the ssl but still not connecting 1

@mahian commented on GitHub (Jan 5, 2025): I'm trying to connect barrier but the give the disconnected error in the barrier log after some time I uncheck the ssl but still not connecting 1

gitea-mirror referenced this issue

2026-05-05 07:56:37 -06:00

[PR #158] [MERGED] OSX: Explain why the app needs to go into /Applications #1570