[SOLUTION] DCOM was unable to communicate with the computer

DCOM was unable to communicate with the computer

I have an error on my server saying:

DCOM was unable to communicate with the computer wscremote2.westminster.local using any of the configured protocols.

I know that this is the case because that computer simply does not exist. How do I get the server to stop giving me the error?

DC are as I would expect them. wscremote2 does not exist on that list, nor does it exist in FSMO.
The results of dcdiag:

C:\Windows\system32>dcdiag

Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = WSCALFS
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: WESTMINSTER\WSCALFS
Starting test: Connectivity
......................... WSCALFS passed test Connectivity

Doing primary tests

Testing server: WESTMINSTER\WSCALFS
Starting test: Advertising
......................... WSCALFS passed test Advertising
Starting test: FrsEvent
......................... WSCALFS passed test FrsEvent
Starting test: DFSREvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... WSCALFS failed test DFSREvent
Starting test: SysVolCheck
......................... WSCALFS passed test SysVolCheck
Starting test: KccEvent
......................... WSCALFS passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... WSCALFS passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... WSCALFS passed test MachineAccount
Starting test: NCSecDesc
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=westminster,DC=local
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=DomainDnsZones,DC=westminster,DC=local
......................... WSCALFS failed test NCSecDesc
Starting test: NetLogons
......................... WSCALFS passed test NetLogons
Starting test: ObjectsReplicated
......................... WSCALFS passed test ObjectsReplicated
Starting test: Replications
......................... WSCALFS passed test Replications
Starting test: RidManager
......................... WSCALFS passed test RidManager
Starting test: Services
......................... WSCALFS passed test Services
Starting test: SystemLog
An Error Event occurred. EventID: 0xC00010DF
Time Generated: 04/05/2017 11:26:55
Event String:
A duplicate name has been detected on the TCP network. The IP addre
ss of the computer that sent the message is in the data. Use nbtstat -n in a com
mand window to see which name is in the Conflict state.
An Error Event occurred. EventID: 0xC00010DF
Time Generated: 04/05/2017 11:38:55
Event String:
A duplicate name has been detected on the TCP network. The IP addre
ss of the computer that sent the message is in the data. Use nbtstat -n in a com
mand window to see which name is in the Conflict state.
An Error Event occurred. EventID: 0xC00010DF
Time Generated: 04/05/2017 11:50:35
Event String:
A duplicate name has been detected on the TCP network. The IP addre
ss of the computer that sent the message is in the data. Use nbtstat -n in a com
mand window to see which name is in the Conflict state.
An Error Event occurred. EventID: 0xC00010DF
Time Generated: 04/05/2017 11:50:55
Event String:
A duplicate name has been detected on the TCP network. The IP addre
ss of the computer that sent the message is in the data. Use nbtstat -n in a com
mand window to see which name is in the Conflict state.
......................... WSCALFS failed test SystemLog
Starting test: VerifyReferences
......................... WSCALFS passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation

Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation

Running partition tests on : westminster
Starting test: CheckSDRefDom
......................... westminster passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... westminster passed test CrossRefValidation

Running enterprise tests on : westminster.local
Starting test: LocatorCheck
......................... westminster.local passed test LocatorCheck
Starting test: Intersite
......................... westminster.local passed test Intersite

I also do not see anything in DNS pointing to that server.

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.

LVL 17

Jason CrawfordTransport NinjaCommented: 2017-04-04

What DNS server(s) do you have configured on that server? Are you using something like 8.8.8.8 or your ISPs DNS server WAN IP? If so, the error makes sense since it's telling you a public DNS server can't resolve a .local TLD.

aclaus225Author Commented: 2017-04-05

That computer is using internal DNS. I am wondering why this computer is looking for that computer and how to stop it from looking, since that computer is not in my network anymore. Where on my W2k8 server would I go to remove this from looking for wsc2remote which does not exist anymore?

I think related to this I also have this error: Certificate enrollment for Local system failed to enroll for a DomainController certificate from wscremote2.westminster.local\wscremote2 (The RPC server is unavailable. 0x800706ba (WIN32: 1722)).

wscremote2 is no longer a computer in my network. What do I need to do to remedy this problem?

Jason CrawfordTransport NinjaCommented: 2017-04-05

If that server was a Domain Controller you should follow this Technet article:

https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

The server at one time was a domain controller, I guess, but it does not appear in AD Users and Computers anywhere that I can find.

Run this command from an existing Domain Controller:

netdom query dc

Followed by

netdom query fsmo

Look in DNS for any lingering DNS records, check the Domain Controllers OU in ADUC. Run a dcdiag from an elevated command prompt.

It sounds like there was/is an Enterprise CA in your network. Do you know if it was ever replaced or are you now operating without an Enterprise CA?

I found an article that may explain why you're receiving these errors:

http://www.petenetlive.com/KB/Article/0000473

But before you do that you may want to try disabling Windows Firewall as a troubleshooting step and see what happens.

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

DCOM was unable to communicate with the computer

Who is Participating?