Dcom Error 1009
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: DCOM was unable to communicate with the computer x.x.x.x using any of the configured protocols. dcom error 10009 Windows Server > Windows Server General Forum Question 0 Sign in to vote
Dcom Error Windows Xp
I get this message on a domain controller that i just put into production, running windows server 2008 r2, dcom error 1084 AD 2003. This gets generated almost everytime i reboot the server. It occurs 4 times in succession relating once to each of our external dns forwarders. I have checked that DCOM uses
Dcom Error Windows 10
tcp/ip. I do not believe this to be impacting us significantly however i do prefer to know what this means and how to prevent it.Thanks Tuesday, January 26, 2010 4:40 PM Answers 0 Sign in to vote Hi, Thanks for the post. From your description, I understand that the Event error 10009 stating “DCOM was unable to communicate with the computer %1 dcom server process launcher error using any of the configured protocols” is received on the new DC. 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. For detailed information about the above steps, please refer to the following article: Event ID 10009 — COM Remote Service Availability http://technet.microsoft.com/en-us/library/cc774368(WS.10).aspx Does it work? If the problem continues, please collect the MPSReport from Windows Server 2008 R2. 1. Download proper MPS Report tool from the website below. Microsoft Product Support Reports http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-88B7-F9C79B7306C0&displaylang=en 2. Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After that, click Next, when the "Select the diagnostics you want to run" page appears, select "G
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 06 Oct 2016 15:22:57 GMT by s_hv999 (squid/3.5.20)
SPONSORED BY MICROSOFT See more RELATED PROJECTS XP to Windows 7 Refresh Refreshed aging Dells with Dell AIO Win 7 machines XP conversion Conversion from XP environment https://community.spiceworks.com/topic/349338-dcom-10009-error to Win 7 Personal Security Individual Home use profile security IN THIS http://serverfault.com/questions/266214/event-id-10009-on-server-2008-r2-dcom-was-unable-to-communicate-with-computer-x 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 communicate with the computer (computer name) using any of the configured protocols. Log Name: system Source: DistributedCOM dcom error 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 a DCOM error every time it cant find one of the computers from that other domain. We dcom error windows 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 RELATED TOPICS: DCOM 10016 Error DCOM 10009 Error LyncSQLReplayClient DCOM error  
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 device that had a pulse, regardless of whether or not it was a Wi