| Event Id | 10009 |
| Source | Microsoft-Windows-DistributedCOM |
| Description | DCOM was unable to communicate with the computer %1 using any of the configured protocols. |
| Event Information | According to Microsoft : Cause : This event is logged when DCOM was unable to communicate with the computer using any of the configured protocols. Resolution : Ensure that the remote computer is available There is a problem accessing the COM Service on a remote computer. To resolve this problem: Ensure that the remote computer is online. This problem may be the result of a firewall blocking the connection. For security, COM+ network access is not enabled by default. Check the system to determine whether the firewall is blocking the remote connection. Other reasons for the problem might be found in the Extended Remote Procedure Call (RPC) Error information that is available in Event Viewer. To perform these procedures, you must have membership in Administrators , or you must have been delegated the appropriate authority. Ensure that the remote computer is online To verify that the remote computer is online and the computers are communicating over the network: 1.Open an elevated Command Prompt window. Click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator . If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue . 2.At the command prompt, type ping , followed by a space and the remote computer name, and then press ENTER. For example, to check that your server can communicate over the network with a computer named ContosoWS2008, type ping ContosoWS2008 , and then press ENTER. 3.A successful connection results in a set of replies from the other computer and a set of ping statistics. Check the firewall settings and enable the firewall exception rule To check the firewall settings and enable the firewall exception rule: 1.Click Start , and then click Run . 2.Type wf.msc , and then click OK . If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue . 3.In the console tree, click Inbound rules . 4.In the list of firewall exception rules, look for COM+ Network Access (DCOM In) 5.If the firewall exception rule is not enabled, in the details pane click Enable rule, and then scroll horizontally to confirm that the protocol is TCP and the LocalPort is 135 . Close Windows Firewall with Advanced Security . Review available Extended RPC Error information for this event in Event Viewer To review available Extended RPC Error information for this event in Event Viewer: 1.Click Start , and then click Run . 2.Type comexp.msc , and then click OK . If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue . 3.Under Console Root , expand Event Viewer (Local) . 4.In the details pane, look for your event in the Summary of Administrative Events , and then double-click the event to open it. 5.The Extended RPC Error information that is available for this event is located on the Details tab. Expand the available items on the Details tab to review all available information. Verify : You can verify that the COM service is available remotely by running the Component Services administrative tool and ensuring that the required properties for remote access are configured. To perform these procedures, you must have membership in Administrators , or you must have been delegated the appropriate authority. To open Component Services and verify that the required properties for remote access are configured: 1.Click Start , and then click Run . 2.Type wf.msc , and then click OK . If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue 3.To locate your computer, click Component Services , click Computers My Computer . 4.Right-click My Computer , and then click Properties . 5.Click the Default Protocols tab, and confirm that the appropriate communication protocols are listed. 6.Click each protocol, and then click Properties to verify that the settings for the protocol are correct. You can verify that the COM+ Network Access firewall exception rule is enabled so that components can communicate over the network To open Windows Firewall with Advanced Security and verify that the firewall exception rule for COM+ Network Access is enabled: 1.Click Start , and then click Run . 2.Type wf.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue 3.In the console tree, click Inbound rules. 4.In the list of firewall exception rules, locate COM+ Network Access (DCOM In). 5.Ensure that this firewall exception rule is enabled, and then scroll horizontally to confirm that the protocol is TCP and the LocalPort is 135 . ------------------------------------------------------------------------------------------------------------------------According to News group : Please follow the steps to resolve the problem: a) Is there a firewall between the DC and the machine ED2003? b) Please telnet to ED2003 with port 135: telnet IPofED2003 135 where IPofED2003 is the IP address of ED2003 c) Form the problematic DC, try to ping ED2003 and connect to it via run \\ED2003 d) Let's clean boot the DC. This will isolate any third-party application from causing the issue. To so do, 1. Click Start, select RUN and type msconfig and press enter 2. On the Startup page, click Disable All. 3. On the Services page, mark the checkbox before "Hide All Microsoft Services" and then click Disable All. 4. Click Apply and click OK, restart Server. 5. Run for some time and check if the issue persists. |
| Reference Links | Event ID 10009 from Source Microsoft-Windows-DistributedCOM |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.