@paulthedate
Answer was I needed to use the IP instead of Hostname in the Configurator. now all good.

@tobydox https://prnt.sc/1e1d6oj
I have a problem I can't import the key so it appears

https://prnt.sc/1e1d6oj

Hi,
The way to fix this problem :

install the lightdm package on the PC running gdm select lightdm option during installation reboot

Juste one question :
For which reason does the command "telnet localhost 11100" is OK just after the lightdm installation and not before with GDM ???

V.Le Mieux

@tobydox Not technical enough! Does not the entire internet work through TCP/IP? That's like saying that you can listen to the radio, as long as your radio can pick up the electro magnetic waves.

Though I suppose the caveat "directly" offers some clues. I suppose you mean to suggest that the IP route is unobstructed, and not behind NAT or firewalls, right? Can you elaborate on the security risks or design paradigm a bit? Is all I have to do is forward the 11100 and 11400 ports?

Are you using key file or logon authentication? In case of logon authentication the bottleneck could be your AD server since it has to handle authentication requests from all Veyon clients at the same time (since each client checks the credentials of the teacher to authenticate the connection).

@erict: indeed the authentication key name check is too strict at the moment since it only allows word characters (0-9, a-z, A-Z and underscore). I just committed a fix which will also allow the minus character (https://github.com/veyon/veyon/commit/768feeb53c11d7a1f5e5fa4d8378d795c73cc1ad). It will be part of Veyon 4.5.7 next month. In case you build packages on your own, you can simply do this for the latest 4.5 branch.

Besides that, importing keys via veyon-cli should work with the following command:

veyon-cli authkeys import veyon_master/public public-key.pem

A red screen usually indicates authentication problems, i.e. either the authentication keys have not been setup properly on both teacher and student computers or logon authentication fails due to invalid credentials entered on Veyon Master startup.

@stuartr Interesting! Does it work with 4.5.5? I'm asking because we upgraded the 3rdparty OpenLDAP library in 4.5.6 so the crash might be related to that.

@tobydox I don't see where to add the parameter. I switched to advanced mode, under "service" I don't see any place to add a parameter under the VNC server section.

Hello Tobydox
I now know the problem of error 87 ... but I don't know how to solve it yet ...
the error occurs if I am connected in RDP on the machine on which I am installing Veyon. if I am physically connected to the machine no more error 87 problem. From the information I could read, this is related to graphics driver problem ...
But you have necessarily done something about the graphics settings since until version 4.5.4.3 this does not pose a problem in RDP.
Fred

Have you installed all available Windows updates? The AcceptSecurityContext call has been an issue with certain updates 1 or 2 years ago. As a workaround you can enable the Use alternative user authentication mechanism option in the Windows configuration page in Veyon Configurator after enabling the advanced settings (View -> Advanced).

FYI: the issue has been fixed in Veyon 4.5.6.

As written elsewhere already, nested AD groups are supported by Veyon 4.5.6 and newer.