We are stumped as to why. Here is event from System log: Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 10/3/2012 10:53:37 AM Event ID: 10009 Task Category: Thank You,Timothy Garner timothy.garner-it Full Member Posts: 106Joined: Wed Aug 24, 2011 12:05 pm Private message Top Re: DCOM alerts in DNS servers following LT2012 install by glarsen.tuscanydrilling » Wed Art Bunch posted Jul 11, 2016 Do i need windows 8 security... Source
Your servers just don't have access to your ISP's or Google's DNS server through the DCOM protocols (probably due to the firewall restrictions mentioned earlier in this thread), where as if That way at least they are not hitting my server for udp > port 53 DNS queries, and only instead go to my server over over port > 80 for the Reply Aamer says: June 5, 2012 at 12:23 pm We have these DCOM 10009 Events filling up event logs after removing a server from the network. I can ping and resolve these addresses. my site
Reply Brian says: April 4, 2013 at 6:00 am All my DCOM error messages are coming from Non-windows machines, anyone have this problem: All events are logged on the domain controller: After that, click Next, when the "Select the diagnostics you want to run" page appears, select "General", “Internet and Networking”,“Server Components”, click Next. 3. 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 There is a problem accessing the COM Service on a remote computer.
We are getting the same error with DCOM trying to communicate with the external dns servers. To chat live with a Partner Support Consultant, complete the form below and click Connect. I hope this helps everyone. -J 1 Pimiento OP alexsan Aug 13, 2015 at 6:24 UTC So what would be your suggestion then? Dcom Was Unable To Communicate With The Computer Dcdiag Expand Forest: Domain.local, Domains, Domain.local and select Group Policy Objects. (Replace Domain.local with your domain) 4.
I have at least one client server that is receiving DCOM 10009 errors, and the IP addresses are of the server's external DNS forwarders. Dcom Was Unable To Communicate With The Computer Domain.local Using Any Of The Configured Protocols Java Programming Languages-Other Introduction to VisualVM (Part 1) Video by: Amitkumar This tutorial will introduce the viewer to VisualVM for the Java platform application. After collecting all log files, choose "Save the results", choose a folder to save
Covered by US Patent. Dcom Was Unable To Communicate With The Computer Windows 2012 I also ran the "dcdiag /test:dns /dnsforwarders" command at a couple clients. After collecting all log files, choose "Save the results", choose a folder to save
Thursday, July 19, 2012 3:35 PM 2 Sign in to vote I'm also seeing the same dcom errors when N-Able is trying to connect to machines that are no longer on find more info The DC DIAG tool will write the DCOM errors to the event log. Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols Server 2008 Spin Guest Experts, I have almost got this figured out! Dcom Was Unable To Communicate With The Computer 10009 Server 2008 I would like to stop these errors from appearing.
Member Login Remember Me Forgot your password? this contact form Member Posts: 77Joined: Tue Apr 17, 2012 6:24 pmLocation: Adelaide Private messageWebsite Top Re: DCOM alerts in DNS servers following LT2012 install by timothy.garner-it » Mon Jul 16, 2012 4:37 Additional: Extended info dump from one of the events on a SBS2011 server
I have tested this on both of our DNS servers and all DCOM 10009 errors disappeared. So, a Microsoft bug is found by Labtech, only to have Labtech recursively spread the bug to the point it crashes itself...awesome. I have a couple of other servers with the same issue but they are not SBS Servers. have a peek here I used to get a lot of these, mostly for desktops, but some servers.
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 Proposed as answer by alexpking Wednesday, July 18, Dcom Was Unable To Communicate With The Computer 10028 Cluster Join the community of 500,000 technology professionals and ask your questions. The college in 'Electoral College' Does "Excuse him." make sense?
In the text box labeled Allow unsolicited incoming messages from these IP addresses, add the IP (IPv4) of the server. Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser. Anyone have any luck fixing this? Dcom Was Unable To Communicate With The Computer 18.104.22.168 Using Any Of The Configured Protocols Your servers just don't have access to your ISP's or Google's DNS server through the DCOM protocols (probably due to the firewall restrictions mentioned earlier in this thread), where as if
Privacy statement © 2016 Microsoft. So, the IP addresses of some of the workstations were correlated to the incorrect (old) host names. After removing it from Server Manager, this error (Event ID 10028) no longer occurs. Check This Out In certain cases, the settings of the TCP/IP protocol can affect the network traffic.
Browse other questions tagged domain-controller dcom or ask your own question. Discussion in 'Active Directory' started by Spin, Dec 9, 2005. We use LabTech too. There is a problem accessing the COM Service on a remote computer.
Microsoft Customer Support Microsoft Community Forums TechCenter Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 Tuesday, July 31, 2012 9:33 PM 0 Sign in to vote I'm also seeing the same dcom errors when N-Able is trying to connect to machines that are no longer on If enough of us complain, maybe they will acknowledge this.