DTCPing: Troubleshooting MSDTC Connectivity Issueshttp://blogs.msdn.com/florinlazar/archive/2005/09/16/469064.aspxIn today's world, security hardening is causing many headaches to software developers and admins. Especially when you have an application that needs to go beyond the boundaries of the local machine. MSDTC is a distributed app by definition and thus, gettingen-USCommunityServer 2.1 SP1 (Build: 61025.2)re: DTCPing: Troubleshooting MSDTC Connectivity Issueshttp://blogs.msdn.com/florinlazar/archive/2005/09/16/469064.aspx#469766Sat, 17 Sep 2005 05:29:46 GMT91d46819-8472-40ad-a661-2c78acb4018c:469766Tomas RestrepoDTCPing and DTCTester are both very useful tools in diagnosing DTC access issues. However, I believe they are pushed sometimes as *the* tools to use, instead of fixing the real problem: The DTC is way, way too poor at giving the caller good error codes/messages, and most of the time just downright fails with an E_FAIL or unknown error. Heck, it doesn't even leave a message in the machine's Event Log. <br> <br>I really wish you guys devoted some time to improving the internal diagnostic code in the DTC instead...re: DTCPing: Troubleshooting MSDTC Connectivity Issueshttp://blogs.msdn.com/florinlazar/archive/2005/09/16/469064.aspx#476704Tue, 04 Oct 2005 07:27:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:476704florinlazarTo: Tomas <br>Thanks for the feedback. I agree with you. DTC was &quot;born&quot; as a service that was supposed to run in the background and you should never have to be concerned about it. Only COM+ or SQL Server will deal with it. <br> <br>With the amount of security hardening that happened in the last years, suddenly the scenarios using transactions started to fail and the users needed to be aware of DTC. How do I get it to work? <br> <br>We have the Tracing feature that might help a little but I know it's not enough. We are looking into improving the user experience and our troubleshooting story.