Link to home
Start Free TrialLog in
Avatar of BeGentleWithMe-INeedHelp
BeGentleWithMe-INeedHelpFlag for United States of America

asked on

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?
SOLUTION
Avatar of Nik
Nik
Flag of Croatia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of BeGentleWithMe-INeedHelp

ASKER

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?
and if it's tombstoned (the domain doesn't want it anymore), why woudl the server be wasting time trying to reach it
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.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I uncommented the 127.0.0.1  localhost in the hosts file and deleted that machine.  I'll reboot later.