@ARoger It doesn't work

Go to Veyon Configurator, Locations, and Computers, Go to your Computer list and look for a + icon in the right box, now add it like the other ones you did, and you should be fine.

Following up on this... I wasn't thinking yesterday. What I did was to just create a local user account with the same password as my network account. I actually made two of them because I wasn't sure which one I needed and didn't want to spend too much time in this. I did make these local accounts members of one of the groups that my domain account is a member of, also the same group as the normal local user logs into. Not sure if that's important, but I did it anyway. #1 username and #2 username.domain (not full domain, example .google not the .com part) And now I can see and control this computer, I'll configure the second computer when I have time.

Having a similar issue here. Not using LDAP for anything just key based auth but whenever the master is launched the AD account of the user running it is locked out. Version 4.8.2 Config: { "AccessControl": { "DomainGroupsEnabled": "false", "UserGroupsBackend": "2917cdeb-ac13-4099-8715-20368254a367" }, "Authentication": { "Method": 1 }, "Core": { "ApplicationVersion": 8, "InstallationID": "634bdaa2-e820-4ca8-b94a-7d174b240dd9", "PluginVersions": { "JsonStoreObject": { "{14bacaaa-ebe5-449c-b881-5b382f952571}": "1.1", "{1b08265b-348f-4978-acaa-45d4f6b90bd9}": "1.1", "{1baa01e0-02d6-4494-a766-788f5b225991}": "1.1", "{2917cdeb-ac13-4099-8715-20368254a367}": "1.1", "{2ad98ccb-e9a5-43ef-8c4c-876ac5efbcb1}": "1.1", "{387a0c43-1355-4ff6-9e1f-d098e9ce5127}": "1.1", "{39d7a07f-94db-4912-aa1a-c4df8aee3879}": "1.1", "{4122e8ca-b617-4e36-b851-8e050ed2d82e}": "1.2", "{4790bad8-4c56-40d5-8361-099a68f0c24b}": "1.1", "{67dfc1c1-8f37-4539-a298-16e74e34fd8b}": "1.1", "{6f0a491e-c1c6-4338-8244-f823b0bf8670}": "1.2", "{80580500-2e59-4297-9e35-e53959b028cd}": "1.2", "{8ae6668b-9c12-4b29-9bfc-ff89f6604164}": "1.1", "{a54ee018-42bf-4569-90c7-0d8470125ccf}": "2.0", "{d4bb9c42-9eef-4ecb-8dd5-dfd84b355481}": "1.0", "{e11bee03-b99c-465c-bf90-7e5339b83f6b}": "1.0", "{ee322521-f4fb-482d-b082-82a79003afa7}": "1.1", "{f626f759-7691-45c0-bd4a-37171d98d219}": "1.0" } } }, "Features": { "DisabledFeatures": [ "{6f4cd922-b63e-40bf-9451-536065c7cdf9}" ] }, "LDAP": { "ComputerLocationAttribute": "", "ComputerLocationsByAttribute": "false", "ComputerLocationsByContainer": "false", "LocationNameAttribute": "", "UserLoginNameAttribute": "" }, "Master": { "AccessControlForMasterEnabled": "true", "AllowAddingHiddenLocations": "false", "AutoAdjustMonitoringIconSize": "false", "AutoOpenComputerSelectPanel": "false", "AutoSelectCurrentLocation": "false", "ComputerMonitoringUpdateInterval": 3000, "ConfirmUnsafeActions": "false", "EnforceSelectedModeForClients": "false", "HideComputerFilter": "false", "HideEmptyLocations": "false", "HideLocalComputer": "false", "RemoteAccessImageQuality": 2, "ShowCurrentLocationOnly": "false" }, "Network": { "FirewallExceptionEnabled": "false", "VeyonServerPort": 11100 }, "NetworkObjectDirectory": { "Plugin": "14bacaaa-ebe5-449c-b881-5b382f952571" }, "Service": { "ClipboardSynchronizationDisabled": "true", "FailedAuthenticationNotifications": "true", "HideTrayIcon": "true", "RemoteConnectionNotifications": "true" }, "VncServer": { "Plugin": "39d7a07f-94db-4912-aa1a-c4df8aee3879" }, "Windows": { "SoftwareSASEnabled": "1" } }

La password è corretta!

Hi, Thank you for the answer. Indeed, by putting a UNC path I no longer have the problem of access denied. It's a total success of the working class !

We've noticed this problem too - we thought there should be an option to disable the client keyboard/mouse input whilst you are using remote control. The same use case applies to lock mode, but this remote input disable isn't implemented as a function in Veyon. The VNC backend should support these functions already - so can the Veyon Client and Master make use of these?

Hi, Parsing veyon conf for something else, I noticed this : WebAPI/HttpServerEnabled=false It's the default conf (I didn't touch anything about this). Maybe modify this parameter should help (if you didn't yet). (I didn't try, I don't use webapi... Just an information I found by chance and I thought could help you ) E.T.

I forgot something in my previous post : VERY IMPORTANT : The table in your nft file must be named like the file (the name you gave in veyon-configurator) too, or you won't be able to deactivate blocking from master. As example, if you declare "myfile" in veyon-configurator: On clients, you must put a file called myfile in /etc/veyon/iac/firewall/rules.d/, containing your rules, and the table in this file must be called myfile too : table inet myfile { Don't forget to activate InternetAccessControl/UnblockOnServiceStart=true in veyon config, this is the best (only?) way to be sure internet is available for next users, without any need to do anything (automatically deactivates blocking on clients when the user logs out, or reboots). Finally got all this running like I wanted to... Thanks to Todybox for his precious help (and job on Veyon, of course). E.T.

I answer myself. The problem is wayland : I deactivate it and now veyon master can access the ubuntu workstations