Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

DCOM Event 10009 on Server2003

Posted on 2010-09-03
3
Medium Priority
?
677 Views
Last Modified: 2013-11-21
My one and only DC which runs Server 2003 is giving me a DCOM error 10009 stating: DCOM was unable to communicate with computer XXX.XXX.1.1 using any of the configured protocols.  The computer it is trying to reach is private interface of my firewall.  Nothing has changed that I am aware of and if it has, wouldn't it be on the firewall or not?
SM
0
Comment
Question by:smantz
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 2

Assisted Solution

by:edwarneke
edwarneke earned 600 total points
ID: 33600071
I ran into an issue where I was getting a similar error. My symptoms and reason for looking at this was that I wasn't receiving mail from specific domains(1and1 hosting, the mail server was mx00.perfora.net), yet most were coming through fine.

What I found was that my internal DNS(Windows server 2003 DNS) was not configured correctly. I didn't have an A record for our MX (mail.organisation.com). Once I entered an A record this error went away and I could receive emails from the problem domain.

Are there any other symptoms you're noticing besides this error?
0
 

Author Comment

by:smantz
ID: 33601079
No and this only pops up occasionally.  I did see that my DNS forwarding is set to the gateway.  This is for some DNS proxy so, maybe that has something to do with that.  Thoughts?
0
 
LVL 11

Accepted Solution

by:
farjadarshad earned 1400 total points
ID: 33609470
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
This is the first one of a series of articles I’ll be writing to address technical issues that are always referred to as network problems. The network boundaries have changed, therefore having an understanding of how each piece in the network  puzzl…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Suggested Courses

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question