SBS 2011 standard - log is filled with loads of erro 10009 DCOM was unable to communicate with the computer [name] using any of the configured protocols

There's a machine that is out in the field these days / hasn't been on our SBS 2011 network for months now (a year + maybe).

I'm getting loads of DCOM was unable to communicate with the computer x.x.x.x using any of the configured protocols errors in the event log.

some web pages for this say to delete the computer from AD. But it might be back at some point.  Is there a way to have dcom not try to communicate / stop logging these?

Or after x months, DCOM wants to talk to machines that aren't on the LAN?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NikSystems SpecialistCommented:
You are getting this errors on the SBS server for one or more computers?

Have you seen this article?
http://community.spiceworks.com/topic/288546-dcom-was-unable-to-communicate-with-the-computer-64-99-64-32
David Johnson, CD, MVPRetiredCommented:
after 180 days it is probably tombstoned and even if brought back in it will not be able to authenticate.
BeGentleWithMe-INeedHelpAuthor Commented:
david - really!?  what then? the laptop still thinks its part of the domain and the domain says no?  

still have to join the laptop to a workgroup then join back to the domain?
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

BeGentleWithMe-INeedHelpAuthor Commented:
and if it's tombstoned (the domain doesn't want it anymore), why woudl the server be wasting time trying to reach it
R. Andrew KoffronownerCommented:
you have multiple questions on SBS2011, it's highly likely that there's a root cause, that's cascading if these are all the same server.
R. Andrew KoffronownerCommented:
after looking this over again, I think David is probably right, you'll most likely need to log into the local admin on the laptop, and change it to a workgroup, then delte the account from the AD Users and Computers,  than rejoin the domain.

deleting the account from the AD should end the error in your logs,

this is probably just a coincidental error and "probably" not related to your other questions,

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BeGentleWithMe-INeedHelpAuthor Commented:
I uncommented the 127.0.0.1  localhost in the hosts file and deleted that machine.  I'll reboot later.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.