DCOM Error 10009

  • Thread starter Thread starter Jack B. Pollack
  • Start date Start date
J

Jack B. Pollack

Guest
I have a small peer to peer network. One of the machines (XP Pro

SP3) recently started to log DCOM Error 10009 every time Windows boots.

There is a failure event for each machine on the network.



The text of the message is:

DCOM was unable to communicate with the computer COMPUTER NAME using any of

the configured protocols.



This is the only machine doing this, and as I mentioned it just started a

few weeks ago. Nothing has changed or been installed on the system.



There is no spyware or Viruses on this machine.

I have removed all mapped drives and printers.
 
Does the machine logging the error(s) have more than a single Network

Adapter ( 1394..Wireless...) ?



I would do a compare of the Services & Start modes on one of the other

PCs and check it against the one logging the error. I'd pay special

attention

to the Computer Browser service.



"Jack B. Pollack" wrote in message

news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>I have a small peer to peer network. One of the machines (XP Pro

> SP3) recently started to log DCOM Error 10009 every time Windows boots.

> There is a failure event for each machine on the network.

>

> The text of the message is:

> DCOM was unable to communicate with the computer COMPUTER NAME using any

> of

> the configured protocols.

>

> This is the only machine doing this, and as I mentioned it just started a

> few weeks ago. Nothing has changed or been installed on the system.

>

> There is no spyware or Viruses on this machine.

> I have removed all mapped drives and printers.

>

>
 
Thanks for your reply.

Only one network card (no wireless or 1394)



The machine that is logging the errors is setup as the Master Browser.

The other machines are set up not to be MB.



I think these settings were done many months ago but I will go back and

change them and see if there is any benefit.



"R. McCarty" wrote in message

news:uitJl5krKHA.4284@TK2MSFTNGP04.phx.gbl...

> Does the machine logging the error(s) have more than a single Network

> Adapter ( 1394..Wireless...) ?

>

> I would do a compare of the Services & Start modes on one of the other

> PCs and check it against the one logging the error. I'd pay special

> attention

> to the Computer Browser service.

>

> "Jack B. Pollack" wrote in message

> news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>>I have a small peer to peer network. One of the machines (XP Pro

>> SP3) recently started to log DCOM Error 10009 every time Windows boots.

>> There is a failure event for each machine on the network.

>>

>> The text of the message is:

>> DCOM was unable to communicate with the computer COMPUTER NAME using any

>> of

>> the configured protocols.

>>

>> This is the only machine doing this, and as I mentioned it just started a

>> few weeks ago. Nothing has changed or been installed on the system.

>>

>> There is no spyware or Viruses on this machine.

>> I have removed all mapped drives and printers.

>>

>>

>

>
 
I just set



IsDomainMaster back t the default value false

and

MaintainServerList back to default value auto



rebooted, but still have the problem









"R. McCarty" wrote in message

news:uitJl5krKHA.4284@TK2MSFTNGP04.phx.gbl...

> Does the machine logging the error(s) have more than a single Network

> Adapter ( 1394..Wireless...) ?

>

> I would do a compare of the Services & Start modes on one of the other

> PCs and check it against the one logging the error. I'd pay special

> attention

> to the Computer Browser service.

>

> "Jack B. Pollack" wrote in message

> news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>>I have a small peer to peer network. One of the machines (XP Pro

>> SP3) recently started to log DCOM Error 10009 every time Windows boots.

>> There is a failure event for each machine on the network.

>>

>> The text of the message is:

>> DCOM was unable to communicate with the computer COMPUTER NAME using any

>> of

>> the configured protocols.

>>

>> This is the only machine doing this, and as I mentioned it just started a

>> few weeks ago. Nothing has changed or been installed on the system.

>>

>> There is no spyware or Viruses on this machine.

>> I have removed all mapped drives and printers.

>>

>>

>

>
 
I would check the NIC and see what services and protocols are

bound to it.



"Jack B. Pollack" wrote in message

news:%23UcvuImrKHA.3408@TK2MSFTNGP06.phx.gbl...

>I just set

>

> IsDomainMaster back t the default value false

> and

> MaintainServerList back to default value auto

>

> rebooted, but still have the problem

>

>

>

>

> "R. McCarty" wrote in message

> news:uitJl5krKHA.4284@TK2MSFTNGP04.phx.gbl...

>> Does the machine logging the error(s) have more than a single Network

>> Adapter ( 1394..Wireless...) ?

>>

>> I would do a compare of the Services & Start modes on one of the other

>> PCs and check it against the one logging the error. I'd pay special

>> attention

>> to the Computer Browser service.

>>

>> "Jack B. Pollack" wrote in message

>> news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>>>I have a small peer to peer network. One of the machines (XP Pro

>>> SP3) recently started to log DCOM Error 10009 every time Windows boots.

>>> There is a failure event for each machine on the network.

>>>

>>> The text of the message is:

>>> DCOM was unable to communicate with the computer COMPUTER NAME using any

>>> of

>>> the configured protocols.

>>>

>>> This is the only machine doing this, and as I mentioned it just started

>>> a

>>> few weeks ago. Nothing has changed or been installed on the system.

>>>

>>> There is no spyware or Viruses on this machine.

>>> I have removed all mapped drives and printers.

>>>

>>>

>>

>>

>

>
 
Just the regular stuff,

TCP/IP, File & Print sharing, Client for MS Network



"R. McCarty" wrote in message

news:ek2pwOmrKHA.5356@TK2MSFTNGP02.phx.gbl...

> I would check the NIC and see what services and protocols are

> bound to it.

>

> "Jack B. Pollack" wrote in message

> news:%23UcvuImrKHA.3408@TK2MSFTNGP06.phx.gbl...

>>I just set

>>

>> IsDomainMaster back t the default value false

>> and

>> MaintainServerList back to default value auto

>>

>> rebooted, but still have the problem

>>

>>

>>

>>

>> "R. McCarty" wrote in message

>> news:uitJl5krKHA.4284@TK2MSFTNGP04.phx.gbl...

>>> Does the machine logging the error(s) have more than a single Network

>>> Adapter ( 1394..Wireless...) ?

>>>

>>> I would do a compare of the Services & Start modes on one of the other

>>> PCs and check it against the one logging the error. I'd pay special

>>> attention

>>> to the Computer Browser service.

>>>

>>> "Jack B. Pollack" wrote in message

>>> news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>>>>I have a small peer to peer network. One of the machines (XP Pro

>>>> SP3) recently started to log DCOM Error 10009 every time Windows

>>>> boots.

>>>> There is a failure event for each machine on the network.

>>>>

>>>> The text of the message is:

>>>> DCOM was unable to communicate with the computer COMPUTER NAME using

>>>> any of

>>>> the configured protocols.

>>>>

>>>> This is the only machine doing this, and as I mentioned it just started

>>>> a

>>>> few weeks ago. Nothing has changed or been installed on the system.

>>>>

>>>> There is no spyware or Viruses on this machine.

>>>> I have removed all mapped drives and printers.

>>>>

>>>>

>>>

>>>

>>

>>

>

>
 
Thanks for the info. Do all these PCs have the same AV & other security

software ? Also are there any other System/Application Event log warnings

and errors besides the one you listed earlier ?



"Jack B. Pollack" wrote in message

news:eWjReZmrKHA.732@TK2MSFTNGP06.phx.gbl...

> Just the regular stuff,

> TCP/IP, File & Print sharing, Client for MS Network

>

> "R. McCarty" wrote in message

> news:ek2pwOmrKHA.5356@TK2MSFTNGP02.phx.gbl...

>> I would check the NIC and see what services and protocols are

>> bound to it.

>>

>> "Jack B. Pollack" wrote in message

>> news:%23UcvuImrKHA.3408@TK2MSFTNGP06.phx.gbl...

>>>I just set

>>>

>>> IsDomainMaster back t the default value false

>>> and

>>> MaintainServerList back to default value auto

>>>

>>> rebooted, but still have the problem

>>>

>>>

>>>

>>>

>>> "R. McCarty" wrote in message

>>> news:uitJl5krKHA.4284@TK2MSFTNGP04.phx.gbl...

>>>> Does the machine logging the error(s) have more than a single Network

>>>> Adapter ( 1394..Wireless...) ?

>>>>

>>>> I would do a compare of the Services & Start modes on one of the other

>>>> PCs and check it against the one logging the error. I'd pay special

>>>> attention

>>>> to the Computer Browser service.

>>>>

>>>> "Jack B. Pollack" wrote in message

>>>> news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>>>>>I have a small peer to peer network. One of the machines (XP Pro

>>>>> SP3) recently started to log DCOM Error 10009 every time Windows

>>>>> boots.

>>>>> There is a failure event for each machine on the network.

>>>>>

>>>>> The text of the message is:

>>>>> DCOM was unable to communicate with the computer COMPUTER NAME using

>>>>> any of

>>>>> the configured protocols.

>>>>>

>>>>> This is the only machine doing this, and as I mentioned it just

>>>>> started a

>>>>> few weeks ago. Nothing has changed or been installed on the system.

>>>>>

>>>>> There is no spyware or Viruses on this machine.

>>>>> I have removed all mapped drives and printers.

>>>>>

>>>>>

>>>>

>>>>

>>>

>>>

>>

>>

>

>
 
All event logs are clean.

All computers are using Avast and error happens even with AV and firewall

disabled.



"R. McCarty" wrote in message

news:uuFWUgmrKHA.4752@TK2MSFTNGP04.phx.gbl...

> Thanks for the info. Do all these PCs have the same AV & other security

> software ? Also are there any other System/Application Event log warnings

> and errors besides the one you listed earlier ?

>

> "Jack B. Pollack" wrote in message

> news:eWjReZmrKHA.732@TK2MSFTNGP06.phx.gbl...

>> Just the regular stuff,

>> TCP/IP, File & Print sharing, Client for MS Network

>>

>> "R. McCarty" wrote in message

>> news:ek2pwOmrKHA.5356@TK2MSFTNGP02.phx.gbl...

>>> I would check the NIC and see what services and protocols are

>>> bound to it.

>>>

>>> "Jack B. Pollack" wrote in message

>>> news:%23UcvuImrKHA.3408@TK2MSFTNGP06.phx.gbl...

>>>>I just set

>>>>

>>>> IsDomainMaster back t the default value false

>>>> and

>>>> MaintainServerList back to default value auto

>>>>

>>>> rebooted, but still have the problem

>>>>

>>>>

>>>>

>>>>

>>>> "R. McCarty" wrote in message

>>>> news:uitJl5krKHA.4284@TK2MSFTNGP04.phx.gbl...

>>>>> Does the machine logging the error(s) have more than a single Network

>>>>> Adapter ( 1394..Wireless...) ?

>>>>>

>>>>> I would do a compare of the Services & Start modes on one of the other

>>>>> PCs and check it against the one logging the error. I'd pay special

>>>>> attention

>>>>> to the Computer Browser service.

>>>>>

>>>>> "Jack B. Pollack" wrote in message

>>>>> news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>>>>>>I have a small peer to peer network. One of the machines (XP Pro

>>>>>> SP3) recently started to log DCOM Error 10009 every time Windows

>>>>>> boots.

>>>>>> There is a failure event for each machine on the network.

>>>>>>

>>>>>> The text of the message is:

>>>>>> DCOM was unable to communicate with the computer COMPUTER NAME using

>>>>>> any of

>>>>>> the configured protocols.

>>>>>>

>>>>>> This is the only machine doing this, and as I mentioned it just

>>>>>> started a

>>>>>> few weeks ago. Nothing has changed or been installed on the system.

>>>>>>

>>>>>> There is no spyware or Viruses on this machine.

>>>>>> I have removed all mapped drives and printers.

>>>>>>

>>>>>>

>>>>>

>>>>>

>>>>

>>>>

>>>

>>>

>>

>>

>

>
 
I have tracked the problem down to a particular program (Hard Drive

Inspector - a SMART monitoring program). I have contacted the author, but

have not heard back from him.



I am wondering if there are any DCOM diagnostic or logging options that

might help me track down the

problem on this machine as the program is working fine on other computers.







"Jack B. Pollack" wrote in message

news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>I have a small peer to peer network. One of the machines (XP Pro

> SP3) recently started to log DCOM Error 10009 every time Windows boots.

> There is a failure event for each machine on the network.

>

> The text of the message is:

> DCOM was unable to communicate with the computer COMPUTER NAME using any

> of

> the configured protocols.

>

> This is the only machine doing this, and as I mentioned it just started a

> few weeks ago. Nothing has changed or been installed on the system.

>

> There is no spyware or Viruses on this machine.

> I have removed all mapped drives and printers.

>

>
 
Another interesting point:



I also have an image of the computer with the DCOM errors that is about 6

months old. I installed the offending program on it and the old image does

not log the errors. The image is too old to use for this (minor) problem,

but there

must be some minor change to the system that is causing this.





"Jack B. Pollack" wrote in message

news:OpvR61krKHA.3408@TK2MSFTNGP06.phx.gbl...

>I have a small peer to peer network. One of the machines (XP Pro

> SP3) recently started to log DCOM Error 10009 every time Windows boots.

> There is a failure event for each machine on the network.

>

> The text of the message is:

> DCOM was unable to communicate with the computer COMPUTER NAME using any

> of

> the configured protocols.

>

> This is the only machine doing this, and as I mentioned it just started a

> few weeks ago. Nothing has changed or been installed on the system.

>

> There is no spyware or Viruses on this machine.

> I have removed all mapped drives and printers.

>

>
 
You must log in or register to reply here.
Back
Top