[GH-ISSUE #144] Unrecognized client when using configuration file generated by Barrier #115

New issue

Open

opened 2026-05-05 05:18:14 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 05:18:14 -06:00

Owner

Originally created by @NickAcPT on GitHub (Oct 6, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/144

Operating Systems

Server: Windows 8.1 (Build: 9600)

Client: Windows 10 (Version 1803 OS Build 17134.286)

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

Add client screen to "interactive configuration" on the server.
Click Barrier -> Save Configuration
Tell Barrier to use existing configuration
On the client, try to connect.
Watch the log saying it doesn't recognize the client.

Other info

When did the problem start to occur? When I saved the configuration generated by Barrier and told it to use that file.
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? No, but it makes it impossible to specify percentages for screen alignment.

Originally created by @NickAcPT on GitHub (Oct 6, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/144 ### Operating Systems ### Server: Windows 8.1 (Build: 9600) Client: Windows 10 (Version 1803 OS Build 17134.286) ### Barrier Version ### 2.1.0-RELEASE-0b2dfd80 ### Steps to reproduce bug ### 1. Add client screen to "interactive configuration" on the server. 2. Click Barrier -> Save Configuration 3. Tell Barrier to use existing configuration 4. On the client, try to connect. 5. Watch the log saying it doesn't recognize the client. ### Other info ### * When did the problem start to occur? When I saved the configuration generated by Barrier and told it to use that file. * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? No, but it makes it impossible to specify percentages for screen alignment.

gitea-mirror added the

windows

label

2026-05-05 05:18:14 -06:00