do you use server ports other than the default ones (i.e. 11100)? If so please upgrade to Veyon >= 4.0.7 which contains a fix for remote control with non-default ports. If you didn't change the ports you normally shouldn't encounter any problems. Which authentication method are you using? Are you using access control rules?
I have the same problem. I'm using default configuration and I'm not able to see the remote desktop, it keeps trying.
Telnet to the service ports are ok from and to the computer, I'm not using access control. Any ideas?
pd: version 4.0.7
Hi tobydox, I am also having a problem with it trying to connect forever. I am using Veyon 4.3.1+repack1-2build2 on Linux Ubuntu 20.04 and 3 linux machines all work together but I also have 2 Windows 10 Home machines and neither work. Is there a setting I need to change? They are all on the same home network.
me , too, i have problems to view logged in users in RDP-Sessions on win 2019 and win2012R2 Servers. I'm using default config. Veyon Master is showing computernames and the Name of logged in user at console, but not of the RDP-Users, not on 2012 R2, 2019 and not on Win10. On the Clients / Terminalservers the VeyonClient shows the ports e.g. 11102 but only the client-session of the console shoes "connected to ....". In the other RDP-Sessions the clients shows a different port (e.g. 11102) but not wether it is connected or not. On the Master-PC a telnet to the specific port of the clients works.
All antivirus and firewall settings are deactivated for testing but no positive result.
What else can be the problems in connecting from ussersessions to the master?
(veyon 4.3.5 on windows 2019, 2012 and win10)
Thanks in advance