github-starred/barrier

Fork 0

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

[GH-ISSUE #160] Put barriers.exe in firewall whitelist as name "Barrier Server" and change barrier.exe firewall whitelist name as "Barrier" #129

New issue

Closed

opened 2026-05-05 05:20:28 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 05:20:28 -06:00

Owner

Originally created by @coughingmouse on GitHub (Oct 20, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/160

Operating Systems

Server: Windows 10 (Microsoft Windows Version 1803 (OS Build 17134.345))

Client: macOS (macOS High Sierra version 10.13.6 (17G65))

Barrier Version

2.1.0-RELEASE
(You know, the one you can download pre-compiled.)

Steps to reproduce bug

Mac and Windows on same network.
Download and install 2.1.0 precompiled .exe for windows, and the like for the mac.
Go to Configure Server... on Windows barrier and configure client name or IP whatever.
Run server on windows.
Get Server IP and put it in the mac client, after checking the client checkbox on mac.
Run client on mac.
Nothing happens, especially on the sever side. They should've been connected by now.
From the client side, it repeatedly says that the server is rejecting.

Other info

Workaround: Yes
Does it prevent me from using barrier completely: It prevents using Windows as Server; yeah in that #case.

Be aware: Maybe this is already patched. IDK. But for a totally techno-phobic person like me who can't compile anything but a simple .c file, .exe file download's the only option.

I figured barrier for Windows 10 does not set privillage for barriers.exe but only for barrier.exe.

That is, I was trying to connect my MacBook Air to a Windows PC locally.
I could set my Mac as server and Windows as client quite automatically.
But I couldn't connect while setting Windows as server, even after tweaking with "Configure Server..."
Looking at the logs on both sides, it was apparent that Mac couldn't even reach, probably due to firewall settings on the Windows side. After registering barriers.exe to the firewall whitelist, voila! It works like a charm.
For what I see, barrier.exe is registered on the firewall whitelist as "barrier" which is already a bad name on which I would like to encourage changing the name to "Barrier" or "Barrier Client". But barriers.exe doesn't get added to the firewall. So, please make to do so, in name "Barrier Server" to be fair.

Originally created by @coughingmouse on GitHub (Oct 20, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/160 ### Operating Systems ### Server: Windows 10 (Microsoft Windows Version 1803 (OS Build 17134.345)) Client: macOS (macOS High Sierra version 10.13.6 (17G65)) ### Barrier Version ### 2.1.0-RELEASE (You know, the one you can download pre-compiled.) ### Steps to reproduce bug ### 0. Mac and Windows on same network. 1. Download and install 2.1.0 precompiled .exe for windows, and the like for the mac. 2. Go to Configure Server... on Windows barrier and configure client name or IP whatever. 3. Run server on windows. 4. Get Server IP and put it in the mac client, after checking the client checkbox on mac. 5. Run client on mac. 6. Nothing happens, especially on the sever side. They should've been connected by now. 7. From the client side, it repeatedly says that the server is rejecting. ### Other info ### Workaround: Yes Does it prevent me from using barrier completely: It prevents using Windows as Server; yeah in that #case. Be aware: Maybe this is already patched. IDK. But for a totally techno-phobic person like me who can't compile anything but a simple .c file, .exe file download's the only option. I figured barrier for Windows 10 does not set privillage for barriers.exe but only for barrier.exe. That is, I was trying to connect my MacBook Air to a Windows PC locally. I could set my Mac as server and Windows as client quite automatically. But I couldn't connect while setting Windows as server, even after tweaking with "Configure Server..." Looking at the logs on both sides, it was apparent that Mac couldn't even reach, probably due to firewall settings on the Windows side. After registering barriers.exe to the firewall whitelist, voila! It works like a charm. For what I see, barrier.exe is registered on the firewall whitelist as "barrier" which is already a bad name on which I would like to encourage changing the name to "Barrier" or "Barrier Client". But barriers.exe doesn't get added to the firewall. So, please make to do so, in name "Barrier Server" to be fair.

gitea-mirror closed this issue

2026-05-05 05:20:29 -06:00

gitea-mirror commented

2026-05-05 05:20:32 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Oct 20, 2018):

I think this will be fixed with barrier 2.2

@AdrianKoshka commented on GitHub (Oct 20, 2018): I think this will be fixed with barrier 2.2

gitea-mirror commented

2026-05-05 05:20:34 -06:00

Author

Owner

@jdnewman85 commented on GitHub (Feb 10, 2019):

Hey, how about you make a note for this KNOWN ISSUE. I opened the firewall for barrier.exe, then gave up and tried an earlier version (2.0.0). This version prompted as it should have for 'barriers.exe'. After, I reinstalled the latest version.

Seriously, stick a note above the download or something.

@jdnewman85 commented on GitHub (Feb 10, 2019): Hey, how about you make a note for this _KNOWN ISSUE_. I opened the firewall for barrier.exe, then gave up and tried an earlier version (2.0.0). This version prompted as it should have for 'barriers.exe'. After, I reinstalled the latest version. Seriously, stick a note above the download or something.

gitea-mirror commented

2026-05-05 05:20:36 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Feb 10, 2019):

Sorry, been busy with work and other things, slipped my mind.

@AdrianKoshka commented on GitHub (Feb 10, 2019): Sorry, been busy with work and other things, slipped my mind.

gitea-mirror commented

2026-05-05 05:20:37 -06:00

Author

Owner

@jdnewman85 commented on GitHub (Feb 11, 2019):

No worries, was just a bit irritated at trying to get it to work :p

@jdnewman85 commented on GitHub (Feb 11, 2019): No worries, was just a bit irritated at trying to get it to work :p

gitea-mirror commented

2026-05-05 05:20:39 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Feb 11, 2019):

I hope this is good enough.

@AdrianKoshka commented on GitHub (Feb 11, 2019): I hope this is good enough. ![screenshot_2019-02-10 debauchee barrier](https://user-images.githubusercontent.com/8690255/52542555-fc0eed80-2d6e-11e9-8ec8-2cf2ff2a9936.png)

gitea-mirror commented

2026-05-05 05:20:42 -06:00

Author

Owner

@mrmohitj commented on GitHub (Aug 1, 2021):

Hi I am using barries 2.3.3 and unable to connect to server running in windows 10 from client in raspberry . I have tried with screen name and server Ip on the client side .
My suspicion is in the windows firewall but I can see the rule in firewall.
I don't see anything in server logs and can see on wireshark on server side that message from client is coming but nothing going back.

Enclosing screen shots.

Can someone help ?

Thanks,
mohit

@mrmohitj commented on GitHub (Aug 1, 2021): Hi I am using barries 2.3.3 and unable to connect to server running in windows 10 from client in raspberry . I have tried with screen name and server Ip on the client side . My suspicion is in the windows firewall but I can see the rule in firewall. I don't see anything in server logs and can see on wireshark on server side that message from client is coming but nothing going back. Enclosing screen shots. Can someone help ? Thanks, mohit ![barrier_2](https://user-images.githubusercontent.com/57355906/127776778-c13d348c-5c3b-457e-aacc-7b9555b74903.jpg) ![barrier_1](https://user-images.githubusercontent.com/57355906/127776779-10354fa4-233c-4994-ad9d-b938ff1ef1fc.jpg)

No labels

Rows
Columns