Barrier is starting loop. Windows (Host) Mac (Client)

[ShernNing]

What happened?

I am running barrier 2.4.0 on both windows 11 and macos Sonoma. SSL is turned off.

When i use mac as host and windows as client, it connects just fine, but when i use windows as Host and mac and Client, the mac just gets stuck in Barrier is starting forever. On the windows (host) side, it goes to barrier is running with no issues.

How do i get 'Barrier is running' on mac (client).

Here are the logs:
[2024-06-17T12:18:11] INFO: stopping barrier desktop process
[2024-06-17T12:18:16] ERROR: process exited with error code: 9

[2024-06-17T12:18:16] INFO: starting client
[2024-06-17T12:18:16] INFO: config file: /private/var/folders/np/d9kp375j437gmbqxw0jlr87c0000gn/T/Barrier.WIOBiO
[2024-06-17T12:18:16] INFO: log level: INFO
[2024-06-17T12:18:16] INFO: drag and drop enabled
[2024-06-17T12:18:16] NOTE: started client
[2024-06-17T12:18:16] NOTE: connecting to '192.168.0.105': 192.168.0.105:24802
2024-06-17 12:18:16.282 barrierc[6309:293079] starting cocoa loop
[2024-06-17T12:18:31] WARNING: failed to connect to server: Timed out
[2024-06-17T12:18:32] NOTE: connecting to '192.168.0.105': 192.168.0.105:24802

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Installed both from github

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

Windows, macOS

What OS versions are you using?

Windows 11
MacOs Sonoma 14.5

Relevant log output

No response

Any other information

No response

[AymenFJA]

Hey, @ShernNing it seems like you are providing the Class C private address (192.168.0.105) of your server (windows) to your client machine (Mac OS).

When you start barrier as a server it provides Class C and Class A (10.0.x.x) or so check the picture attached here one for server (Windows) and one for client (Mac Os):

Based on my experience with barrier, you should use your server machine's Class A IP address for your client's to access barrier server. I hope this will help you to fix our issue. Feel free to report back.

[AymenFJA]

I am also assuming that you already have the correct:

• Screen name of your client.
• port number is set the same on both client and server.

[joemilacek]

Even though it showed SSL as disabled, I got this to work by going into the actual Barrier settings (menu bar > Barrier > change settings) on the Mac side and uncheck SSL.

[Alistair1231]

Even though it showed SSL as disabled, I got this to work by going into the actual Barrier settings (menu bar > Barrier > change settings) on the Mac side and uncheck SSL.

I had to do that on both sides. I thought that having no fingerprint selected on both sides was enough to disable ssl. This seems to not be the case. I think the UI could be clearer about this.