Simply remove the /etc/veyon directory as well as the configuration file /etc/xdg/Veyon\ Solutions/Veyon.conf. Afterwards you can start from scratch

Hi, Not a pro with veyon, just a "basic" user, but here are some informations that maybe could help you : Key authentication is not needed for veyon to work (I managed many classrooms without using it). Although your laptops addresses are dynamic, they can be fixed. If you have access to dhcp configuration, you can declare your devices, and assign a fixed address to each one. In dhcpd conf file, it looks like : host pc1 { hardware ethernet 68:5d:43:2a:f3:af; fixed-address 10.21.27.101; } (MAC and IP addresses should be changed, according to your devices and network) Maybe it could allow you to declare IP addresses in Veyon and fix your issue with laptops appearing or not in veyon-master (I'm not sure of which parameter veyon uses to "recognize" PCs). You should maybe describe a little more your context to help someone to help you (what kind of network, which part of the infrastructure you have access to...) If you don't manage the network, you should see with an admin to help you. Hope it can help a little bit, ET

Thank you for your feedback and your tests! They'll help us to investigate this issue and hopefully find a solution for the next release.

Hi, really i've had no probs with 4.1.7 and 30 pc with win10 Are you sure in the General tab of the configurator there is the connection through key file ? It is not the default

I tried to upgrade graphics driver, didnt help. After upgrading Veyon to 4.2 Alpha (4.1.91), the problem is solved and everything works fine. Thank you.

@tobydox Thanks for your help Tobydox, i have tried in cmd under windows and i always get an error. If i try with the graphic interface authentification "@" in my password this work perfectly.

In the Veyon Configuration (Master -> Behaviour) you can enable the option "Enforce selected mode for client computers" which should automatically re-lock computers once logged on again.

Hi, yes I have changed the network object directory backend to "LDAP" ! Best regards

Hello and thanks Recursive search is active, but it is also needed because of the nesting of user groups and room groups. This is related to bugtracker https://github.com/veyon/veyon/issues/465 . The renaming is a working workaround for me. Pay attention to the alphabetical order of nested items in the LDAP tree. -workstations -- Workdepartment1 ---- Room01 ---- Room02 -- Workdepartment2 ---- Room03 ---- Room04 That's how it works for at the moment.

Which installation directory did you use for Veyon? Maybe some special characters with accents etc.? Can you try to set the log level in Veyon Configurator to "Debug" and look for VeyonService.log in C:\Windows\Temp?

In order to connect to a client TCP port 11100 (Veyon Server) has to be accessible. 11200 is just the port of the internal VNC server which is used by Veyon Server internally only. Are you using a dedicated firewall or internet security software?

Hello, I suggest to increase the log level to "Debug" in Configurator, clearing log files and take a look at the log files on the affected clients (C:\Windows\Temp\VeyonServer.log) after opening Veyon Master on the teacher computer. You might find further information in the log files on what's going on and what causes the failure.

Unfortunately Veyon 4.2 is already delayed and we did not manage to get this implemented We still try to get this done in Veyon 5.

Did you configure Veyon to use IP addresses or hostnames? When using hostnames make sure your DNS setup is working properly, i.e. names can be resolved to IP addresses with regular DNS and not WINS/NETBIOS only.

Are you using logon authentication or key file authentication? If logon authentication, can you logon into Veyon Master application on a Windows 10 machine?

As Veyon simply launches the default browser so you'll have to configure your system to use Chrome as the default browser.

Hello @herge you can achieve the desired behaviour by setting up access control rules and deploy the updated configuration to all clients. You'll have to define rules for explicitely granting access under certain conditions, i.e. "logged on user is member of group <students>".