Maybe you can open port 135/TCP for your subnet on the reported computer instead of running the mentioned command. DCOM was unable to communicate with the computer MARK-PC.pmc.local using any of the configured protocols. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Bring up the Component Services Administrative tool. 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
But please read for the options. 0 LVL 1 Overall: Level 1 Message Active today Author Comment by:bdhtechnology ID: 362104892011-07-18 I saw this information: TCP/135, TCP/139 But it also states: Do they need yet another banner added? And is there any way to stop it?
x 3 Tim Noble From a newsgroup post: "When I use the Message Tracking Center in Exchange I see all handled messages. x 4 Wayne Prinsloo I found this event after installing Windows 2003 SP1 and updates. Moving the "Computer" (the NAS entry) from the MyBusniess Computers list in the AD to the Computers list right "under" the domain fixed the issue. Dcom 10009 Sbs 2011 See EV100090 - "HP Forum - HPBPRO.EXE killing my server" for further information on this issue.
x 1 Gustavo Hurtado This error is also related with a DCOM/COM+ bug not releasing (consuming) TCP ports between 1024 and 5000 range under heavy load. Dcom Was Unable To Communicate With The Computer 10028 The college in 'Electoral College' Bought agency bond (FANNIE MAE 0% 04/08/2027), now what? Hope it helps sources : http://blogs.msdn.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspx share|improve this answer answered Aug 26 '13 at 6:59 Douda 765 add a comment| Your Answer draft saved draft discarded Sign up or log https://blogs.msmvps.com/bradley/2009/11/28/dcom-was-unable-to-communicate-with-the-computer/ Seemingly, DCOM saw something at that IP address and was trying to communicate with it as if it were the laptop.
Do progress reports/logging information belong on stderr or stdout? Dcom Was Unable To Communicate With The Computer 220.127.116.11 Using Any Of The Configured Protocols HP LaserJet 1320 Toolbox miss-registered itself during standard install, caused two DCOM errors every 35 seconds. could you please tell, how do i verify if the dns has the right ip address for this client or not. Privacy statement © 2016 Microsoft.
Every time when the network health check runs the DCOM event 10009 appeared for some machines (running XP Pro). If using OneCare on the SBS client machines, make sure you are using the Small Business version of Windows Live OneCare. Dcom Error 10009 Server 2008 R2 Most likely it is going to be the PC from DCOM error. Event Id 10009 Dcom Was Unable To Communicate With The Computer What is the proper translation of Breishit (Gen.) 40:16?
There are many possibilities which can cause this issue. check over here More information can be found in ME290512. Cheers! How to fix this? Dcom Was Unable To Communicate With The Computer Domain.local Using Any Of The Configured Protocols
x 1 Anonymous EV100587 (How to troubleshoot DCOM 10009 error logged in system event?) blog article from Microsoft's Development team provides details on why is this event recorded and how to Take a look at this kb article search for 10009, there is a possible solution for configuring the firewall on the affected client. x 1 Anonymous In my case, the error was occurring with high frequency on a Windows Server 2003 Standard running SMS 2003. his comment is here x 99 Anonymous In my case on a Small Business Server 2003 R2 SP2 with ISA Server 2004 apart from receiving this event, when I used WMI tools from the server,
I found the error with "Process Explorer" from Sysinternals. Dcom Was Unable To Communicate With The Computer Dcdiag After reading this thread: http://community.spiceworks.com/topic/249442-dcom-errors-with-64-99-64-32 on the issue, I checked the Spiceworks log (Settings -> Network Scan -> complete log files (link at bottom of page)), I noticed in the 'Network Our approach: This information is only available to subscribers.
I removed the printer object and the errors have ceased. I had tried all the above solutions but to no avail pl help anybody!!!! 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 Dcom Was Unable To Communicate With The Computer Dns Forwarder Client PC'S are set to local static IP'S and are not actually set to obtain if this has any variance.
It had the same ip address assigned as another computer that was being used. This computer had not actually been on the network in months, but the error was showing up every thirty minutes in ten-error bursts. Pimiento May 11, 2012 Zombian Manufacturing I was getting this error for a device that is on the network and functioning properly for months. http://netfiscal.com/dcom-was/event-10009-dcom-was-unable-to-communicate.html Scenario 1:The remote target server happens to be offline for a short time, for example, just for maintenance.
See T774368. Check the affected station if the firewall is configured right on these machines, maybe the GPO is not applting correct? 2. Join thousands of tech enthusiasts and participate. Concepts to understand: What is DCOM?
An example of Our approach Comments: Anonymous Service: MSSQL$BKUPEXEC, OS: Windows SBS 2008 SP2, Software: Backup Exec 2010 Just removed Library Validation Code value from registry. I dont know what other protocols am I missing there. 2. They are still valid but they are either shut down or notebooks that are out of the office at that point. its harmless Add your comments on this Windows Event!
Since i am new to SW my guess this has a lot to do with live reporting of machines on or offline, i was just wondering if there is a way Folder-by-type or Folder-by-feature Did Donald Trump say that "global warming was a hoax invented by the Chinese"? Please suggest. a.
To do this, follow these steps: 1. x 7 Ricky Faulstich The culprit, in my case, was Microsoft SQL Server Management Studio. Issue turned out to be caused by an old DNS entry which was pointing to the machine even though it was no longer present, same IP address was also being assigned