|
Posted by Erland Sommarskog on 09/14/06 15:47
This is some advice that we got from the support professional on our case:
Windows 2003 R2 has new DTC protection measures built-in and enabled
by default, since MSDTC is used for SQL Server purposes and this
machines don't have internet access there are no problem in set no
authentication required. In future if you upgrade your Windows 2000
machine to Windows 2003 SP1 or Windows 2003 R2 and they are in same
domain (this is a requirement) you can activate mutual authentication
in MSDTC and will not have any problem.
These steps are not documented but I let you some recommendations to
troubleshooting MSDTC problems.
1) Put security setting at the minimum level
2) Enable MSDTC logging and verify if anything appears on log file
3) Use DTCPing utility to avoid firewall problems
4) Verify if RPC is started before MSDTC and SQL Server is started
after MSDTC and RPC services.
5) Verify in SQL Server error log that MSDTC started with success
6) Please verify if you have COM/COM+ components enabled and with all
hot fixes installed
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|