Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two servers, a web application server and an SQL Server database running on its own server.

I have a firewall between these two servers.

Do I have to open port 135 on both the SQL Server and the Web Application Server.

Does the SQL Server open its own connection to the Web Application Server on port 135 or any other port?

Do I have to in component services point the Web Application Server MSDTC at the SQL Database Server?

If the firewall is completely open, the settings in component services set to allow remote connections, remote administration etc is there any other settings that need to be changed in order to allow remote connections to the SQL Server MSDTC?

share|improve this question

I ran wireshark on this and found out the answers to my questions

  1. yes you have to open 135 on both sql server and application server

  2. No you don't have to use a remote transaction co-ordinator, you can use the local one

  3. Yes if there is no firewall and all the local DTC settings in component services are set to allow incoming and outgoing traffic then there is no obstacle to the DTC working across multiple servers.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.