mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1104] Mac OS detects the windows server, then infinite timeout loop. #883
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#883
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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):
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.
@DwertlePlayz commented on GitHub (Mar 16, 2021):
And on both machines barrier is allowed through the firewall.
@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)
@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. :)