Errors DCOM (10009) in system logs

[Zuider]

Hi,

I've multiple errors DCOM (10009) in my system logs.

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

For example (in French sorry :p):

"
System 2010-04-15 09:25:40 10009 Error event DCOM xxxx DCOM n'a pas pu communiquer avec l'ordinateur xxxx en utilisant les protocoles configurés.
System 2010-04-15 09:26:27 10009 Error event DCOM zzzz DCOM n'a pas pu communiquer avec l'ordinateur zzzz en utilisant les protocoles configurés.
"

My firewalls are desactived by GPO.

Does anyone know how to clean these up?

Thanks.

[Zuider]

It is possible desactived these eventlog (DCOM 10009) in my system logs ?

[Hemoco]

Zuider wrote:
It is possible desactived these eventlog (DCOM 10009) in my system logs ?

I'm not sure you can do this, I'll have to search for it.

[Zuider]

Thanks for your answer.

But, firewall are not activate on server and the remote computers.

I've very much logs generated by Lansweeper for this eventlogs (DCOM 10009).

It is possible desactived these rapports in my system logs ?

If yes, how do ?

Thanks advance.


Edit: A possible cause can be that the remote computers are shutdown ?

[Hemoco]

Zuider wrote:
Edit: A possible cause can be that the remote computers are shutdown ?

Yes, that's possible.

[sandve]

Lansweeper wrote:

Zuider wrote:
Edit: A possible cause can be that the remote computers are shutdown ?

Yes, that's possible.

Would it be possible to have LS try a different connection method (perhaps a ping) before making a WMI query, thus eliminating error messages for machines that are not currently available on the network?

[Hemoco]

sandve wrote:

Lansweeper wrote:

Zuider wrote:
Edit: A possible cause can be that the remote computers are shutdown ?

Yes, that's possible.

Would it be possible to have LS try a different connection method (perhaps a ping) before making a WMI query, thus eliminating error messages for machines that are not currently available on the network?

Lansweeper did this in the past which caused problems with computers not responding to pings but with the correct ports open.

[Hemoco]

This is indeed caused by a firewall blocking access on the remote computer.