Potential risks of using unsecure RPC (No Authentication Required setting) in MSDTC security configuration

When your MSDTC machine is accessible from an un-authenticated client, i.e. machine outside your domain/firewall. Then when such a machine tries to talk to this MSDTC server, the MSDTC server will accept such requests, so in all it could allow requests from a machine outside the domain(as long as it can reach the MSDTC server/ports)…

1

MSDTC security settings getting reset on a cluster server if the DomainControllerState key value is set to 1.

  There are two Windows server 2003 SP2 nodes on the Veritas cluster and both of them are Domain Controllers. Under the registry hive HKLM\software\Microsoft\MSDTC\Security, the value of DomainControllerState is set to “1” (Node 1) and “2” (Node 2) respectively. When we move over the resources from node1 to node2, all the MSDTC security settings…

0

COM+ : 8000FFFF – Catastrophic Failure

On a windows 2003 server, when we open Component services MMC –> complus Applications, we get the following error :   Catalog error:  An error occured while processing the last operations error code 8000FFFF – Catastrophic Failure the event log may contain additional troubleshoooting information   The system was very sluggish and slow in responding….

3

0x8004D027 : MSDTC was unable to read its configuration information.

On a two node Windows 2003 SQL server cluster, while running the SP 2 setup for SQL server 2005, we were getting the following error : Error Description : MSP Error: 29549 Failed to install and configure assemblies C:\Program Files (x86)\Microsoft SQL Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087 Error message: Unknown error 0x80131501 Error…

1