DCOM Event 10009 in System Event Viewer

[William]

First of all let me say that I think this is a GREAT product and I wish I had come across it years ago! Thank you for all your hard work.

I'm noticing that I'm now getting a LOT of the following error in the System Event log:

Source: DCOM
Category: None
Type: Error
Event ID: 10009
USER: DOMAIN\lansweeper
Computer: SERVER
Description: DCOM was unable to communicate with the computer 192.168.0.x using any of the configured protocols.

Has anyone else come across this and is there a resolution?

Thanks in advance,

\/\/

[Hemoco]

Possibly dns problems (resolving to the wrong IP)

[ngalioto]

Thank you for your response,

Any other causes you can think of, I performed a netstat on client which shows port 135 open and listening.
Our group policy keeps firewalls on all clients disabled.
Any suggestions on how to troubleshoot?

Thanks in advance,
Nic

[ngalioto]

Still looking for a resolution to this problem.......... Any Ideas Lansweeper Administators

I'm noticing that I'm now getting a LOT of the following error in the System Event log:

Source: DCOM
Category: None
Type: Error
Event ID: 10009
USER: N/A
Computer: SERVER
Description: DCOM was unable to communicate with the computer (computer name here) using any of the configured protocols.

Has anyone else come across this and is there a resolution?

[Hemoco]

ngalioto wrote:
Still looking for a resolution to this problem.......... Any Ideas Lansweeper Administators

I'm noticing that I'm now getting a LOT of the following error in the System Event log:

Source: DCOM
Category: None
Type: Error
Event ID: 10009
USER: N/A
Computer: SERVER
Description: DCOM was unable to communicate with the computer (computer name here) using any of the configured protocols.

Has anyone else come across this and is there a resolution?

Most likely cause : windows firewall is blocking access to port 135 on the client.

[Hemoco]

Maybe there is a problem with your dns lookup of a client.

Are you sure that there isn't a computer on that address?
Check the table tblCPlogoninfo to find out which client logged on from this IP

[William]

What if I told you that there was no client at that IP?

[Hemoco]

Your server cannot communicate with the client 192.168.0.x using RPC.
Check if the client is not firewalled, ...
Use the connectiontest utility.