Event 10028 DCOM was unable to communicate with the computer

Event error 10028 may occur when ports between computers or servers are blocked. The description in your event log then shows:
Event 10028 DCOM was unable to communicate with the computer X using any of the configured protocols; requested by PID 1b18 (C:\WINDOWS\system32\ServerManager.exe).
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Event ID: 10028
Level: Error

Event 10028 DCOM was unable to communicate with the computer

In my case, I was trying to manage some servers with Server Manager. These servers existed in another VLAN. But you may also encounter this error when

  • you have enabled the Windows Firewall, or
  • you have not enabled File and Printer sharing on the target machine
  • the computer is not in your network (anymore), but the DNS  record still exists

To solve this error:

  • try to disable the firewall on the target computer
  • enable File and Printer sharing on the target computer
  • remove the computer from Server Manager (if you don’t want to monitor)
5 1 vote
Article Rating
Subscribe
Notify of
guest
5 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Iwan

remove the server from Server manager is the solutuion

1
Reply
darshan shah

But if we didn’t remove any node from Cluster still we get this error then what to do ?

0
Reply
Pat

We encountered this issue where there were DCOM errors every 5 mins across all DCs in the domain. After doing some digging we found it was being caused by a scheduled task “\Microsoft\Windows\CertificateServicesClient\SystemTask”. After doing some further review of the domain, we found that certificate auto enrollment was configured in the Default Domain Policy. However, at the time of the issue, the environment did not have any active Certificate Authorities. Using the CMD utility CertUtil.exe and the -ADCA, we found there were four CA’s present that were from over a decade ago and are no longer in the domain. So,… Read more »

2
Reply
Rene 
In my case there was a certifying server, which was no longer on the network.
Run the ADSIEDIT command at configuration+CN=Services+CN=Public Key Services+CN=Certification authorities.
Delete the server that had that property and no more events came out
4
Reply
Rene 
In my case there was a certifying server, which was no longer on the network.
Run the ADSIEDIT command at configuration+CN=Services+CN=Public Key Services+CN=Certification authorities.
Delete the server that had that property and no more events came out
2
Reply

Related Posts

5
0
Would love your thoughts, please comment.x
()
x