Hello, Could you please helpto find out my issue is " DCOM was unable to communicate with the computer xxxxx using any of the configured protocal Event ID 10009. TheOS is Windows server 2003 R2 STD 32 bit SP2, installed SCCM2007 with SQL 2005, All client is windows XP SP2 I tried to troubleshoot DCOM Event ID 10009 many method , but I can't resolve this issue. I tried the following method : 1: Verify the name resolution is working correctly. 2: Verify the network connectivity is ok. 3. Verify port usage of all SCCM 2007 and DCOM need toopen. 4. Verifythe hotfix ,So Windows Server 2003 SP2 was include that hotfix. 5. disable windows firewall or Allow remote administration exception,All file and printer sharing exception./ Server / Client. 6. Allow Launch permission of DCOM Setting What is anything else to do morethan my method? Please recommend me, how to resolve this issue or suggest tools to trobleshooting this case. Thank you very much Kom

Kom what is it you are attempting to do when this error happens? Remote Control a client?

Hi, I think the error was happens when tried to : 1. I attempting to push install client after update collection membership list in collections group. 2. I did to installationConfigMgrconsole at help desk'sPC . He need to remote to manage SCCM 2007 Server via his PC . Theerror occurwhen I run ConfigMgr Console at help desk's PC to SCCM2007 Server, the error show in system log "DCOM was unable to communicate with the computer xxxxx". I would like add more information about error in conponent status SMS_CLIENT_CONFIG_MANAGER . SMS Client Configuration Manager cannot connect to the machine "ADM219-02". The operating system reported error 1003: Cannot complete this function. Possible cause: The client is not accessible.Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. Possible cause: A remote client installation account was not specified in the SMS Admin console, the account is not valid, is disabled, or has an expired password.Solution: Ensure one or more valid and active remote client installation accounts are specified in the SMS Admin console, that the account names and passwords are correct, and that the account has the required administrator rights on the target machines. I confirm that the client installtion account has admin privilages on the target PC ,because this account is member domain Admin. I don't khow this information can help you to resolvemy issue or not. If you need more information please let's me khow. Thank you Kom

See the following section of the ConfigMgr documentation library "How to Configure DCOM Permissions for Configuration Manager Console Connections". This secrion discusses the necessary DCOM permissions needed to connect to the ConfigMgr server.

We have had this error when the server can't communicate with a client because it is off and we have seen it when the Lease changes in DHCP. There for IP and computer name don't match up so we see this error.

Hi I have done to follow step guide "How to Configure DCOM Permissions for Configuration Manager Console Connections" and Configure Port Windows firewall, but the error still show in system log. Do you any idea for suggest me for solve this issue ?. Thanks Kom

Hi All, Could you please let's me know ,if you have any idea for resolve this issue. I still waiting for your idea to resolve that. Thanks you Kom

I have the same issue, the device that it is trying to communicate with is an HP IP KVM that needs an IP. I gave it one but I don't think there is any place to name it.

who has resolved this issue? I have the same.

My issue is that DCOM wants to communicate with a computername which is the first letter of the local computername. Eg if the computername is Energy01 then the error is "DCOM was unable to communicate with the computer E using any of the configured protocols" This is occuring across multiple servers. If an entry is entered in the hosts file 127.0.0.1 E, then that stops the error but the source of the issue is a mystery. Any ideas?

In my case the message comes for a short duration(4-5 days contineously) and than stops for next 3 months or so and returns back. I had tried all the above solutions but to no avail pl help anybody!!!! thanks in advans

This was in fact caused by a monitoring script running on each server. Now resolved