title: MSDTC from a standalone machine to a domain machine
body: <p>The issue is that we have a website on a standalone webserver (Windows 2003 SP2 - Machine name is TESTAPP which can be sen in the log below) which uses TransactionScope.</p>
  
  <p>The SQL Server 2008 R2 machine (Windows Server 2008) is within a domain.</p>
  
  <p>When the standalone machine hit's the TransactionScope it fails (error details will ensue).</p>
  
  <p>When I run the code from a machine in the same domain as the DB server it works fine.</p>
  
  <p>On the standalone machine I get the ubiquitous error of:</p>
  
  <pre><code>Error HRESULT E_FAIL has been returned from a call to a COM component.
  </code></pre>
  
  <p>However MSDTC is setup correctly, it uses Network Service by the way. DTCPing.exe works fine both ways.</p>
  
  <p>Upon digging into the DB machine i found the following Audit Failure:</p>
  
  <p>An account failed to log on.</p>
  
  <pre><code>Subject:
  Security ID:        NULL SID
  Account Name:       -
  Account Domain:     -
  Logon ID:       0x0
  
  Logon Type:         3
  
  Account For Which Logon Failed:
  Security ID:        NULL SID
  Account Name:       TESTAPP$
  Account Domain:     WORKGROUP
  
  Failure Information:
  Failure Reason:     Unknown user name or bad password.
  Status:         0xc000006d
  Sub Status:     0xc0000064
  
  Network Information:
  Workstation Name:   TESTAPP
  Source Network Address: 192.168.**.**
  Source Port:        1202
  </code></pre>
  
  <p>The standalone machine is trying to logon to SQL Server machine using it's own machine name, god knows what it is using as a password.</p>
  
  <p>Therefore is it possible to get MSDTC to work from a standalone machine to a domain machine?</p>
  
  <p>P.S. If possible (if there is another way) I don't want to affect 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity' registry key.</p>
  
  <p>P.P.S. If possible I'd like to keep Mutual Authentication Required on MSDTC, (I'm aware that a possible solution is to set MSDTC to require No Authentication, but am not sure if this is totally necessary)</p>
  
  <p>The wierd thing about it is using a test standalone web server to domain DB server MSDTC is working fine whether set to No Authentication or Mutual Authentication! :S</p>
  
  <p>P.P.S. Firewalls are off on both machines.</p>