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. For scenario 3: Need capture more resources like Network traffic, or even iDNA trace to further investigate how this failure happens. It is a crazy issue. 0 LVL 29 Overall: Level 29 MS Legacy OS 6 Active Directory 5 Windows Server 2012 4 Message Active 3 days ago Expert Comment by:Randy They are all our networking gear: switches, routers, firewall, WAPs etc. have a peek at this web-site
The article is about migrating and non-existent computers but maybe its applicable in your migration. Can the product of two nonsymmetric matrices be symmetric? Validate Random Die Tippers What are these boxes mounted inline on each of the 3 phase wires of a high voltage power line in Miami? 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 http://www.lansweeper.com/kb/139/dcom-was-unable-to-communicate-with-the-computer.html
The machines are obviously not missing but maybe the entries are corrupted somehow. Graeme Edited by The Oracle Friday, April 27, 2012 10:14 AM Friday, April 27, 2012 10:13 AM 0 Sign in to vote I am receiving this error not even from a Proposed as answer by Skip47025B Wednesday, March 20, 2013 4:32 PM Unproposed as answer by Skip47025B Wednesday, March 20, 2013 4:32 PM Friday, March 15, 2013 7:05 PM 0 Sign in
Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser. There is a problem accessing the COM Service on a remote computer. DCOM errors (Event ID 1009) because it can't create an RPC connection to my DNS forwarder (OpenDNS)!?! Dcom Was Unable To Communicate With The Computer Dcdiag Click Start, click Run, type GPMC.MSC, and click OK. 2.
If the client machine is offline or firewalled, DCOM automatically logs an error in your server's Event Viewer. Dcom Was Unable To Communicate With The Computer Domain.local Using Any Of The Configured Protocols Join Now For immediate help use Live now! 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 Read More Here The DCOM error references the original name of the computer I gathered from.
Not sure why the DNS got the incorrect records. Wednesday, August 22, 2012 7:59 PM 3 Sign in to vote All LabTech users try this: Find the dctest.bat file in the \windows\ltsvc folder on the server and edit it so Dcom Was Unable To Communicate With The Computer Event Id 10009 When Node 3 was turned off (as Lawrence mentioned above), Server Manager will report Event ID 10028 at all other cluster nodes. 0 Message Author Comment by:jyoung127 ID: 408626562015-07-01 Unfortunately Dcom Was Unable To Communicate With The Computer 10009 Server 2008 All Rights Reserved Privacy & Terms
For your convenience, I have created a workspace for you. Check This Out We can verify it by ping
Thank you! Close Windows Firewall with Advanced Security Right mouse click and enable the rule Then to get the server to be able to query thename/model of theremote server enable the WMI You could do a group policy at the server to push out this policy to the machine in question. Source Command syntax: tracetcp.exe hostname:port Example: tracetcp.exe api.opendns.com:443) 0 Message Author Comment by:jyoung127 ID: 408711482015-07-07 NO issues with Tracert sorry for the delay response. 0 LVL 29 Overall: Level 29
For example, if the IP of the server is 192.168.1.2, the text box should read: localsubnet,192.168.1.2. Dcom Was Unable To Communicate With The Computer 10028 Cluster on Jan 7, 2013 at 8:59 UTC | Spiceworks Support 0Spice Down Next: Spiceworks User Accounts TECHNOLOGY IN THIS DISCUSSION Join the Community! 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.
Set the ActivationFailureLoggingLevel value in the registry key below to 2. For detailed information about the above steps, please refer to the following article: Event ID 10009 — COM Remote Service Availability http://technet.microsoft.com/en-us/library/cc774368(WS.10).aspx Does it work? The DCOM error references the original name of the computer I gathered from. Dcom Was Unable To Communicate With The Computer Exchange Go to the hosts file on the Spiceworks server and uncomment the IPV4 localhost entry, but leaving the IPV6 entry commented out, as in the screen shot below.
For security, COM+ network access is not enabled by default. 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 Resolution: To attempt to resolve configuration issues with the firewall try the following: Make sure to allow remote management exception. have a peek here Thanks, Edited by Skip47025B Wednesday, March 20, 2013 4:36 PM Wednesday, March 20, 2013 4:35 PM 0 Sign in to vote Anyone figure this out yet?
They are both online and responding, but I'm not sure why DCOM would be attempting to contact external DNS servers. A published paper stole my unpublished results from a science fair In what spot would the new Star Wars movie "Rogue One" go in the Machete Order? 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. The latest version is 7.5.00095. 9 Replies OP Best Answer Rob (Spiceworks) Jan 7, 2013 at 10:41 UTC Hi Ronny, We see this sometimes if your DNS server
You can install or repair the component on the local computer. 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 We use OpenDNS servers as forwarders on all of our servers and have for sometime.