Distributedcom 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 computer distributed com error Windows Small Business Server > Small Business Server Question 0 Sign in
Distributedcom 10009 Domain Controller
to vote Hi All, I am seeing lots of error events in my SBS 2011 event log which distributedcom 10009 unable to communicate 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 server 2008 r2 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 services and
Dcom Error 10009 Unable To Communicate With Computer
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 check the co
Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events event 10009 dcom was unable to communicate Event 10009 (Error) Source: DCOM How important is this event? (41 dcom was unable to communicate with the computer event id 10009 votes) 1 2 3 4 5 not important very important Description < < Add link Text to display:
Dcom Was Unable To Communicate With The Computer 10028
Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text 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 Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages DCOM was unable to communicate with the computer swbend531 using any of the configured protocols.
Jun 12, 2009 DCOM was unable to communicate with the computer tracy using any of the configured protocols. Jun 21, 2009 DCOM was unable to communicate with https://community.spiceworks.com/windows_event/show/4-dcom-10009 the computer 216.34.131.135 using any of the configured protocols. Jun 22, 2009 DCOM was unable to communicate with the computer 192.192.0.139 using any of the configured protocols. Jun 23, 2009 DCOM was unable to communicate with the computer 192.168.200.178 using any of the configured protocols. Jun 26, 2009 DCOM was unable to communicate with the computer 192.168.168.117 using any of the configured protocols. Jul 02, 2009 111 Feb 21, 2013 DCOM was unable to communicate with the computer 192.168.42.101 using any of the configured protocols. Jul 17, 2009 DCOM was unable to communicate with the computer 10.10.10.254 using any of the configured protocols. Jul 24, 2009 DCOM was unable to communicate with the computer tshepo-pc.mds.local using any of the configured protocols. Aug 06, 2009 DCOM was unable to communicate with the computer hutt.deansci.ubc.ca using any of the configured protocols. Aug 08, 2009 DCOM was unable to communicate with the computer sach-compaqhp08.sach.org.sg using any of the configured protocols. Aug 11, 2009 DCOM was unable to communicate with the computer 192.168.165.101 using any of the configured prAnalyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs http://www.eventid.net/display-eventid-10009-source-DCOM-eventno-579-phase-1.htm Free for subscribers 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
TechSpot RSS Get our weekly newsletter Search TechSpot Trending Hardware The Web Culture Mobile Gaming Apple Microsoft Google Reviews Graphics Laptops Smartphones CPUs Storage Cases Keyboard & Mice Outstanding Features Must Reads Hardware Software Gaming Tips & Tricks Best Of Downloads Latest Downloads Popular Apps Editors Picks Device Drivers Product Finder New Releases New PC Games Laptops Smartphones Routers Storage Motherboards Monitors Forums Recent Activity Today's Posts News Comments TechSpot Forums Forums TechSpot Core Networking Today's Posts Event ID: 10009 DCOM was unable to communicate with the computer