Name of computer not reacheable

[zedodo]

I reopen my previous issue (Upgrade problem with windows X 1809).
I worked on this problem, and get news information.

First it occurs only on freshly (new) installed computers with windows 1809, and all last updates. The computers joined a domain before installing Veyon. The computer is defined with his name in the computer room.
Veyon in this situation do not appear in Veyon MAster (grayed computers), while well defined in the computer list

I'm using 4.1.90 for this issue, but I suspect it is the same on 4.1.6

On new installed computer (windows 10 1809, all updates, computers in a domain) the computer has to be defined
with his IP address in order to be visible in Veyon Master. Using his name did not work (computer stayed in gray)

The name access is working if the computer was updated from a previous version of Windows, and a previous version of Veyon...

I got this on the 5 new computers we got in our lab.

FYI, here is a summary of the log on the workstation, using the 4.1.90 release when the computer is defined
with his name in Veyon master.

APPLICATION EVENTS

int WinVNCAppMain() : ***************** SDEvent created --The system cannot find the file specified.
DWORD imp_desktop_thread(LPVOID) : OpenInputdesktop OK --The parameter is incorrect.
void vncProperties::Load(BOOL) : ***** DBG - Entering Load --Data error (cyclic redundancy check).
int WinVNCAppMain() : ################## SHUTING DOWN SERVER #################### --Attempt to release mutex not owned by caller.
VBool VSocket::Shutdown() : shutdown socket --Data error (cyclic redundancy check).
VBool VSocket::Close() : closing socket --A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.
VBool VSocket::Close() : closing socket --Data error (cyclic redundancy check).
virtual void* vncSockConnectThread::run_undetached(void*) : quitting socket connection thread --An operation was attempted on something that is not a socket.
VBool VSocket::Close() : closing socket --No connection could be made because the target machine actively refused it.
VBool VSocket::Close() : closing socket --An operation was attempted on something that is not a socket.
virtual void vncServer::KillAuthClients() : KillAuthClients() done --An operation was attempted on something that is not a socket.
int WinVNCAppMain() : ***************** SDEvent created --The system cannot find the file specified.
DWORD imp_desktop_thread(LPVOID) : OpenInputdesktop OK --The parameter is incorrect.
void vncProperties::Load(BOOL) : ***** DBG - Entering Load --Data error (cyclic redundancy check).

SYSTEM EVENTS

The Veyon Service service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

As the classes restarted this week, this becomes more and more urgent. Some help will be greatly appreciated
Thanks
Nicolas