Improve company productivity with a Business Account.Sign Up

x
?
Solved

DCOM was unable to communicate with the computer on SBS 2008

Posted on 2011-02-26
4
Medium Priority
?
1,240 Views
Last Modified: 2013-12-12
On a SBS 2008 at one of my customers I continually get this event log

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 26/02/2011 7:41:55 AM
Event ID: 10009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SBSERVER.kargomax.local
Description:
DCOM was unable to communicate with the computer <IP Address> using any of the
configured protocols.

I see that this started to happen on Feb 15th and now the events are generated
every few seconds with most the IP's addresses in the network

Any ideas what to look for?
0
Comment
Question by:Gerhardpet
  • 2
4 Comments
 
LVL 22

Expert Comment

by:Larry Struckmeyer MVP
ID: 34987508
From the SBS Official Blog: (http://blogs.technet.com/b/sbs/archive/2008/08/26/known-post-installation-event-errors-in-sbs-2008-and-how-to-resolve-them.aspx)

Problem: The DCOM event id 10009 will occur when a client workstation has a miss-configured firewall or other issues affecting its network communications within the domain, for example if the workstation is not managed by an SBS GPO. In this scenario, the DCOM event 10009 will happen repeatedly, potentially hundreds per day.

Were the stations on this SBS added with the //connect wizard, and are they in the correct OU, My Business - Computers - SBS Computers?
0
 
LVL 1

Accepted Solution

by:
Gerhardpet earned 0 total points
ID: 35001028
I found the problem...the event is generated by the monitoring tool I'm using which is normal.
0
 
LVL 1

Author Closing Comment

by:Gerhardpet
ID: 35042669
I found the problem...the event is generated by the monitoring tool I'm using which is normal.
0
 

Expert Comment

by:bluemarbletech
ID: 39713898
I had the same issue with a client's 2011 SBS, the System log showed Event 1009 every 30 minutes for two computers in the domain. It did not seem to affect anything but the log was full of these errors. While dealing with some other issues I found the solution, which was pretty simple. No reg hacks, no port changes.

The two computers showing in the logs had recently been upgraded to Windows 7. They were both wiped clean and then had Win 7 pro reinstalled from scratch, and then rejoined to the domain with new computer names. However, both still showed in AD under the old names as well as the new ones. My guess is they were not dis-joined from the domain before the upgrade. The new computer names showed in AD under SBS Computers, but the old names were still showing under the Computers OU.

In my case the answer was as simple as deleting the old computer names out of AD. The new names stayed put and the errors which were filling up the logs every half hour stopped completely.

Hope this helps in any way.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

587 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