mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1281] Cannot establish connection between server and client #1026
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#1026
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 @AntonBock on GitHub (Sep 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1281
What happened?
Barrier worked perfectly for me until we switched IT systems at work, and I no longer have administrator rights. I am therefore assuming that this is the issue, however I am hoping that someone has a fix or workaround.
I am connecting a Windows machine with a machine running Ubuntu 18.04.
I am manually inserting the server IP, and have tried to connect both with and without SSL enabled.
The server is not configured in any way, except for placing the two computers on the interactive grid. Again, this worked fine before the IT change.
Version
v2.3.3
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
The Ubuntu version was installed with snap, using the command
sudo snap install barrierThe Windows version was installed with the 2.3.3.exe release
What OSes are you seeing the problem on? (Check all that apply)
Linux, Windows
What OS versions are you using?
Windows 10, Ubuntu 18.04
Relevant log output
Any other information
No response
@PedanXr commented on GitHub (Sep 10, 2021):
Can you please run CMD.exe on your server and do a ping and a traceroute to your client? (tracert ip-of-client)
And also do the same but the other way around from your client? (traceroute ip-of-server) and post results?
I would like to test if both clients can even reach each other.
@AntonBock commented on GitHub (Sep 14, 2021):
Hello,
Apologies - I was simply an idiot, who didn't notice that during the IT change, the network was also changed for one computer, but not the other. Switching to the same network fixed it for me facepalm