Share via

DCOM Errors External Forwarders

Question

Thursday, May 21, 2020 8:22 PM

i have a .local domain

NIC card:

ipv4 dns uses ip of server (dc) and secondary dc. not using 127.0.0.1
ipv6 dns uses ::1

This is a Windows Server 2016 Standard

DNS server uses both ipv4 & ipv6 interfaces

DNS server forwarders are set to use google and ISP

My question is, can I fix the dcom errors when dcdiag runs it fails syslog due to not being able to resolve the external dns forwarders?Or do i have to use root hints? I read those are slower

All replies (3)

Wednesday, May 27, 2020 2:13 AM âś…Answered

Hi ,

Sorry for the delayed response. I did not receive the email alert.

When you run "dcdiag /test:dns" tests forwarders by communicating through RPC protocol and DCOM. 

You might see events like:

DCOM errors 10009 in the event logs (DCOM was unable to communicate with the computer X.X.X.X using any of the configured protocols).

If the Forwarded server is responding fine to nslookup, this error can be ignored. You can disregard this warning if the DNS server is a BIND or other non-Microsoft DNS server.

For your reference:

Domain Controller Diagnostics Tool (dcdiag.exe)

Best Regards,

Candy

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]   

Friday, May 22, 2020 5:51 AM

Hi ,

Could you please post the Dcdiag result for us to know more details? 

In addition to this dcdiag error, are there any problem in your actual environment? Could you nslookup external records? Like nslookup google.com?

Best Regards,

Candy

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]   

Friday, May 22, 2020 3:56 PM

No problems, just our monitoring software (connectwise automate [formally labtech] and connectwise manage) is creating tickets for failure. Lookups work fine

Starting test: SystemLog
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 05/21/2020   16:23:22
            Event String:
            DCOM was unable to communicate with the computer 207.172.3.8 using any of the configured protocols; requested by PID      e78 (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 05/21/2020   16:23:43
            Event String:
            DCOM was unable to communicate with the computer 207.172.3.9 using any of the configured protocols; requested by PID      e78 (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 05/21/2020   16:24:04
            Event String:
            DCOM was unable to communicate with the computer 8.8.4.4 using any of the configured protocols; requested by PID      e78 (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 05/21/2020   16:24:25
            Event String:
            DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID      e78 (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 05/21/2020   16:24:48
            Event String:
            DCOM was unable to communicate with the computer 207.172.3.8 using any of the configured protocols; requested by PID     1a8c (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 05/21/2020   16:25:09
            Event String:
            DCOM was unable to communicate with the computer 207.172.3.9 using any of the configured protocols; requested by PID     1a8c (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 05/21/2020   16:25:30
            Event String:
            DCOM was unable to communicate with the computer 8.8.4.4 using any of the configured protocols; requested by PID     1a8c (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 05/21/2020   16:25:52
            Event String:
            DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1a8c (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x00002720
            Time Generated: 05/21/2020   16:51:28
            Event String:
            The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
         ......................... DC1 failed test SystemLog