SBS2008 DistributedCom error

Hi

On my SBS2008 server I have hundreds of System Errors in the event viewer, all saying the same thing.

"DCOM was unable to communicate with the computer PC.domain.local using any of the configured protocols."

Windows Firewall is OFF.

I'm not even sure if this PC is even on the domain anymore, is there a way I can check when it was last connected to the network?
LVL 1
hongeditAsked:
Who is Participating?
 
Larry Struckmeyer MVPConnect With a Mentor Commented:
VPN is old school..... RWW/RWA is the best way to connect remote machines, but you will need a landing point, such as an RDS/TS server or a desktop for them to take control of.  No experience with VPN's and the error you describe, as we don't allow VPN... congests bandwidth and allows unmanaged computers direct access to our server... ugh.

If you produce the senerio where the SBS expects stationX to be connected, and stationX is not connected, the error is what happens.  Best way to stop the pain is to stop hitting oneself.
0
 
Larry Struckmeyer MVPCommented:
Hmmm... should be easy enough to see if the station is still thought to be part of the domain... Server Mangment lists them, but it gets that info from ADUC, where you can check.  If you find it in Server Managment, and you are sure it should not be, just remove it using the wizard on the right.

What happens if you ping it by name, then by IP address?
0
 
hongeditAuthor Commented:
It doesnt respond by name or IP, but it could well be becuase it is off.

It's still part of the domain but I have a feeling the PC was one that we chucked ages ago due to a hardware error.

Anyway to check last domain contact?
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Larry Struckmeyer MVPCommented:
Hmmm... you must have a LOT more stations in your SBS domain than I am used to.  I know the names of each system and where they are becuase the nameing conventions help me figure it out and becuase the documentation says that WKS01 is currently used by Sally.

But, afaik, logons are by user, not by station.
0
 
hongeditAuthor Commented:
not really, they have about 10 stations total, but naming conventions are all over the place, making it very hard to pinpoint.

maybe what I can do is remove all traces of this workstation from DNS and see if it reappears after a week or two.

What is that error about anyway?
0
 
Larry Struckmeyer MVPCommented:
Unable to communicate.... = can't find it.
0
 
hongeditAuthor Commented:
I reckon its an old PC.

Will removing it from SBSComputers in ADUC fix it?
0
 
Larry Struckmeyer MVPCommented:
As in all things SBS, use the Wizards.. in this case, from the Server Manager console.
0
 
hongeditAuthor Commented:
I was not aware there was a Wizard for removing a computer object?
0
 
Larry Struckmeyer MVPCommented:
In 2008/2011 it is under Network, Computers Tab,  highlight a system, on the right - Remove.
0
 
hongeditAuthor Commented:
Ok, removed.

I saved and cleared the log, will check back in 1 or 2 days to see if it still comes up.
0
 
hongeditAuthor Commented:
Well, I cannot see any errors for that machine anymore.

However, a lot of other machines are now showing instead - mostly laptops that spend the majority of time offsite.

Some of these are not even domain-joined.

Is it safe just to ignore these errors, and/or can I get rid of them somehow? I cant delete their computer objects becuase they are live machines, mostly which connect in via VPN.
0
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.

All Courses

From novice to tech pro — start learning today.