MSDTC message not working over VPN
I have an application that starts transactions spanning multiple databases on the same server. Naturally this has to do with the Microsoft Distributed Transaction Coordinator and everything works as intended.
However, when I remotely connect to a network where the server is hosted via VPN and runs the application on my local machine, I get the following error:
System.Transactions.TransactionManagerCommunicationException : "Error communicating with the primary transaction manager."
Caused by:
System.Runtime.InteropServices.COMException:
HRESULT E_FAIL was returned from a call to a COM component.
Here is the stack trace for the outgoing exception:
in System.Transactions.Oletx.IDtcProxyShimFactory.ReceiveTransaction (UInt32 propgationTokenSize, Byte [] propgationToken, IntPtr managedIdentifier, Guid & transactionIdentifier, OletxTransactionIsolationLevel & isolLevel, ITransactionShim & tranzaktsiyaShim)
in System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken (Byte [] propagationToken)
The problem only occurs when connecting to the server via a VPN tunnel.
Also note that I temporarily disabled Windows Firewall on my local machine just to make sure it doesn't block MSDTC.
Does anyone know of any issues when running MSDTC over VPN?
source to share
Are you administering a VPN connection? VPN may have limited ports. Likewise, do you administer your servers? Your servers can only allow connections from IP addresses inside, not from the segment used for the VPN service. If you are an administrator, you can tell which VPN software will help you.
source to share
I suggest you run DTCPing (available from Microsoft's site somewhere). This runs simultaneously on both machines and detects all kinds of DTC problems.
Be careful, I had a lot of difficulty with this tool until I actually read the instructions and started both sides of the test before I pressed the start button.
source to share
I have the same problem with Windows 7 x64 client and Server 2003R2 server. I was able to get it to work (on the same vpn, same server) using XP, Vista x86, and Windows 7 x86. I have a support call with Microsoft open and they are looking into it. I am curious what operating system are you using on your client computers?
source to share