DCOM Error 10009

[Guest]

On one of our Windows 2000 Servers (SP4) every few minutes a DCOM error is
generated which is logged in the event log. The error is as follows...

DCOM was unable to communicate with the computer (name of computer) using
any of the configured protocols. This error is generated on average every
couple of minutes.

I have read KB article 245197 and the workstation named in the event log is
only running TCP/IP and no datagram protocols. The W2K server has TCP set as
the primary default protocol and the only datagram protocol listed is IPX
which is at the bottom of the protocol list.

The Server is a DC and a Print Server I have also tried using the
dcombobulate program as suggested in another post but as the server is behind
a firewall and router etc all ports are stealthed so the program is unable to
determine the status of DCOM.

Can any one help?

 

[John John]

Maybe this can help:

How to disable DCOM support in Windows
http://support.microsoft.com/default.aspx?scid=kb;en-us;825750

Microsoft always says not to disable DCOM because your teeth may all
fall out if you do! But over the long years I have found out 3 things
about DCOM:

1- It is so incredibly complicated to understand and figure out that
you almost need a masters degree in computer science to configure it
properly. I have no such degree and I don't expect to ever live long
enough to figure it out by myself.

2- Hardly no software vendors other that Microsoft uses or bothers with
DCOM. MS Office seems to be the vehicle of choice for MS to make use of
DCOM, but hardly no one really needs it anyway, you do not need DCOM
enabled for Office to work properly.

3- I have always disabled DCOM on all my machines and have never
suffered ill effects thereafter.

Disclaimer: Your mileage may vary. You may have software that needs or
uses DCOM and you may have MS Office programs set to use DCOM properly
and it may be useful in some cases. If your MS Office users complain
that they can no longer "collaborate" after you disable DCOM you will
have to try to debug DCOM... or hire a university professor to come and
fix it for you.

John