![]() Dameware now allows to assist remotely without presence of the end-user, who is not in the intranet but travelling. In this release we focused all our efforts to finalise the remote support story with unattended over the internet sessions. I’m thrilled to announce that Dameware 12.0 is now publicly available. I know that NTLM version 1 is deactivated via Security Basline, but I assume Damware is using Version 2? Protocol Version - DWRCS.EXE: 13.000000-0.000000Īuthentication Type: NT Challenge/ResponseĬonnect/Logon timeout setting: 90000 milliseconds ![]() (AcceptSecurit圜ontext).Įrror: Authentication Failed Using Windows NT Challenge/Response. System Message: The operation completed successfully.Īuthentication failed: Socket API recv Failed. I have checked the application log of the remote machine and found these events: ![]() Windows Security Baselines | Microsoft Docs Somebody meet this situation and knows what to do? Is there a configuration in dameware that can be changed to work with the basline or did u change a setting on the baselines? No matter which protocol from the dropdown list (Windows NT Challange / Response, Encrypted Windows Logon. If we now like to use dameware 12 to remote control a computer the authentication is not working through. We've enabled Microsoft's Security Baseline via GPO to our Windows 10 computers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |