The other DCs don't show this error probably because dcdiag wasn't run on them. (your post suggested the DCOM error was triggered by dcdiag) –strongline Jun 18 '15 at 16:44 Interview question "How long will you stay with us?" In what spot would the new Star Wars movie "Rogue One" go in the Machete Order? MS Article Link : http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/353d381d-0911-41c3-98fb-2475b65c32f6 Any assistance appreciated in resolving. Client PC'S are set to local static IP'S and are not actually set to obtain if this has any variance. have a peek at this web-site
Edmund Friday, June 22, 2012 6:14 PM 0 Sign in to vote Nice find, Greg. The error logs are filling up on a number of computers. The error logs are filling up on a number of computers. The (portable) machine may have just been switched off, or the owner may be on the road at the given moment. http://www.lansweeper.com/kb/139/dcom-was-unable-to-communicate-with-the-computer.html
Windows Server > Windows Server General Forum Question 0 Sign in to vote I get this message on a domain controller that i just put into production, running windows server 2008 I have delted every printer, deleted every file/regkey etc that might possibly containg the orginal host name. Jul 15, 2010 #3 harihar rautara TS Rookie In my case the message comes for a short duration(4-5 days contineously) and than stops for next 3 months or so and returns No, create an account now.
Please help. Additional: Extended info dump from one of the events on a SBS2011 server
It occurs 4 times in succession relating once to each of our external dns forwarders. Check with your firewall manufacturer for the proper ways of allowing dynamic RPC traffic. * If the workstation is on a different subnet than the SBS server and it is running Thursday, February 09, 2012 1:42 AM 0 Sign in to vote Holy Hannah! Could someone post a fix pls.
This problem may be the result of a firewall blocking the connection. Dcom Was Unable To Communicate With The Computer Dns Forwarder Repeat Steps 7.a and 7.b for the following rules: Windows Firewall: Allow inbound remote administration exception Windows Firewall: Allow inbound remote desktop exceptions Post Navigation ← Previous Post Next Post → Reply Skip to main content Follow UsArchives October 2016(1) September 2016(2) August 2016(3) March 2016(2) February 2016(1) January 2016(4) December 2015(2) November 2015(1) August 2015(2) June 2015(2) December 2014(1) November 2014(2) Any help appriciated.
Reply Danie de Wet says: June 13, 2013 at 1:30 am Many thanks for sharing knowledge in down to earth explanation!! https://community.spiceworks.com/topic/288546-dcom-was-unable-to-communicate-with-the-computer-64-99-64-32 For security, COM+ network access is not enabled by default. Dcom Was Unable To Communicate With The Computer Event Id 10009 Go to the hosts file on the Spiceworks server and uncomment the IPV4 localhost entry, but leaving the IPV6 entry commented out. Dcom Was Unable To Communicate With The Computer 10009 Server 2008 more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed
Friday, January 29, 2010 3:29 PM 0 Sign in to vote Any update? Check This Out Download proper MPS Report tool from the website below. The fix from Jez above was also the one we ended up using. For your convenience, I have created a workspace for you. Dcom Was Unable To Communicate With The Computer 22.214.171.124 Using Any Of The Configured Protocols
Reply Winston says: August 23, 2011 at 1:17 am you need to find out the process who is always trying to send out DCOM request where the target server doesn't exists Server 2008 R2 DC. Same boat as you guys, nothing in AD and DNS. Source 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
In the same article (comments section from the blog team), it's suggested to run tools like Network Monitor and Process Monitor, look at which process keeps sending failured RPC requests to Dcom Was Unable To Communicate With The Computer 10028 Cluster 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 simulation with kinetic friction, weird results Can a mathematician review my t-shirt design?
When I tried to connect to the services console on the remote, access was denied… And then I found the issue: There was a HOST(A) record on the DNS, but the There is a problem accessing the COM Service on a remote computer. b. Dcom Was Unable To Communicate With The Computer Exchange We use OpenDNS servers as forwarders on all of our servers and have for sometime.
Check the system to determine whether the firewall is blocking the remote connection. I am running windows Server 2008 R2 and have never used LabTech. Unfortunately, this means opening common ports like TCP/135, TCP/139 but also a range of dynamic ports that cannot easily be defined and start at 1025. have a peek here Edmund Thursday, June 21, 2012 11:53 AM 0 Sign in to vote I don't think it's a config problem...unless three dozen Microsoft articles are also wrong.
Cheers! Edited by Broxigar1983 Tuesday, July 17, 2012 3:59 AM Tuesday, July 17, 2012 3:55 AM 0 Sign in to vote We also have the same problem with the DCOM error message Generated Thu, 22 Dec 2016 02:38:58 GMT by s_ac16 (squid/3.5.20) Home "DCOM was unable to communicate with the computer 126.96.36.199 by Ronny N. May 23, 2013 at 7:58 UTC maybe rename your current hosts file and create a new one from a freshly installed Windows box and paste it in and see if there
Our other two domain controllers have this same information in their registry but do not show this error. –Wayne In Yak Jun 15 '15 at 13:55 Why don't you Or not connected through VPN onto the local network. Anyone else agree? Dave Thursday, January 19, 2012 8:05 PM 0 Sign in to vote I'm also having this issue, however it's for our ISP's DNS servers.
From your description, I understand that the Event error 10009 stating “DCOM was unable to communicate with the computer %1 using any of the configured protocols” is received on the new For example, if the IP of the server is 192.168.1.2, the text box should read: localsubnet,192.168.1.2. I've got a Server 2008 R2 lab at home (domain controller, exchange, web, dev, etc...) and I do not use LabTech. This error indicates that Lansweeper was unable to scan the client machine, but does not point to an underlying issue with your server or Lansweeper installation.
Friday, February 08, 2013 4:46 PM 0 Sign in to vote Hi there. Click OK. 8. You have the logs. Why would our DC being trying to contact network equipment via DCOM?
Your cache administrator is webmaster. Both claim every test passed. Scenario 3: Even though the TCP connection to remote server has no any problem, but if the communication of RPC authentication gets problem, we may get the error status code like It does give the reason of the DCOM attempts, but explains you what is triggering the DCOM call and gives tips on getting rid of it.