Hi Tobydox

Thank you very much for your reply, that makes sense I see what you mean.

That sounds good! Many thanks for the great software!

@tobydox thank you!

Which version of Veyon are you running? Which VNC software do you have installed? Can you take a look at the log files in C:\Windows\Temp\Veyon*log ?

Hi @Ben-Ronlund
you're right that in Veyon 4.1 all passwords (also including the LDAP bind password) are stored encrypted in the local configuration. Once you upgrade to Veyon 4.1 and modify the configuration they get encrypted automatically (besides other configuration updates). This means you should save your configuration before upgrading to 4.1 as reverting back to 4.0 will make problems.

Unfortunately Veyon currently is not available for Raspberry Pi (armel/armhf/arm64). You can however build packages on your RPI on your own as described in our README file. We might provide binary packages for RPI in the future as well.

Hi @SamGreff

theoretically you can omit the master computer from the configuration with the drawback that auto-discovery of current room will not work. In your case you can enable the setting "Hide local computer" in the Master configuration page in Veyon Configurator. This should hide the master computer while functioning regularly.

OK I'll have a look whether we can improve the connection timeout settings.

Problem #1.
If they are on the same network, then try disabling your firewall.
If the connection is successful, try to open ports
Problem #2.
Check energy settings to try to solve the sleep mode, it could be an option

Thanks for fixing that in a future release.

The message box shouldn't be a problem (and could be a indicator that it works). Custom positions is not that important - to fix the zoom level will be enough.