<div>
Are you running and Symantec anti-virus or firewall products? &nbsp;I've seen issues where they can cause issues and throw strange errors. &nbsp;<br />
<br />
Is there anything else in the log that would point to another issue at the same time these arrors are happening?
</div>


Are you running and Symantec anti-virus or firewall products?  I've seen issues where they can cause issues and throw strange errors.  

Is there anything else in the log that would point to another issue at the same time these arrors are happening?

<div>
We are using Sophos Endpoint Protection - the same on all of the servers.<br />
<br />
The rest of the logs show no other errors or warnings?
</div>


We are using Sophos Endpoint Protection - the same on all of the servers.

The rest of the logs show no other errors or warnings?

<div>
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
</div>


This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.

<div>
<div class="content wysiwyg-content">
Hey,<br />
<br />
We have a Windows Server 2008 R2 Standard machine working as a Terminal Server (TS1). We've recently noted the following critical error in the event log:<br />
<br />
DCOM was unable to communicate with the computer CSR|DC1 using any of the configured protocols.<br />
<br />
I have been looking into this error, everything on TS1 and DC1 firewall wise looks fine relating to DCOM Network Access (DCOM-In). I can telnet to both servers on the DCOM-In port 135, however the errors are still populating the event log on TS1<br />
<br />
Any ideas why this is occurring or where we can look further into this?<br />
<br />
Thanks
</div>
</div>


Hey,

We have a Windows Server 2008 R2 Standard machine working as a Terminal Server (TS1). We've recently noted the following critical error in the event log:

DCOM was unable to communicate with the computer CSR|DC1 using any of the configured protocols.

I have been looking into this error, everything on TS1 and DC1 firewall wise looks fine relating to DCOM Network Access (DCOM-In). I can telnet to both servers on the DCOM-In port 135, however the errors are still populating the event log on TS1

Any ideas why this is occurring or where we can look further into this?

Thanks

DCOM was unable to communicate with the computer CSR - Terminal Server 2008 R2 Standard (AP)

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.