10009 Dcom Error
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 Business Server >
Dcom Error 10009 Xp
Small Business Server Question 1 Sign in to vote So I am seeing 1000's dcom error 10009 windows xp of these events in the event log which are becoming quite annoying (I hate a dirty event log) and hard to dcom error 10009 server 2008 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 XP clients to allow connections from
Dcom Error 10006
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 but that was 4+ yrs ago on a 2003
Dcom Error 10016
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 Sign in to vote Hi, Several thinkings: 1. Make sure your SBS 2003 is up-to-date; 2. Disable all
Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Corporate Infrastructure Redesign Upgrade existing Active Directory domain from 2003 to 2008R2, install larger storage servers, utilize virtualization w/ SAN, install backup system, implement network security, ASA firewalls and VLANs. dcom error 10009 xp pro P2V Conversion of all Servers Move physical servers: RedHat EL5, 2x Windows Servers (1 MSSQL, 1 Pervasive
Dcom 10009 Dcom Was Unable To Communicate With The Computer
SQL), 2x Windows workstations running proprietary Scheduling Software, 1x Unbuntu Server for Calendar Server. Windows 7 Deployment Image and Deployment of 40+ HP 8300 dcom error 10009 server 2008 r2 machines with Windows 7. IN THIS DISCUSSION Broadcom NetXt...net Controller Join the Community! Creating 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 https://social.technet.microsoft.com/Forums/en-US/42db9e37-66a5-47a0-be40-0e81e132ffe9/1000s-of-dcom-event-id-10009-errors-in-the-system-event-log?forum=smallbusinessserver or so in the event log. There is no other events logged from DCOM with the 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 https://community.spiceworks.com/topic/502109-dcom-10009-error-on-dns-forwarders 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 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.
Add-on Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and http://www.eventid.net/display-eventid-10009-source-DCOM-eventno-579-phase-1.htm workstation via the Splunk Universal Forwarder. read more... Event ID: 10009 Source: DCOM Source: DCOM Maintenance: Recommended maintenance tasks for Windows servers Type: Error Description:DCOM was unable to communicate with the computer