github-starred/barrier
2
0
Fork 0
mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00
Code Issues 1.0k Projects Packages Wiki Activity Actions

[GH-ISSUE #1480] Server connection timeout but the client can ping the server #1128

New issue
Closed
opened 2026-05-05 07:30:59 -06:00 by gitea-mirror · 3 comments
gitea-mirror commented 2026-05-05 07:30:59 -06:00
Owner
Copy link

Originally created by @llinfeng on GitHub (Dec 15, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1480

What happened?

Both the server and two clients are running Barrier 2.4.0, and all are Windows machines. The server and the dysfunctional client are both Win 10, and another functioning client runs Win 11. All machines are hooked up to the same router.

It bugged me that whatever I try, the client that runs Win 10 fails to connect to the server. I have tried:

  1. Keep all versions of Barrier the same --- I have tried Barrier 2.3.3, 2.3.4 and 2.4.0 for the server and the Win 10 client.
  2. Disabled SSL in Settings/Network
  3. Verify that the client can ping the server, via the server's local address (in my case, it is 192.168.0.66.)
  4. Open the IP-v4 port for both inbound/outbound on both the server and the buggy client.

It is a bit concerning that upon reinstalling Barrier on the problematic client, even when there is nothing left in c:\ProgramData\Barrier\, c:\Program Files\Barrier\ and ~/AppData/Local/Barrier, a newly installed Barrier program should know my previous setting for debug-logs. This hints to me that something is left on the buggy client that keeps causing the timeout events in the log.

Please advise how to get the Win 10 client connected to the server. (I have used the same machine previously. Recently, I installed a fresh Win 10 OS on it. This may rule out possible hardware issues.)

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

All barrier instances are installed using BarrierSetup-2.4.0-release.exe, from the release page.

What OSes are you seeing the problem on? (Check all that apply)

Windows

What OS versions are you using?

Server runs Win 10, one functioning machine runs Win 11. Another client runs Win 10, and I cannot get it to connect to the server.

Relevant log output

[2021-12-14T19:52:43] INFO: connecting to service...

[2021-12-14T19:52:44] INFO: starting client
[2021-12-14T19:52:44] INFO: config file: C:/Users/llinfeng/AppData/Local/Temp/Barrier.cYeaQu
[2021-12-14T19:52:44] INFO: log level: INFO
[2021-12-14T19:52:44] INFO: log file: C:/Program Files/Barrier/log/barrier.log
[2021-12-14T19:52:44] INFO: connection established
[2021-12-14T19:52:31] INFO: using last known command: "C:/Program Files/Barrier/barrierc.exe" -f --no-tray --debug INFO --name Surface7 --ipc --enable-drag-drop --disable-crypto --profile-dir C:\Users\llinfeng\AppData\Local\Barrier [196.168.0.66]:24800
[2021-12-14T19:52:31] INFO: service command updated
[2021-12-14T19:52:31] INFO: starting new process as privileged user
server status: active
[2021-12-14T19:52:32] INFO: drag and drop enabled
[2021-12-14T19:52:32] NOTE: started client
[2021-12-14T19:52:32] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:52:32] WARNING: failed to connect to server: The network can't be reached from this host at this time
[2021-12-14T19:52:33] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:52:33] WARNING: failed to connect to server: The network can't be reached from this host at this time
[2021-12-14T19:52:34] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:52:34] WARNING: failed to connect to server: The network can't be reached from this host at this time
[2021-12-14T19:52:35] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:52:35] WARNING: failed to connect to server: No route to host
[2021-12-14T19:52:36] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:52:44] INFO: service command updated
server status: active
[2021-12-14T19:52:44] INFO: got ipc shutdown message
[2021-12-14T19:52:44] NOTE: stopped client
[2021-12-14T19:52:46] INFO: process 4248 was shutdown gracefully
[2021-12-14T19:52:46] INFO: starting new process as privileged user
[2021-12-14T19:52:46] INFO: drag and drop enabled
[2021-12-14T19:52:46] NOTE: started client
[2021-12-14T19:52:46] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
server status: active
[2021-12-14T19:53:01] WARNING: failed to connect to server: Timed out
[2021-12-14T19:53:02] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:53:17] WARNING: failed to connect to server: Timed out
[2021-12-14T19:53:18] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:53:33] WARNING: failed to connect to server: Timed out
[2021-12-14T19:53:34] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:53:49] WARNING: failed to connect to server: Timed out
[2021-12-14T19:53:50] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:54:05] WARNING: failed to connect to server: Timed out
[2021-12-14T19:54:06] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800
[2021-12-14T19:54:21] WARNING: failed to connect to server: Timed out



### Any other information

_No response_
Originally created by @llinfeng on GitHub (Dec 15, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1480 ### What happened? Both the server and two clients are running Barrier 2.4.0, and all are Windows machines. The server and the dysfunctional client are both Win 10, and another functioning client runs Win 11. All machines are hooked up to the same router. It bugged me that whatever I try, the client that runs Win 10 fails to connect to the server. I have tried: 1. Keep all versions of Barrier the same --- I have tried Barrier 2.3.3, 2.3.4 and 2.4.0 for the server and the Win 10 client. 2. Disabled SSL in Settings/Network 3. Verify that the client can ping the server, via the server's local address (in my case, it is `192.168.0.66`.) 4. Open the IP-v4 port for both inbound/outbound on both the server and the buggy client. It is a bit concerning that upon reinstalling Barrier on the problematic client, even when there is nothing left in `c:\ProgramData\Barrier\`, `c:\Program Files\Barrier\` and `~/AppData/Local/Barrier`, a newly installed Barrier program should know my previous setting for debug-logs. This hints to me that something is left on the buggy client that keeps causing the timeout events in the log. Please advise how to get the Win 10 client connected to the server. (I have used the same machine previously. Recently, I installed a fresh Win 10 OS on it. This may rule out possible hardware issues.) ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? All barrier instances are installed using `BarrierSetup-2.4.0-release.exe`, from the release page. ### What OSes are you seeing the problem on? (Check all that apply) Windows ### What OS versions are you using? Server runs Win 10, one functioning machine runs Win 11. Another client runs Win 10, and I cannot get it to connect to the server. ### Relevant log output ```shell [2021-12-14T19:52:43] INFO: connecting to service... [2021-12-14T19:52:44] INFO: starting client [2021-12-14T19:52:44] INFO: config file: C:/Users/llinfeng/AppData/Local/Temp/Barrier.cYeaQu [2021-12-14T19:52:44] INFO: log level: INFO [2021-12-14T19:52:44] INFO: log file: C:/Program Files/Barrier/log/barrier.log [2021-12-14T19:52:44] INFO: connection established [2021-12-14T19:52:31] INFO: using last known command: "C:/Program Files/Barrier/barrierc.exe" -f --no-tray --debug INFO --name Surface7 --ipc --enable-drag-drop --disable-crypto --profile-dir C:\Users\llinfeng\AppData\Local\Barrier [196.168.0.66]:24800 [2021-12-14T19:52:31] INFO: service command updated [2021-12-14T19:52:31] INFO: starting new process as privileged user server status: active [2021-12-14T19:52:32] INFO: drag and drop enabled [2021-12-14T19:52:32] NOTE: started client [2021-12-14T19:52:32] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:52:32] WARNING: failed to connect to server: The network can't be reached from this host at this time [2021-12-14T19:52:33] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:52:33] WARNING: failed to connect to server: The network can't be reached from this host at this time [2021-12-14T19:52:34] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:52:34] WARNING: failed to connect to server: The network can't be reached from this host at this time [2021-12-14T19:52:35] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:52:35] WARNING: failed to connect to server: No route to host [2021-12-14T19:52:36] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:52:44] INFO: service command updated server status: active [2021-12-14T19:52:44] INFO: got ipc shutdown message [2021-12-14T19:52:44] NOTE: stopped client [2021-12-14T19:52:46] INFO: process 4248 was shutdown gracefully [2021-12-14T19:52:46] INFO: starting new process as privileged user [2021-12-14T19:52:46] INFO: drag and drop enabled [2021-12-14T19:52:46] NOTE: started client [2021-12-14T19:52:46] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 server status: active [2021-12-14T19:53:01] WARNING: failed to connect to server: Timed out [2021-12-14T19:53:02] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:53:17] WARNING: failed to connect to server: Timed out [2021-12-14T19:53:18] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:53:33] WARNING: failed to connect to server: Timed out [2021-12-14T19:53:34] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:53:49] WARNING: failed to connect to server: Timed out [2021-12-14T19:53:50] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:54:05] WARNING: failed to connect to server: Timed out [2021-12-14T19:54:06] NOTE: connecting to '196.168.0.66': 196.168.0.66:24800 [2021-12-14T19:54:21] WARNING: failed to connect to server: Timed out ``` ``` ### Any other information _No response_
gitea-mirror commented 2026-05-05 07:31:03 -06:00
Author
Owner
Copy link

@llinfeng commented on GitHub (Dec 15, 2021):

With one Win 10 client that connects and the other Win 10 client failing to connect, on both clients, I did the TCP test suggested in this post and get identical results. My server is running at xxx.xxx.x.66.

PS C:\Users\llinfeng> Test-NetConnection -Port 24800 -ComputerName xxx.xxx.x.66 -InformationLevel Detailed


ComputerName            : xxx.xxx.x.66
RemoteAddress           : xxx.xxx.x.66
RemotePort              : 24800
NameResolutionResults   : xxx.xxx.x.66
                          AW
MatchingIPsecRules      :
NetworkIsolationContext : Internet
IsAdmin                 : False
InterfaceAlias          : Wi-Fi
SourceAddress           : xxx.xxx.x.203
NetRoute (NextHop)      : 0.0.0.0
TcpTestSucceeded        : True
<!-- gh-comment-id:994802890 --> @llinfeng commented on GitHub (Dec 15, 2021): With one Win 10 client that connects and the other Win 10 client failing to connect, on both clients, I did the TCP test suggested in [this post](https://github.com/debauchee/barrier/issues/190#issuecomment-445582840) and get identical results. My server is running at `xxx.xxx.x.66`. ``` PS C:\Users\llinfeng> Test-NetConnection -Port 24800 -ComputerName xxx.xxx.x.66 -InformationLevel Detailed ComputerName : xxx.xxx.x.66 RemoteAddress : xxx.xxx.x.66 RemotePort : 24800 NameResolutionResults : xxx.xxx.x.66 AW MatchingIPsecRules : NetworkIsolationContext : Internet IsAdmin : False InterfaceAlias : Wi-Fi SourceAddress : xxx.xxx.x.203 NetRoute (NextHop) : 0.0.0.0 TcpTestSucceeded : True ```
gitea-mirror commented 2026-05-05 07:31:04 -06:00
Author
Owner
Copy link

@llinfeng commented on GitHub (Dec 15, 2021):

My way out of this awkward issue is to roll back to Synergy. I happened to find an old V1 license of mine for Synergy. Now, my software KVM setup is working again. Though, I had to remove screenSaverSync = true from the server configuration file as Synergy V1 does not like it.

The fix in my case involves two simple steps. It surprised me a bit as I did not even need to reboot the server machine.

  1. Uninstall Barrier 2.4.0 on all machines, and
  2. Install synergy_1.14.2-stable.c6918b74_windows_x64.msi from Synergy on all machines.

Then, it took a while to find the proper setting that asks Synergy to source my original configuration file. In case others need it, here is a point-and-click guide:
image

Reflection

I suspect something is left on the server machine after the numerous Barrier uninstallations. This particular thing blocks a specific client from connecting to the server. As documented previously, a Win 11 client connects to the server just fine. And, the TCP test passed on both clients. Now, since Synergy has no problem getting both clients to work with the server, I suppose some leftover setting from Barrier was blocking the connection previously.

<!-- gh-comment-id:994937078 --> @llinfeng commented on GitHub (Dec 15, 2021): My way out of this awkward issue is to roll back to Synergy. I happened to find an old V1 license of mine for Synergy. Now, my software KVM setup is working again. Though, I had to remove ` screenSaverSync = true` from the server configuration file as Synergy V1 does not like it. ---- The fix in my case involves two simple steps. It surprised me a bit as I did not even need to reboot the server machine. 1. Uninstall Barrier 2.4.0 on all machines, and 2. Install `synergy_1.14.2-stable.c6918b74_windows_x64.msi` from Synergy on all machines. Then, it took a while to find the proper setting that asks Synergy to source my original configuration file. In case others need it, here is a point-and-click guide: ![image](https://user-images.githubusercontent.com/5890407/146221288-825fa9f4-7a7c-4ed9-ac89-f5dbbba2502d.png) ---- #### Reflection I suspect something is left on the server machine after the numerous Barrier uninstallations. This particular thing blocks a specific client from connecting to the server. As documented previously, a Win 11 client connects to the server just fine. And, the TCP test passed on both clients. Now, since Synergy has no problem getting both clients to work with the server, I suppose some leftover setting from Barrier was blocking the connection previously.
gitea-mirror commented 2026-05-05 07:31:05 -06:00
Author
Owner
Copy link

@andrew222651 commented on GitHub (Jan 17, 2023):

I had the same issue and it worked after I rebooted the server

<!-- gh-comment-id:1385619999 --> @andrew222651 commented on GitHub (Jan 17, 2023): I had the same issue and it worked after I rebooted the server
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
enhancement/builds/windows-multi-versions-build
martin-furter-barrier-term
enhancement/builds/macos-universal
enhancement/builds/macos-universal-qt6-test
2.3.x
fix/lang-translation/ssl-slash-tls
feature/build/compile/32-bit
feature/build/compile/armv7
testing-framework
README-update
remotes/fork/README-update
remotes/fork/smartzeroconf
smartzeroconf
pages-devel
remotes/fork/pages-devel
pkgconfig
remotes/fork/pkgconfig
release
remotes/fork/release
v2.4.0
v2.3.4
v2.3.3
1.11.0-stable
v1.11.0-rc2
v2.3.2
v1.10.3-stable
v2.3.2-alpha
v2.3.1
v2.3.0
v1.10.2-stable
v1.10.2-rc1
v1.10.2-rc2
v2.1.2
v2.0.8-beta
v2.0.7-beta
v2.0.4-beta
v2.0.3-beta
v2.1.1
v2.1.0
v1.9.1-stable
v2.0.0
v1.9.0-stable
v2.0.0-RC2
v2.0.0-RC1
v2.0.0-stable
v1.8.8-stable
v1.8.7-stable
v1.8.6-stable
v1.8.5-stable
v1.8.4-stable
v1.8.3-stable
v1.8.1-stable
v1.8.0-beta
v1.7.3-stable
v1.7.2-stable
v1.7.1-stable
1.7.0
1.6.3-final
1.6.2
1.6.1
1.6.0
Labels
Clear 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

Mirrored from GitHub Pull Request

  
query

   
question

   
regression

   
regression

   
v2.4.0

   
windows

   
wontfix

   
work-in-progress
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1128
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?