Replies: 1 comment
-
For the benefit of anyone else considering this issue - here is what ultimately worked for me (after a bit of trial and error):
I found that it was necessary to turn off crypto, and explcitly specify the port on the server. This is what works on my machine -- your results may differ. But, perhaps a starting point. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Simple setup - Windows 10 server, and Linux client (AlmaLinux 9). Running barrier 2.4 on both. Things work fine, if -- but only if -- I (i) start barrier on the client using the GUI, and (ii) only if I uncheck auto-config, and then manually enter the server ip (the name doesn't work alone - must enter the ip).
From the CLi, I've tried the following, but it doesn't seem to be working (basically, I'm trying to avoid having to use the GUI -- I want to be able to simply ssh to the machine and run the following, or version of same that works):
Starts fine, and I can see barrierc running as a process, but can't connect to the machine.
Any suggestions, or corrections, would be much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions