@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:
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.
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 18.104.22.168 this does not pose a problem in RDP.