Error 10009 Dcom Windows Xp
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: 1000's of DCOM Event ID 10009 errors in the system event log Windows Small dcom error 10009 server 2008 r2 Business Server > Small Business Server Question 1 Sign in to vote So dcom error 10009 unable to communicate with computer I am seeing 1000's of these events in the event log which are becoming quite annoying (I hate a dirty
Dcom Windows Vista
event log) and hard to find anything else in the event log because so many of these errors. I looked at Microsoft Article ID: 957713 which has you modify the GPO for the
Dcom Microsoft
XP clients to allow connections from the server IP. I configured this even though I have the Windows Firewall turned off on all of my machines and the SBS 2011 server itself. Still having the same issue. I am quite fed up with this. I have seen this in the past and I was able to fix it by modifying something in the component services dcom was unable to communicate with the computer using any of the configured protocols 10009 but that was 4+ yrs ago on a 2003 server and I dont recall my steps. Event ID 10009 Source: Distributed COM DCOM was unable to communicate with the computer xxxxx.xxxxx.local using any of the configured protocols. Please help! Friday, September 28, 2012 11:13 PM Reply | Quote All replies 0 Sign in to vote Are these computers turned off? What OS are they? It's a WMI issue on XP's that I've seen. Saturday, September 29, 2012 12:37 AM Reply | Quote Moderator 0 Sign in to vote On the XP boxes: 1. Start - Run - DComcnfg 2. Expand Component Services 3. Expand Computers 4. Right click My Computer and choose properties 5. Click the Default Properties Tab 6. Is the Enable Distributed COM on this computer checkbox checked? If not, that'll do it. 7. Make sure Default Authentication Level is set to 'Connect' and Default Impersonation Level to 'Impersonate 8. OK, then close Component Services dialog. Chris Chris Saturday, September 29, 2012 1:38 AM Reply | Quote 0 Sign in to vote Some of these are Windows 7 machines Saturday, September 29, 2012 3:05 AM Reply | Quote 0 Sig
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 06:58:33 GMT by s_ac15 (squid/3.5.20)
Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Setup WDS Server Setup WDS server to easily capture and https://community.spiceworks.com/topic/467073-windows-server-2008-r2-dc-10009-dcom-errors-in-system-log-in-event-viewer deploy images on the fly. Setting up WDS Research, testing, and deploying Windows Deployment Services Server OS Upgrades EOL for '03 approaching, so bring on '08! Sadly can't go on to '12 due to software compatibility. TECHNOLOGY IN THIS DISCUSSION Sophos Microsoft Wind...Server 2008 R2 Join the Community! Creating your account only takes a few minutes. Join Now I am getting unable to a ton of these errors in the system log. I have looked on google, and so far no luck. A couple of years ago we had a domain controller fail majorly. I replicated all roles and removed all the records off the old server. I checked again in ntdsutil.exe and the old server is removed and no longer listed in our site. Can you guys give unable to communicate me any ideas? I just am sick of filtering all the errors to find the "real" errors. I am getting 10.1.x.x errors and 169.x.x.x. Strangely I am also seeing 10.249.166.46 which is not even in my scope on my network?! Thank you in advance for your time and expertise! Event ID: 10009DCOM was unable to communicate with the computer 10.1.xxx.xxx using any of the configured protocols. Edited Apr 2, 2014 at 7:59 UTC Tags: Microsoft Windows Server 2008 R2Review it: (211) Reply Subscribe RELATED TOPICS: Windows Server 2008 R2 DC keeps changing to a workstation account Windows Server 2008 R2 DC User Permission Printing issues w/ Kyocera Mita printers on Windows Server 2008 R2 DC   6 Replies Jalapeno OP Kevin2318 Apr 1, 2014 at 3:06 UTC Try this.... not sure if you had SBS in the past, but I have also seen this with a Windows 2008R2 Environment when migrated/upgraded from 2003 Security software that is blocking WMI messages from the server. For example does the security software provide it's own firewall software? Event ID: 10009 Source: DCOM: http://www.eventid.net/display-eventid-10009-source-DCOM-eventno-579-phase-1.htm Event ID 10009 — COM Remote Service Availability: http://technet.microsoft.com/en-us/library/cc774368.aspx Check the firewall settings. http://support.micros