[GH-ISSUE #909] Windows 7 and Ubuntu 20.04 no longer working after windows sleep #725

New issue

Closed

opened 2026-05-05 06:59:46 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:59:46 -06:00

Owner

Originally created by @dookei on GitHub (Oct 12, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/909

Hi there,
My barrier worked for a day! :-)
Both machines are on the same local network and both can ping each other.
I disabled already all the firewalls to see if the issue was related to the firewall. No luck neither.
The weird thing is that this worked already before. The only thing I have done was to put the windows machine to sleep for the night. In the next morning no longer connects to the server.
I also tried to set the server on the windows machine. Reinstall Barrier on both machines ...etc... nothing seams to work no more.
My Barrier version on both machines is 2.3.2.
Any idea what might be?

Greetings

Originally created by @dookei on GitHub (Oct 12, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/909 Hi there, My barrier worked for a day! :-) Both machines are on the same local network and both can ping each other. I disabled already all the firewalls to see if the issue was related to the firewall. No luck neither. The weird thing is that this worked already before. The only thing I have done was to put the windows machine to sleep for the night. In the next morning no longer connects to the server. I also tried to set the server on the windows machine. Reinstall Barrier on both machines ...etc... nothing seams to work no more. My Barrier version on both machines is 2.3.2. Any idea what might be? Greetings

gitea-mirror closed this issue

2026-05-05 06:59:48 -06:00

gitea-mirror commented

2026-05-05 06:59:51 -06:00

Author

Owner

@mcnaveen commented on GitHub (Oct 12, 2020):

Can you post the log? I too faced the same kinda issue. #737

@mcnaveen commented on GitHub (Oct 12, 2020): Can you post the log? I too faced the same kinda issue. #737

gitea-mirror commented

2026-05-05 06:59:54 -06:00

Author

Owner

@dookei commented on GitHub (Oct 13, 2020):

Hi @mcnaveen ,
thanks for your reply. The solution that you proposed also worked for me ?
sudo iptables -I INPUT -p tcp --dport 24800 --syn -j ACCEPT
I believe that when I activated the vpn kill switch it closed some ports for me. I now added this command to the startup script with barrier. Many thanks !

@dookei commented on GitHub (Oct 13, 2020): Hi @mcnaveen , thanks for your reply. The solution that you proposed also worked for me ? **sudo iptables -I INPUT -p tcp --dport 24800 --syn -j ACCEPT** I believe that when I activated the vpn kill switch it closed some ports for me. I now added this command to the startup script with barrier. Many thanks !

gitea-mirror commented

2026-05-05 06:59:55 -06:00

Author

Owner

@mcnaveen commented on GitHub (Oct 13, 2020):

You're Welcome 🙂

@mcnaveen commented on GitHub (Oct 13, 2020): You're Welcome 🙂

gitea-mirror referenced this issue

2026-05-05 07:59:34 -06:00

[PR #725] [MERGED] Make connection message a NOTE for consistency #1689

gitea-mirror referenced this issue

2026-05-05 07:59:41 -06:00