Home > Unable To > Error 10009 Unable To Communicate With The Computer

Error 10009 Unable To Communicate With The Computer

Contents

I also have never used LabTech. Every search I've done points me to opening firewall settings for COM+ --the problem isn't the firewall settings (which I don't want to change), the problem is I don't want the Ensure that this firewall exception rule is enabled, and then scroll horizontally to confirm that the protocol is TCP and the LocalPort is 135. Ideally we don't want these messages appearing the event logs.Any ideas to suppress?Thanks 1360-324165-1709393 Back to top Kailas S Members #2 Kailas S 817 posts Posted 22 January 2013 - 03:13 http://csimonitoring.com/unable-to/error-10009-dcom-windows-xp.php

This problem was first reported in 2012. If you do not have any of the connection-oriented protocols in the list, click Add to bring up Select DCOM protocol and endpoint dialog box. 7. At this time, there are two options. Right-click the Windows SBS Client – Windows XP Policy and click Edit. 5.

Error 10009 Dcom Was Unable To Communicate With The Computer

Reply Salomon says: July 3, 2013 at 12:53 pm Good point to start. Thanks, Bernie 0 Sonora OP LiamK May 13, 2015 at 8:20 UTC You have 8.8.8.8 as a dns server, that should be a forwarder not a dns server x 8 Eric B The user is working at a new location. We also use LabTech like the last couple of people have mentioned.

  1. Quoting a LabTech Tech's response: "Greg, This issue is due to the labtech service running a DC Diag to ensure your AD environment is healthy and following MSFT's best practices.
  2. Friday, January 04, 2013 6:27 AM 0 Sign in to vote IIRC Labtech's answer was "no it won't be pushed".
  3. I found this MS article(http://support.microsoft.com/kb/957713), but I am curious if you heard anything back from LT.
  4. I revoked the certifiacate and the error is gone.
  5. I have searched and searched and cannot find the answer.
  6. We use LabTech too.
  7. I'm not alone - ANYone find a way to stop my bleepin' SBS 2011 server from attempting DCOM connections to nonexistent (or, Linux) boxes?
  8. We had a XP PC with an attached HP Laserjet P1505 printer.

I had this error on a Windows XP SP2 machine after I installed the driver and tool package for the connected printer HP1320n. 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 Server 2008 R2 DC. Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols 10028 Removing the printer removed the problem.

Click the Default Protocols tab. 5. Dcom Was Unable To Communicate With The Computer 10009 Server 2008 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. 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 For more information about Extended RPC Error information and how to interpret it, see Obtaining Extended RPC Error Information (http://go.microsoft.com/fwlink/?LinkId=105593).

I removed the printers and the ports and the problem was solved. Dcom Was Unable To Communicate With The Computer Event Id 10009 Make note of the IPv4 address listed. 7. The only difference between the 2 configurations that I see is that one has the 3 static DNS forwarders configured and the other is using just the Root Hints. Me, I wanted to be a sysadmin.

Dcom Was Unable To Communicate With The Computer 10009 Server 2008

x 2 Anonymous We tracked this error back to a pair of scheduled discovery tasks for N-Able (a remote management and monitoring software). http://www.expta.com/2011/07/fix-for-dcom-10009-errors-in-exchange.html When I double click on a message, I see all the message events and the tree. Error 10009 Dcom Was Unable To Communicate With The Computer For example, if the IP of the server is 192.168.1.2, the text box should read: localsubnet,192.168.1.2. 10009 Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols I changed it back to Local and Remote Execution and Activation and the problem was solved.

Is it a configuration problem or a bug do you think? see here Right-click the Windows SBS Client - Windows XP Policy and click Edit. 5. could you pls clarify why this access would be required? This link helped me find and delete them. Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols Server 2008

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 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole Reboot the machine hosting the Lansweeper Server service. The (portable) machine may have just been switched off, or the owner may be on the road at the given moment. this page To resolve this problem: Ensure that the remote computer is online. (remainder left out) From my side I can add that the same error is also occurring in mass on our

Reply Jens says: July 1, 2016 at 8:11 am Hello all, i was having this error - DCOM trying to contact a non-existent server - more specifically, a server that i Dcom Was Unable To Communicate With The Computer Domain.local Using Any Of The Configured Protocols Brad Wednesday, February 22, 2012 7:05 PM 0 Sign in to vote That regedit proposed above really didn't do much, and perhaps made my situation worse, because now I have no For security, COM+ network access is not enabled by default.

Reply Turbocutt says: August 3, 2015 at 2:30 am Hello guys, I have a same issue "DCOM was unable to communicate with the computer "Computer_name" using any of the configured protocol"

The only difference for me is that I know what the "computers" are. This article has some good info about Root hints and forwarders, http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/16c8211b-eaea-4c78-beea-4356860... I hope this helps everyone. -J I'm also seeing the same dcom errors when N-Able is trying to connect to machines that are no longer on the network. Dcom Was Unable To Communicate With The Computer Dns Forwarder Topology and the 2016 Nobel Prize in Physics Why do most log files use plain text rather than a binary format?

Reply Scott5297 says: January 9, 2014 at 9:25 am I had this on a SBS 2011 domain. Check the Registry under HKEY Local Machine/Software/Microsoft/RPC/DCOM Protocols for the list of RPC protocol sequences. I found the error with "Process Explorer" from Sysinternals. Get More Info b.

I'm hoping they will have some type of solution to this rather than having to modify their batch file and re-deploying it to our remote sites. An example of English, please! After upgrading the workstations to Windows 7 and renaming them, the DNS records got mixed up. Check the network connections.

Which makes sense because according to a couple Technet articles the forwarders actually have to time out before the root hints kick in, and if there's no forwarders configured then the Is there (or does something exist that is close to) a theory of arguments? DCOM 10009 communicating to XenApp Servers Started by Nicky Crancher , 22 January 2013 - 02:21 PM Login to Reply 2 replies to this topic Nicky Crancher Members #1 Nicky Crancher Removing the forwarders from DNS seems to have cleared the errors when running the command from above, and the test runs much faster.

Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After uninstalling the driver, the errors stopped.