[GH-ISSUE #737] Working as server but not working as client #578

Closed
opened 2026-05-05 06:42:47 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @mcnaveen on GitHub (Jun 4, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/737

Operating Systems

Server: Ubuntu 20.04

Client: Windows 7

Barrier Version

2.3.2

Steps to reproduce bug

Started the Server. Checked logs...

[2020-06-04T22:50:17] INFO: starting server
[2020-06-04T22:50:17] INFO: config file: /tmp/Barrier.f35726
[2020-06-04T22:50:17] INFO: log level: INFO
[2020-06-04T22:50:17] NOTE: started server (IPv4/IPv6), waiting for clients

In the Client Log...

[2020-06-04T23:06:10] NOTE: connecting to '192.168.31.201 , 192.168. 31.201:24800
2020-06-04T23:06:101 INFO : Openssl 1.0.21 25 May 2017
[2020-06-04T23:06:25] WARNING: failed to connect to server: Timed out

Other info

I tried to swap the client as a server and server as a client.
It works this way.

But, Previously I used like this.

While Upgrading from Ubuntu 18.04 to 20.04 I did the fresh installation. After that, this problem occurs.

Originally created by @mcnaveen on GitHub (Jun 4, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/737 ### Operating Systems ### Server: Ubuntu 20.04 Client: Windows 7 ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### Started the Server. Checked logs... ``` [2020-06-04T22:50:17] INFO: starting server [2020-06-04T22:50:17] INFO: config file: /tmp/Barrier.f35726 [2020-06-04T22:50:17] INFO: log level: INFO [2020-06-04T22:50:17] NOTE: started server (IPv4/IPv6), waiting for clients ``` In the Client Log... ``` [2020-06-04T23:06:10] NOTE: connecting to '192.168.31.201 , 192.168. 31.201:24800 2020-06-04T23:06:101 INFO : Openssl 1.0.21 25 May 2017 [2020-06-04T23:06:25] WARNING: failed to connect to server: Timed out ``` ### Other info ### I tried to swap the client as a server and server as a client. It works this way. But, Previously I used like this. While Upgrading from Ubuntu 18.04 to 20.04 I did the fresh installation. After that, this problem occurs.
Author
Owner

@mcnaveen commented on GitHub (Jun 4, 2020):

Running this command on Ubuntu (Barrier Server) Solved the issue.

sudo iptables -I INPUT -p tcp --dport 24800 --syn -j ACCEPT

Basically What it does is opening the TCP Port 24800 for the Barrier server.

<!-- gh-comment-id:639005286 --> @mcnaveen commented on GitHub (Jun 4, 2020): Running this command on Ubuntu (Barrier Server) Solved the issue. `sudo iptables -I INPUT -p tcp --dport 24800 --syn -j ACCEPT` Basically What it does is opening the TCP Port 24800 for the Barrier server.
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#578
No description provided.