Re: COM+/DTC + firewall + SQL Server = need help

From: Gert E.R. Drapers (GertD_at_Online.SQLDev.Net)
Date: 09/12/03


Date: Thu, 11 Sep 2003 16:12:26 -0700


Correct, you need to open a range of ports as described in:

INFO: Configuring Microsoft Distributed Transaction Coordinator (DTC) to
Work Through a Firewall
http://support.microsoft.com/default.aspx?scid=kb;EN-US;250367

Since you are only using one SQL Server, why are you using COM+ distributed
transactions? Are there any other resource managers involved? If not you are
wasting 15-16% performance for no functional gain what so ever and you are
adding the dependency for DTC communication to the system.

If you have no need for a distributed transaction stop using transactions
via COM+, use database transactions.

If you have multiple resource manager, and they are all SQL Server, you
might be able to switch it around and have the DTC instances between the SQL
Server involved, but leave the application server TM out of the picture, by
using T-SQL begin distributed transaction instead of starting the DTC
transaction on the application server.

GertD@SQLDev.Net

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2003 All rights reserved.

"Dave" <info@gartopia.com> wrote in message
news:04eb01c37865$0f226c10$a001280a@phx.gbl...
> I'm not sure this is the right place to post this but I'm
> hoping someone can help me. I have a problem involving
> COM+ components, the configuration of internal firewalls
> and SQL Server 2000.
>
> We have developed a set of components based on Microsofts
> COM+ technology. There is a Business Logic Layer (BLL)
> and a Data Access Layer (DAL) component. Both components
> have been configured to participate in distributed
> transactions within the COM+ environment. The DAL
> accesses a SQL Server 2000 database. My understanding
> is ... COM+ uses the Distributed Transaction Coordinator
> (DTC) which in turn uses RPC to coordinate transactions
> across multiple servers. Our configuration involves only
> 2 servers. The first server is our web and application
> server (with the ASP, BLL and DAL). The second server is
> the SQL Server 2000 server. There is a firewall between
> the 2 servers. RPC requires port 135 to be open. Since
> DTC requires RPC, DTC cannot coordinate transactions
> between the applcation server and the database server
> unless port 135 is open. Our security guys do not want
> to open 135 due to the latest round of viruses and worms.
>
> Sooooo, my question is .... Is there a way to configured
> DTC to work with a SQL Server database without opening up
> port 135? What do other companies do when they have COM+
> components and databases that run on separate servers and
> firewalls are involved? This seems like a common
> implementation. Don't other companies have similar
> concerns about this port? Is there a way to safely open
> port 135 for internal server-to-server communications?
>
> Any help will be greatly appreciated.
>
> -Dave G.
> Rockville, MD
> info@gartopia.com



Relevant Pages

  • Re: MS DTC has cancelled the transaction
    ... Some of my users carry out work via IE onto a third party provider's server. ... "Microsoft Distributed Transaction Coordinator has cancelled the ... It means they're using a system that may be distributed over multiple servers or services, co-ordinated by MS DTC. ... Steve Foster [SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • MS-DTC / SQL Server 2000
    ... Does MS SQL Server 2000 require MS DTC for anything besides ... distributed update transactions, where "distributed" means ... in such transactions, can I safely disable MS DTC on that box? ...
    (comp.databases.ms-sqlserver)
  • Re: DOES ANYONE FROM MICROSOFT KNOWS ABOUT THIS PROBLEM?!
    ... MS DTC started with the following settings: ... Network Administration of Transactions = 1, ... Distributed Transactions using Native MSDTC Protocol = 1, ... msdtc -resetlog.Then i start MS DTC and everything seems to be ok.My server ...
    (microsoft.public.windows.server.migration)
  • Re: DB design, facilitates Double entries of internal transactions
    ... The single server is also ... transactions, even if just a pair of ID's/amounts, is still double entry. ... but I would tend to recommend SQL Server ... Stored Procedures and transaction control on the server. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Transactions across batches
    ... Consider using the Server Defaults. ... set up default user connection environment settings. ... Set the ANSI compliant defaults: ANSI NULLS, ANSI WARNINGS, ANSI PADDING, ... Set CURSOR LOCAL, NOCOUNT ON, and IMPLICIT TRANSACTIONS ...
    (microsoft.public.sqlserver.server)