Description of names and IP addresses that an MSDTC client in a cluster environment must have (311846)
The information in this article applies to:
- Microsoft COM+ 1.0
- Microsoft Transaction Server 2.0
- Microsoft SQL Server
- Microsoft SQL Server 2000 (all editions)
- Microsoft Cluster Server
- Microsoft Internet Information Server 4.0
- Microsoft Internet Information Server 5.0
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard Edition
This article was previously published under Q311846 SUMMARY The purpose of this article is to help you in the setup or
in the troubleshooting of a configuration for a COM+ Application Server or a
configuration for an Internet Information Server (IIS) computer that interacts
with a clustered server that uses Microsoft Cluster Server (MSCS) that is
behind a firewall. You may have one of the following scenarios:
- COM+ or IIS computer (client computer)
- SQL Server clustered that uses MSCS
- Microsoft Distributed Transaction Coordinator (MSDTC) as a
clustered resource in its own resource group (own name and IP
address)
- Cluster and client computer that are separated by a
firewall
Certain Internet Protocol (IP) addresses and their
corresponding network names must be known by the client computer for MSDTC to
work correctly. The client computer can resolve the following names and the
following IP addresses by using Domain Name System (DNS), hosts file, or
another name resolution method:
- MSDTC resource
- An instance of SQL Server if the cluster configuration is
either active-passive or active-active
- Cluster Name
Certain IP addresses and their corresponding network names must
be known by the nodes in the cluster for MSDTC to work correctly. Both nodes in
the cluster can resolve the client computer name to an IP address by using DNS,
hosts file, or another name resolution method. REFERENCES
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
250367
Configuring Microsoft Distributed Transaction Coordinator (DTC) to work through a firewall
258469 Cluster service may not start after you restrict available IP ports for remote procedure call
For information about Distributed Component Object Model (DCOM) and Remote Procedure Call (RPC) with firewalls, visit the following Microsoft Web site:
Modification Type: | Major | Last Reviewed: | 4/7/2006 |
---|
Keywords: | kbsql2005cluster kbhowto kbinfo KB311846 kbAudDeveloper kbAudITPRO |
---|
|