windows-server-2008-r2 dcom share|improve this question asked Aug 14 '13 at 20:18 josh 28127 Do the error messages follow any sort of pattern? –Mitch May 4 '15 at 18:58 add Event id 10009 kept being recorded in the domain controller logs. x 12 Anonymous In my case, this started happening after installing HP Insight Manager. I also enabled dynamic updates for the DNS-Zones, which was disabled by default on our SBS 2008. his comment is here
Click OK.8. If the workstation is on a different subnet than the SBS server and it is running Windows XP SP2 or higher, the firewall exceptions provided by the SBS group policies will If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. 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 https://blogs.msdn.microsoft.com/asiatech/2010/03/15/how-to-troubleshoot-dcom-10009-error-logged-in-system-event/
Click OK. 8. Follow the extra steps below to properly monitor XP SP2 (or higher) machines running in the SBS domain on different subnets than the SBS server, and prevent the DCOM event ID Bayes regression: how is it done in comparison to standard regression? The jobs ran at 10 am and 4 pm and would fill the system log for about twenty minutes.
The network connections might not be configured properly. Another weird note is that it has a tendancy to stop for 10min or so randomly. 0 Chipotle OP BambiX Jun 18, 2013 at 3:02 UTC what apps If the firewall exception rule is not enabled, in the details pane click Enable rule, and then scroll horizontally to confirm that the protocol is TCP and the LocalPort is 135. https://social.technet.microsoft.com/Forums/office/en-US/fc2b104d-2e74-4b2c-8a21-f1a69eeac30a/recurring-event-id-10009-microsoftwindowsdistributedcom?forum=winserverManagement Depending on your firewall solution this might be implemented or might require opening several ports.
x 6 Anonymous My issue was related to a mapped printer to a no longer existing PC. Dcom Was Unable To Communicate With The Computer 18.104.22.168 Using Any Of The Configured Protocols. Well hey, keep us updated, and let us know if you figure out the issue. Concepts to understand: What is DCOM? In the console tree of the Component Services Administrative tool, right-click the computer on which you want to configure the protocol, to bring up the context menu. 3.
x 592 Anonymous In my case, it was caused by an HP 1012 printer that was pointed to a computer no longer in the organization. https://community.spiceworks.com/topic/349338-dcom-10009-error Once you do that your server will report into the console and provide the hardware information on the Network/Computers tab. Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols. 10009 You can check with application team, or run Network Monitor and Process Monitor, look at which process keeps sending failured RPC requests. Event Id 10009 Dcom Was Unable To Communicate With The Computer For scenario 3: Need capture more resources like Network traffic, or even iDNA trace to further investigate how this failure happens.
Eventualy, I found that the premissions on the server object were changed in DCOMcnfg. http://netfiscal.com/dcom-was/event-10009-dcom-was-unable-to-communicate-sbs-2008.html At the command prompt, type ping, followed by a space and the remote computer name, and then press ENTER. Right-click the Windows SBS Client – Windows XP Policy and click Edit. 5. I guess I'll need to find the application that seems to be making calls to the non-existant server name. Dcom Was Unable To Communicate With The Computer No Longer Exists
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 Dcom Was Unable To Communicate With The Computer Dcdiag No, create an account now. Follwed the advice by Adam Lewandowski (see below), however I was still getting it for 1 specific machine.
He had a Lexmark X5 printer mapped to another user's PC from the old workplace. 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 i.e. Dcom Was Unable To Communicate With The Computer Dns Forwarder I searched on Google and found that I am not the only one who had this problem.
What does the code mean and how to troubleshoot the problem? Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? On the Start menu, point to Programs, Administrative Tools, and then click Component Services. 2. http://netfiscal.com/dcom-was/event-10009-dcom-was-unable-to-communicate.html Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password?
DNS records of the old workstations were still present. What does IPconfig /all say in terms of IP addresses on this server? Log Name: system Source: DistributedCOM Event ID: 10009 Level: Error User: N/A Here is the full situation, a distributor has brought his laptop to this site, from another domain, and it Browse other questions tagged windows-server-2008-r2 dcom or ask your own question.
See T774368. So the server tried to contact the computer with a wrong name and the result of this was the error. Review available Extended RPC Error information for this event in Event Viewer To review available Extended RPC Error information for this event in Event Viewer: Click Start, and then click Run. It's really annoying seeing thousands of errors a day in the event log.
I think that in this particular case event 10009 can be ignored.