title: MSDTC attempts to enlist client machine in a distributed transaction
body: <p>We're seeing the following intermittent warning logged by MSDTC:</p>
  
  <blockquote>
    <p>A caller has attempted to propagate a
    transaction to a remote system, but
    MSDTC network DTC access is currently
    disabled on machine 'X'. Please review
    the MS DTC configuration settings.</p>
  </blockquote>
  
  <p>However, MSDTC is disabled on machine X by design - it's a client machine, and has no business being enlisted in the transaction!  </p>
  
  <ul>
  <li>Several windows service endpoints hosting WCF services over TCP</li>
  <li>Single SQL Server 2005 instance beneath</li>
  <li>Linq to Sql</li>
  <li>Remote client receives event callbacks over WCF/TCP</li>
  </ul>
  
  <p>The issue is tricky to reproduce - usually following restart of services.  We suspect a callback to the client machine is occurring within the context of a transaction. </p>
  
  <p>Just wondering if anyone has seen similar issues?? </p>
  
  <p>Ken</p>