Solved

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

Posted on 2010-09-06
5
1,918 Views
Last Modified: 2013-11-25
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]
Description:
* 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.
0
Comment
Question by:excelsupport
  • 3
  • 2
5 Comments
 
LVL 3

Expert Comment

by:Neurom
ID: 33611222
0
 

Author Comment

by:excelsupport
ID: 33611451
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.
0
 
LVL 3

Expert Comment

by:Neurom
ID: 33612345
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?

0
 

Author Comment

by:excelsupport
ID: 33615582
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.
0
 

Accepted Solution

by:
excelsupport earned 0 total points
ID: 33691965
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...)
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

Whether you’re a college noob or a soon-to-be pro, these tips are sure to help you in your journey to becoming a programming ninja and stand out from the crowd.
A procedure for exporting installed hotfix details of remote computers using powershell
The viewer will learn how to user default arguments when defining functions. This method of defining functions will be contrasted with the non-default-argument of defining functions.
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now