There are a lot of threads about this issue, but none ever seem to come to any resolution. I'm running a Server 2003 forest with a single domain. I've added a new 2008 Core domain controller in preparation for raising the functional level. DNS is integrated
with AD.
The problem is that with two configured DNS forwarders (provided by my ISP) I get frequent critical errors in the event log:
DCOM was unable to communicate the computer x.x.x.x using any of the configured protocols.
The fundamental problem is that something on this DC is trying to talk to remote DNS servers using DCOM and, of course, the machines aren't responding (assuming the communication attempt even makes it past the firewall). Another weird thing is that I also
continue to get these errors about forwarders that aren't listed anymore. I temporarily added 8.8.8.8 and 8.8.4.4 just to see what would happen, and they failed as well, but it's been hours (and a dns service stop/start) since I removed them and I'm
still getting errors about DCOM trying to connect to them.
This doesn't appear to be affecting anything negatively and this appears to not be affecting another 2008 Core box I just set up and promoted a few hours ago. Lookups work fine from any DC and dcdiag /test:dns /e only shows inconsequential warnings about missing AAAA records. I've tried using dcomcnfg on another machine to check dcom properties on the affected Server Core DC but I just get an error saying the component has been disabled with error code '80004027'.
I pulled the guid from the event details and tried to search the affected machine's registry, but connecting a network registry only gives HKLM and HKU and I believe you need the HKCR branch for that sort of information.
EDIT: sorry, didn't realize regedit was part of the limited core gui. It turns out the clsid throwing the error belongs to oleres.dll
Anybody have any suggestions?