github-starred/barrier

Fork 0

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

[GH-ISSUE #691] Warning: Failed to connect to server: Timed Out, 24800 #547

New issue

Closed

opened 2026-05-05 06:39:37 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:39:37 -06:00

Owner

Originally created by @miketyj on GitHub (May 25, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/691

Server: Windows 10
Client: Windows 10

Server log
[2020-05-25T13:39:04] INFO: starting server
[2020-05-25T13:39:04] INFO: config file: C:/Users/Yong Jie/AppData/Local/Temp/Barrier.kYhEsV
[2020-05-25T13:39:04] INFO: log level: INFO
[2020-05-25T13:39:04] INFO: service command updated
[2020-05-25T13:39:04] INFO: service command updated
[2020-05-25T13:39:05] INFO: got ipc shutdown message
[2020-05-25T13:39:05] NOTE: stopped server
[2020-05-25T13:39:06] INFO: process 2292 was shutdown gracefully
[2020-05-25T13:39:06] INFO: starting new process as privileged user
[2020-05-25T13:39:06] INFO: drag and drop enabled
[2020-05-25T13:39:06] ERROR: failed to get desktop path, no drop target available, error=2
[2020-05-25T13:39:06] NOTE: started server (IPv4/IPv6), waiting for clients
[2020-05-25T13:39:06] INFO: server status: active

Client log

[2020-05-25T13:40:14] INFO: starting client
[2020-05-25T13:40:14] INFO: config file: C:/Users/VA Intern/AppData/Local/Temp/Barrier.HIKMBy
[2020-05-25T13:40:14] INFO: log level: INFO
[2020-05-25T13:40:14] INFO: service command updated
[2020-05-25T13:40:14] INFO: starting new process as privileged user
[2020-05-25T13:40:14] INFO: drag and drop enabled
[2020-05-25T13:40:14] ERROR: failed to get desktop path, no drop target available, error=2
[2020-05-25T13:40:14] NOTE: started client
[2020-05-25T13:40:14] NOTE: connecting to '192.168.56.1': 192.168.56.1:24800
[2020-05-25T13:40:14] INFO: OpenSSL 1.0.2l 25 May 2017
[2020-05-25T13:40:14] INFO: server status: active
[2020-05-25T13:40:29] WARNING: failed to connect to server: Timed out
[2020-05-25T13:40:30] NOTE: connecting to '192.168.56.1': 192.168.56.1:24800
[2020-05-25T13:40:30] INFO: OpenSSL 1.0.2l 25 May 2017

I tried to ping port 24800 on my server but it returned false.

Test-NetConnection -Port 24800 -ComputerName 192.168.56.1 -InformationLevel Detailed
ComputerName            : 192.168.56.1
RemoteAddress           : 192.168.56.1
RemotePort              : 24800
NameResolutionResults   : 192.168.56.1
MatchingIPsecRules      :
NetworkIsolationContext : Internet
IsAdmin                 : False
InterfaceAlias          : VirtualBox Host-Only Network
SourceAddress           : 192.168.56.1
NetRoute (NextHop)      : 0.0.0.0
TcpTestSucceeded        : True

How can I solve this issue?

Originally created by @miketyj on GitHub (May 25, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/691 Server: Windows 10 Client: Windows 10 **Server log** **[2020-05-25T13:39:04] INFO: starting server [2020-05-25T13:39:04] INFO: config file: C:/Users/Yong Jie/AppData/Local/Temp/Barrier.kYhEsV [2020-05-25T13:39:04] INFO: log level: INFO [2020-05-25T13:39:04] INFO: service command updated [2020-05-25T13:39:04] INFO: service command updated [2020-05-25T13:39:05] INFO: got ipc shutdown message [2020-05-25T13:39:05] NOTE: stopped server [2020-05-25T13:39:06] INFO: process 2292 was shutdown gracefully [2020-05-25T13:39:06] INFO: starting new process as privileged user [2020-05-25T13:39:06] INFO: drag and drop enabled [2020-05-25T13:39:06] ERROR: failed to get desktop path, no drop target available, error=2 [2020-05-25T13:39:06] NOTE: started server (IPv4/IPv6), waiting for clients [2020-05-25T13:39:06] INFO: server status: active** **Client log** **[2020-05-25T13:40:14] INFO: starting client [2020-05-25T13:40:14] INFO: config file: C:/Users/VA Intern/AppData/Local/Temp/Barrier.HIKMBy [2020-05-25T13:40:14] INFO: log level: INFO [2020-05-25T13:40:14] INFO: service command updated [2020-05-25T13:40:14] INFO: starting new process as privileged user [2020-05-25T13:40:14] INFO: drag and drop enabled [2020-05-25T13:40:14] ERROR: failed to get desktop path, no drop target available, error=2 [2020-05-25T13:40:14] NOTE: started client [2020-05-25T13:40:14] NOTE: connecting to '192.168.56.1': 192.168.56.1:24800 [2020-05-25T13:40:14] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-05-25T13:40:14] INFO: server status: active [2020-05-25T13:40:29] WARNING: failed to connect to server: Timed out [2020-05-25T13:40:30] NOTE: connecting to '192.168.56.1': 192.168.56.1:24800 [2020-05-25T13:40:30] INFO: OpenSSL 1.0.2l 25 May 2017** I tried to ping port 24800 on my server but it returned false. ``` Test-NetConnection -Port 24800 -ComputerName 192.168.56.1 -InformationLevel Detailed ComputerName : 192.168.56.1 RemoteAddress : 192.168.56.1 RemotePort : 24800 NameResolutionResults : 192.168.56.1 MatchingIPsecRules : NetworkIsolationContext : Internet IsAdmin : False InterfaceAlias : VirtualBox Host-Only Network SourceAddress : 192.168.56.1 NetRoute (NextHop) : 0.0.0.0 TcpTestSucceeded : True ``` How can I solve this issue?

gitea-mirror closed this issue

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

gitea-mirror commented

2026-05-05 06:39:43 -06:00

Author

Owner

@simons-public commented on GitHub (May 25, 2020):

Test-NetConnection -Port 24800 -ComputerName l92.168.56.1 -InformationLevel Detailed
WARNING: Name resolution of l92.168.56.1 failed

@miketyj Not sure if you noticed, but when you used Test-NetConnection you had a lowercase L instead of a 1, that's why you had a Name resolution failure for what should have been an IP.

Did you make sure to add barrier to the windows firewall?

@simons-public commented on GitHub (May 25, 2020): > Test-NetConnection -Port 24800 -ComputerName l92.168.56.1 -InformationLevel Detailed > WARNING: Name resolution of l92.168.56.1 failed @miketyj Not sure if you noticed, but when you used `Test-NetConnection` you had a lowercase L instead of a 1, that's why you had a `Name resolution` failure for what should have been an IP. Did you make sure to [add barrier to the windows firewall?](https://github.com/debauchee/barrier/wiki/Adding-Barrier-to-the-Windows-Firewall)

gitea-mirror commented

2026-05-05 06:39:47 -06:00

Author

Owner

@miketyj commented on GitHub (May 26, 2020):

@simons-public Thanks for pointing that out. I made a mistake by putting L instead of 1 as you mentioned. I have updated the post above.

Yes. I have added barrier as demonstrated in the link that you sent. The problem still persists.

@miketyj commented on GitHub (May 26, 2020): @simons-public Thanks for pointing that out. I made a mistake by putting L instead of 1 as you mentioned. I have updated the post above. Yes. I have added barrier as demonstrated in the link that you sent. The problem still persists.

gitea-mirror commented

2026-05-05 06:39:50 -06:00

Author

Owner

@miketyj commented on GitHub (May 26, 2020):

Hi guys,
I've managed to solve the issue. I had a VPN installed so Barrier was showing the IP address of the VPN. Go to cmd and type ipconfig

Wireless LAN adapter Wi-Fi:
IPv4 Address. . . . . . . . . . . : 192.168.1.xxx <---- should select this instead

Secondly, you should create a new rule on both machine's firewall.

Go to Window Defenders Firewall -> Advanced Setting ->Highlight Inbound rule -> Go to 'Actions', click on create new rule
Click Program
Add 'C:\Program Files\Barrier\Barrier.exe' to the path and click next [path may be different, depends on where you install it on your machine]
Allow the connection
Check all the boxes under Profile
Add a name to your rule, i called it barrier and click ok.

Do this for both machines. Once this is completed, run barrier as administrator on both machines.

It should work now

@miketyj commented on GitHub (May 26, 2020): Hi guys, I've managed to solve the issue. I had a VPN installed so Barrier was showing the IP address of the VPN. Go to cmd and type ipconfig **Wireless LAN adapter Wi-Fi: IPv4 Address. . . . . . . . . . . : 192.168.1.xxx <---- should select this instead** Secondly, you should create a new rule on both machine's firewall. 1. Go to Window Defenders Firewall -> Advanced Setting ->Highlight Inbound rule -> Go to 'Actions', click on create new rule 2. Click Program 3. Add 'C:\Program Files\Barrier\Barrier.exe' to the path and click next [path may be different, depends on where you install it on your machine] 4. Allow the connection 5. Check all the boxes under Profile 6. Add a name to your rule, i called it barrier and click ok. Do this for both machines. Once this is completed, run barrier as administrator on both machines. It should work now

No labels

Rows
Columns