Master can't access Ubuntu clients joined in a MS Active Directory



  • I am having problem with the following configuration:
    Master: Windows 10 Pro x64 (latest version of Veyon)
    Clients: Ubuntu 18.04.2 LTS (latest version of Veyon, installed by ppa)
    These Ubuntu clients have joined an MS AD domain. Students can log on with their MS AD credentials. Authentication works fine, but the Veyon service does not start. But when a local Ubuntu user with/without administrator rights logs in, the service is started and the master can connect to the client. And after that, I can log off the local user, log on to a domain user, and the service keeps running. The problem occurs when the computer starts and a domain user logs on. The screen remains "red" in the Master.
    I have tried key and login authentication methods, and the same problem happens. Can this be caused because I'm using PAM? I saw something about the PAM configuration in the documentation, but I did not understand what I needed to do.



  • After several tests, I have verified that the service does not start only on the first logon of an AD user on the computer. If someone else has this problem, the solution is to edit the /etc/pam.d/systemd-user file and add the line: @include common-session just below the line @include common-session-nonintercative. Because it is in the "common-session" file that the creation of directories for AD users via PAM is usually configured.


Log in to reply