asked on

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]
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.

Neurom

Try look this: http://www.eventid.net/display.asp?eventid=10009&eventno=579&source=dcom&phase=1

excelsupport

ASKER

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.

Neurom

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?

excelsupport

ASKER

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.

ASKER CERTIFIED SOLUTION

excelsupport

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial