Dcom 10009 Error
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 computer Windows Small Business Server >
Dcom Error 10009 Xp
Small Business Server Question 0 Sign in to vote Hi All, I am dcom error 10009 windows xp seeing lots of error events in my SBS 2011 event log which say Log Name: System Source:
Dcom Error 10009 Server 2008
Microsoft-Windows-DistributedCOM Date: 14/07/2011 12:00:58 Event ID: 10009 Task Category: None Level: Error Keywords: Classic User: dcom error 10006 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 services and go to default protocols tab, the only protocol listed there is "Connection-oriented TCP/IP". The article in dcom error 10016 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 check the computer accounts. I see I just forgot to add tht link in the first comment: http://support.microsoft.com/kb/957713 Regards Ronny ------------- Visit my Blog or follow me on Twitter Marked as answer by Rick TanModera
Consultant/SI GROUP SPONSORED BY MICROSOFT IN THIS DISCUSSION Broadcom NetXt...net Controller Join the Community! Creating your account only takes a few minutes. Join Now
Dcom Error 10009 Xp Pro
I have a server at a client site that is registering DCOM 10009 dcom 10009 dcom was unable to communicate with the computer errors once an hour or so in the event log. There is no other events logged from DCOM with the 10009,
Dcom Error 10009 Server 2008 R2
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, 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 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 of %client%.local, they used %client%.com. I'm pretty sure that these errors arent anything to worry about, but https://community.spiceworks.com/topic/502109-dcom-10009-error-on-dns-forwarders 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.
Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS McAfee Endpoint Encryption Deployed McAfee Endpoint Encryption to the enterprise Migrating to new End Point https://community.spiceworks.com/topic/349338-dcom-10009-error Protection Deployed new End Point Security, Webroot to improve system performance and ease http://serverfault.com/questions/266214/event-id-10009-on-server-2008-r2-dcom-was-unable-to-communicate-with-computer-x management. Secure Remote Employee System We have a remote employee who has been using their personal system to access our network via VPN, and this needed to be upgraded for security reasons. IN THIS DISCUSSION GFI Software GFI Business Agent Join the Community! Creating your account only dcom error takes a few minutes. Join Now I get about 30-40 errors of event 10009 every 3-4 seconds. DCOM was 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 dcom error 10009 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 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 dev
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 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 on Server 2008 R2 DCOM was unable to communicate with computer X up vote 3 down vote favorite On Windows Server 2008 R2 I am getting a DCOM event error 10009 "DCOM was unable to communicate with computer X" I can't ping computer X, I don't know what computer X is, and computer X is not in AD. What can I do to either fix this or make it so the events are not logged. windows-server-2008 dcom share|improve this question asked May 4 '11 at 14:07 evolvd 76832351 I can't find any useful information from Google. I would give a bounty for this but don't have enough rep points. –evolvd May 11 '11 at 15:05 add a comment| 3 Answers 3 active oldest votes up vote 0 down vote accepted It could be that computer X is trying to communicate with your server, but the communication fails and the event gets logged on the server too; having the event there doesn't necessarily mean the server itself initiated the connection. About what it could be... well, practically anything. DCOM is the underlying protocol for almost anything that Windows does on the network and is not plain file sharing. If you can't resolve the host name of computer X to an IP address and don't have any other way to fint it, then your only option is using a network sniffer on the server to see where the traffic is coming from. share|improve this answer answered Jun 20 '11 at 21:09 Massimo 47k28134245 add a comment| up vote 1 down vote +100 WMI uses DCOM underneath, so if you have any scripts or monitoring that uses WMI, those scripts could be misconfigured and trying to contact the unknown server. share|improve this answer answered Jun 20 '11 at 21:02 DougN 5701614 This turned out to be my situation. A network monitoring tool, Level Platforms Onsite Manager, was attempting to check WMI almost continuously on any