[GH-ISSUE #1104] Mac OS detects the windows server, then infinite timeout loop. #883

Open
opened 2026-05-05 07:14:37 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @DwertlePlayz on GitHub (Mar 16, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1104

Describe the bug
When using a windows server and a macOS client, there is an infinite timeout loop. I think barrier is trying to use my ethernet for the server ip instead of the wifi's ip. I don't have a cable plugged into the ethernet, but barrier is still trying to use it.

Desktop (please complete the following information):

  • OS: Windows (server)
  • OS: MacOS (client)
  • Barrier version: 2.3.3

Additional context
When running ipconfig my ethernet's ip is 192.168.56.1 while my wireless is 192.168.0.104.
Barrier is using the ethernet's for some reason.

Originally created by @DwertlePlayz on GitHub (Mar 16, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1104 **Describe the bug** When using a windows server and a macOS client, there is an infinite timeout loop. I think barrier is trying to use my ethernet for the server ip instead of the wifi's ip. I don't have a cable plugged into the ethernet, but barrier is still trying to use it. **Desktop (please complete the following information):** - OS: Windows (server) - OS: MacOS (client) - Barrier version: 2.3.3 **Additional context** When running ipconfig my ethernet's ip is 192.168.56.1 while my wireless is 192.168.0.104. Barrier is using the ethernet's for some reason.
Author
Owner

@DwertlePlayz commented on GitHub (Mar 16, 2021):

And on both machines barrier is allowed through the firewall.

<!-- gh-comment-id:800384931 --> @DwertlePlayz commented on GitHub (Mar 16, 2021): And on both machines barrier is allowed through the firewall.
Author
Owner

@ggcol commented on GitHub (Apr 9, 2021):

Don't know if this can be usefull but happens also using MacOS11 as server and Win10 as Client
(Barrier version: 2.3.3)

<!-- gh-comment-id:816680641 --> @ggcol commented on GitHub (Apr 9, 2021): Don't know if this can be usefull but happens also using MacOS11 as server and Win10 as Client (Barrier version: 2.3.3)
Author
Owner

@aakashthakare commented on GitHub (Feb 13, 2024):

This happened to me when upgraded the mac OS.

Uninstallinng the barrier and reinstalling it fixed the issue.

Hope this helps. :)

<!-- gh-comment-id:1940387102 --> @aakashthakare commented on GitHub (Feb 13, 2024): This happened to me when upgraded the mac OS. Uninstallinng the barrier and reinstalling it fixed the issue. Hope this helps. :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#883
No description provided.