Re: DCOM Error 10009

From: John John (audetweld_at_nbnet.nb.ca)
Date: 01/24/05


Date: Mon, 24 Jan 2005 10:29:09 -0400

Maybe this can help:

How to disable DCOM support in Windows
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B825750

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

S Sainsbury wrote:

> 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?



Relevant Pages

  • DCOM Error 10009
    ... On one of our Windows 2000 Servers every few minutes a DCOM error is ... generated which is logged in the event log. ... the primary default protocol and the only datagram protocol listed is IPX ... The Server is a DC and a Print Server I have also tried using the ...
    (microsoft.public.win2000.networking)
  • [Full-Disclosure] NTBUGTRAQ on DCOM
    ... So I have been running around recommending that everyone get DCOM disabled. ... Microsoft provides a wonderfully vague warning, ... Warning, if you disable DCOM, may you may lose operating system ... The local COM+ snap-in will not be able to connect to remote servers to ...
    (Full-Disclosure)
  • Re: DCOM Problems
    ... Windows Registry Editor Version 5.00 ... > It's a bug with Microsoft Word. ... > see if the error goes away, DCOM is a HUGE security risk anyway. ... > How to disable DCOM support in Windows ...
    (microsoft.public.win2000.general)
  • Re: DCOM Problems
    ... It's a bug with Microsoft Word. ... BUG: Word 2000 Version Key Doesn't Match Its Type Library Version ... see if the error goes away, DCOM is a HUGE security risk anyway. ... How to disable DCOM support in Windows ...
    (microsoft.public.win2000.general)
  • svchost.exe | exe.tsohcvs
    ... This has something to do with DCOM. ... To disable DCOM, change this value ... If EnableDCOM is not set to "Y," then all cross-computer ... I always go to windows updates and do ...
    (microsoft.public.windowsxp.security_admin)