Just turned on LDAPS and enforced it on our DCs. Playing with the veyon settings I have found that the following still works

LDAP server and port: DC works but Domain Name doesn't so have specified a DC. Port 389 works however 636 does not

Encryption protocol: TLS
TLS certificate verification: Custom
Custom CA certificate file: Exported CA cert in CER format, changed extension to PEM and plonked onto a share

Hope this helps somebody

OK, that was a problem with my comprehension of veyon.
The port 11400 is listening on master only when you start demo mode.

So i found my error, it was in access control on the master. The user i which i was tested was not authorized.
I wa able to supervise the clients but only the demo mode was bugging because of access control.

Thanks to lyc_appert for his help 😉

@Badbug Yes, restarting the Master machine solve the problem (for a while), but I don't want to restart my Master PC every day, because it's like a server machine in our network

Hi,

Have you tried with the fullpath name of the program ?
If the program is in the environnement PATH, it should work.
I tested with "notepad" and it launch on the client.

So you can try with notepad to see if it work also.

Bonjour
Là :
https://docs.veyon.io/fr/latest/admin/index.html

Hi,
you can use host names instead of ip adress.

can you please elaborate more about your situation?
did u installed the latest version?
what operating system the master and the clients are using

and what you tried to do that made the error appear?