Dcom Error 10009 Windows Server 2008
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions dcom error 10009 server 2008 r2 TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter
Dcom Error 10009 Unable To Communicate With Computer
Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2
Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols. 10009
Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog
Event Id 10009 Dcom Was Unable To Communicate With The Computer
Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For dcom was unable to communicate with the computer using any of the configured protocols 10028 developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Application Server COM COM Remote Service Availability COM Remote Service Availability Event ID 10009 Event ID 10009 Event ID 10009 Event ID 10006 Event ID 10008 Event ID 10009 Event ID 10011 Event ID 18205 TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Event ID 10009 — COM Remote Service Availability Updated: February 22, 2008Applies To: Windows Server 2008 COM+ applications use Microsoft Component Object Model (COM) technology in Microsoft Windows operating systems to communicate and take advantage of Windows services. COM technologies include COM+, DCOM, and ActiveX Controls. COM+ Network Access enables remote invocation of applications that are built with COM+. The
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site dcom was unable to communicate with the computer domain.local using any of the configured protocols About Us Learn more about Stack Overflow the company Business Learn more about dcom 10009 sbs 2011 hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault dcom was unable to communicate with the computer no longer exists is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The https://technet.microsoft.com/en-us/library/cc774368(v=ws.10).aspx best answers are voted up and rise to the top Event ID 10009 DCOM up vote 3 down vote favorite We have a Server 2008 R2 DC that is generating Event ID 10009 - "DCOM was unable to communicate with the computer X using any of the configured protocol." I found this question: Event ID 10009 on Server 2008 R2 DCOM was unable to communicate with http://serverfault.com/questions/531043/event-id-10009-dcom computer X. The only difference for me is that I know what the "computers" are. They are all our networking gear: switches, routers, firewall, WAPs etc. Why would our DC being trying to contact network equipment via DCOM? And is there any way to stop it? It's really annoying seeing thousands of errors a day in the event log. windows-server-2008-r2 dcom share|improve this question asked Aug 14 '13 at 20:18 josh 28127 Do the error messages follow any sort of pattern? –Mitch May 4 '15 at 18:58 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote I did a bit of research and found an interesting technet blog article from MS about the ID 10009 DCOM Troubleshooting. It does give the reason of the DCOM attempts, but explains you what is triggering the DCOM call and gives tips on getting rid of it. In the same article (comments section from the blog team), it's suggested to run tools like Network Monitor and Process Monitor, look at which process keeps sending failured RPC requests to identify which application is culprit in your scenario. Hope it helps sources : http://blogs.msdn
GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Data Centre Migration Back to Basics Migration. Miami Valley Fire district Designed, Engineered and completed build-out of a https://community.spiceworks.com/topic/349338-dcom-10009-error brand new data center and network infrastructure for a newly formed Fire Department alliance BitLocker Deployment (MBAM) Deploy BitLocker to all laptops in our environment or risk losing our Cyber Security insurance IN http://blogs.msmvps.com/bradley/2009/11/28/dcom-was-unable-to-communicate-with-the-computer/ THIS DISCUSSION GFI Software GFI Business Agent Join the Community! Creating your account only takes a few minutes. Join Now I get about 30-40 errors of event 10009 every 3-4 seconds. DCOM was unable to unable to communicate with the computer (computer name) using any of the configured protocols. Log Name: system Source: DistributedCOM Event ID: 10009 Level: Error User: N/A Here is the full situation, a distributor has brought his laptop to this site, from another domain, and it is spamming DNS requests for computers from his domain, which in turn our server is picking them up and re-requesting them, then giving unable to communicate a DCOM error every time it cant find one of the computers from that other domain. We are talking thousands of errors a minute, it is overflowing the eventlog and has caused the event log to crash a few times now, plus it is causing the network to slow down because the server is using a good chunk of resources handling the thousands of connection requests its creating. I need a way to stop system from searching for these devices that don't exist. I have spent days searching online and not found a solution to this, or even someone who actually has the same issue as me and not just something similar. I even went as far as to completely close off the distributors laptop from the network by having the firewall stop all lan and wan communications from his NICs MAC address. It did not help, it continued for over 8 hours with the original machine uncontactable. Again, the devices DCOM is looking for have never been on the network, they are 100% unknown to this network except for the one non-domain computer is looking for them. How do I make the server stop looking for them also? Reply Subscribe R
PM MESSAGE DCOM was unable to communicate with the computer ANOTHERSERVER.DOMAIN.lan using any of the configured protocol So when you put another server on the network and just set it up for a specific purpose it may not open up all of the needed protocols in the firewall that it needs to correspond to the SBS 2008 box. So here's how to adjust the firewall to get the Dcom messages out of your event logs: Event ID 10009 Source DCOM: http://www.eventid.net/display.asp?eventid=10009&eventno=579&source=DCOM&phase=1 Check the firewall settings and enable the firewall exception rule To check the firewall settings and enable the firewall exception rule: Click Start, and then click Run. 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. In the console tree, click Inbound rules. In the list of firewall exception rules, look for COM+ Network Access (DCOM In). 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 Right mouse click and enable the rule Then to get the server to be able to query thename/model of theremote server enable the WMI in theinbound firewall rules as well. Once you do that your server will report into the console and provide the hardware information on the Network/Computers tab. Posted in: Migrationextras 3 Thoughts on “Dcom was unable to communicate with the computer” Dennis on November 29, 2009 at 3:41 pm said: Should the actions be performed on the SERVER, or on the machine in question that cannot be reached? admin on November 29, 2009 at 4:40 pm said: I was lazy and just did this on the machine in question. You could do a group policy at the server to push out this policy to the machine in question. RVR on December 28, 2009 at 3:29 pm said: As per http://support.microsoft.com/kb/957713 article we have resolved the DCOM issue. 2.1 DCOM Event ID 10009: Problem: The DCOM event ID 10009 will occur when a client workstation has a misconfigured firewall or other issues a