• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1986
  • Last Modified:

DCOM was unable to communicate with the computer using any of the configured protocols.

I have recently removed a Windows Server 2000 (Primary) Domain Controller from our network and it's replacement (a Win2k8) server has been complaining that it can't communicate with the old server ever since I shut it down. It didn't complain when I demoted it and removed it from the domain, only when I shut it down.

The error message I am seeing every 20mins or so on the Win2k8 DC.

06 Sep 2010  11:40:12 AM
Computer: [New Win2k8 DC]
Monitor: [Event Log Monitor]
* Event Time: 06 Sep 2010 10:55:33 AM
* Source: DCOM
* Event Log: System
* Type: Error Event
* Event ID: 10009
* DCOM was unable to communicate with the computer [Old Win2k DC] using any of the configured protocols.
  • 3
  • 2
1 Solution
excelsupportAuthor Commented:
Thanks, but that doesn't help much. It lists loads of possible causes. The most common of which I had already ruled out (the printer mapping). I have also looked at the DCom protocols but there is nothing obvious.
This is the procedure proposed by TechNet to solve the problem of Event ID 10009: http://technet.microsoft.com/en-us/library/cc774368(WS.10).aspx

Yhe version you use is SBS (Small Business Server) 2008?

excelsupportAuthor Commented:
I've seen this one already - it is all about ensuring the remote computer is online. This computer is not online and never will be again.

I want to find out what is trying to contact the old server. So far all I can find is that the error refers to svchost.exe which as far as I can tell could be any number of things.

The server throwing the error is Win2k8 Standard.
excelsupportAuthor Commented:
This has been painful to identity the source of the problem as this is a production server and I didn't want to cause myself or any users, any problems. So I have been slowly and carefully looking at the services running on this server and I finally tracked the problem down to a server monitoring application that was trying to monitor the old server, despite the fact that the monitoring software exists locally on each and every server so that the application only monitors the server it is installed on.

Removed the entry in the monitoring application for the old server and the logs are quiet again.

Is it still not possible to fully track apps, processes and spawned processes/services in Windows? (Don't try and answer that - its a rhetorical question really - closing this one...)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now