Experts,\n\nRunning Windows Server 2003 SP1. Running about 10 small public web sites on\nit. This is a single-server pointing to itself for DNS and running Active\nDirectory. The AD zone is standard primary with "Secure and Non-secure"\nupdates set to 'Yes'. All other zones (for the 10 small public web sites)\nhave dynamic updates turned "off". None of those have name servers pointing\nto my ISP. They do however use the Notify feature to transfer to them a\nsecondary zone. In DNS, under Forwarders, are the two IP addresses for my\nISP's DNS server in question. They were also entered into the properties of\nthe Default Virtual SMTP Server so that Exchange running on this box could\ndo reverse lookups on the domains of incoming mail but I have removed those.\nThe event ID error below basically indicates my server cannot communicate\nwith my ISP server. I can understand that problems sometimes happens, as my\nISP is hosting my secondary zones for the 10 small public web sites. But\nwhy is the server trying to communicate with it using DCOM? I would assume\nit would only try to communicate with it using standard tcp over port 53\n(zone transfer). To me that's just plain weird. I have been over every\nsquare inch of this server. DCdiag results also keep telling me I'm using\nthe two ISP's DNS servers mentioned but I cannot see how/where I am doing\nthat anywhere within the GUI. The Preferred and Alternate DNS servers for\nthis server points to itself under network properties.\n\nEvent Type: Error\nEvent Source: DCOM\nEvent Category: None\nEvent ID: 10009\nDate: 12/2/2005\nTime: 8:35:30 AM\nUser: N/A\nComputer: EBIZ-GATE\nDescription:\nDCOM was unable to communicate with the computer <ISP DNS> using any of the\nconfigured protocols.