Freakz Sep 16, 2010   6:58 AM GMT

I just love people how state the blatantly obvious. Well here is a constructive answer. Check that the group “Domain Controllers” is a member of the group CERTSVC_DCOM_ACCESS. Reboot the client and try again. //M

10 pointsBadges:

dvodvo Mar 25, 2014   9:18 AM GMT

Check the syste, security log entries found at: Start->All Programs->Administrative Tools->Component Services (Expand)->Event Viewer (Local)->Windows Logs->Security

In case your server is not part of a domain, such that adapting the group settings for CERTSVC_DCOM_ACCESS does not apply:
If remote login is denied due to unknown username/password, you may add on the server side a user and corresponding password matching the user that on the client side needing access to the service.
Also make sure that the respecitive access rights are granted, for instance:
Start->All Programs->Administrative Tools->Component Services (Expand)-> Computers (Expand)->My Computer (right-click)->Properties.
In the COM Security tab:
Access Permission->Edit Limits->Everyone->Remote Access
Launch and Activation Permissions->Edit Limits->Everyone->Remote Launch

10 pointsBadges:

Subhendu Sen Mar 25, 2014   12:24 AM GMT

For checking purpose, u can do manually request the domain controller certificate in teh certificate snap-in. 

140,850 pointsBadges:

Genderhayes Mar 26, 2014   1:56 AM GMT

This happens when you create your CA on a Domain Controller and the “Domain Controllers” security group is missing from the “CERTSVC_DCOM_ACCESS” Domain Local Security Group

10,730 pointsBadges: