Dcom Error 10009
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Event 10009 - Dcom was unable to communicate with the dcom error 10009 unable to communicate with computer computer Windows Small Business Server > Small Business Server Question 0 Sign in
Dcom Error 10009 Server 2008 R2
to vote Hi All, I am seeing lots of error events in my SBS 2011 event log
Dcom Error 10009 Server 2008
which say Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 14/07/2011 12:00:58 Event ID: 10009 Task Category: None Level:
Dcom Error 10009 Xp
Error Keywords: Classic User: N/A Computer: ELVIS2011.olt.local Description: DCOM was unable to communicate with the computer xxxx.domain.local using any of the configured protocols. I`ve done some research and came across various posts which direct to the following URL for solution http://technet.microsoft.com/en-us/library/cc774368(WS.10).aspx 1. Now when I open up component dcom error 10009 windows xp services and go to default protocols tab, the only protocol listed there is "Connection-oriented TCP/IP". The article in the URL talks about "appropriate communications protocols", it doesnt gives details on what are those appropriate protocols. I dont know what other protocols am I missing there. 2. it also talks about going to properties of each protocol and verify the settings there are correct. when I go to properties of"Connection-oriented TCP/IP", its just empty there in port ranges field. Do I need to add some port there? 135? Please suggest. many thanks Thursday, July 14, 2011 12:00 PM Reply | Quote Answers 1 Sign in to vote Hi, 1. Check the affected station if the firewall is configured right on these machines, maybe the GPO is not applting correct? 2. Just pinging a name does not say the machine exists if there is a DNS record for a computer it is matched to a ip address, if another computer now uses this ip address you will also get a reply. 3. Open Administrative Tools, DNS manager, browse to forward zone, yourdomain.local and
Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS PDQ Deploy/Inventory We needed something easier and more reliable than Microsoft System Center to push software to eight locations. The DEV environment Quick and dirty build-out for our beloved developers. Internet Cafe Setup I dcom error 10009 xp pro was on vacation when i answered a Skype call and all i heard was 'You got 10 dcom error 10006 days to get this thing working'. An internet cafe with more than 100 computers installed... IN THIS DISCUSSION Broadcom NetXt...net Controller Join the Community! Creating dcom error 10016 your account only takes a few minutes. Join Now I have a server at a client site that is registering DCOM 10009 errors once an hour or so in the event log. There is no other events logged from DCOM with the https://social.technet.microsoft.com/Forums/en-US/6b3a1b12-6582-49a9-86d4-cbe062c1ff43/event-10009-dcom-was-unable-to-communicate-with-the-computer?forum=smallbusinessserver 10009, and the 10009 errors come in pairs, one for each Forwarder I have setup in DNS. An example of the error is listed below (4.2.2.1 and 8.8.8.8). I have done some research on this, and what I have found talks about setting ports and firewall rules to allow RPC so the DCOM request is successful. I don't think that is my answer here given that these are public DNS servers. I am wondering if it has to do with my internal domain name. Instead https://community.spiceworks.com/topic/502109-dcom-10009-error-on-dns-forwarders of %client%.local, they used %client%.com. I'm pretty sure that these errors arent anything to worry about, but they are mucking up my logs and I want them gone. Any suggestions? *Note that the server in question is the DNS server, as it is the only Domain Controller on the network. (I wish they had a backup DC.). That is why the server has itself listed in its DNS config.
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 About Us Learn more about Stack Overflow the company Business Learn more about http://serverfault.com/questions/531043/event-id-10009-dcom hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault 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 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 dcom error 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 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 dcom error 10009 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.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspx share|improve this answer answered Aug 26 '13 at 6:59 Douda 765 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged windows-server-2008-r2 dcom or ask your