List of UUIDs for MSDTC service to filter traffic on the firewall.

MSDTC communication over the network depends upon RPC. RPC functionality through a firewall requires that specific ports are open to accommodate RPC dynamic port allocation. How to configure RPC dynamic port allocation to work with firewalls describes how to enable MSDTC to communicate through a firewall with another MS DTC by opening port ranges on both sides.

Sometimes we may not want to open the port range for DTC traffic through the firewall and choose to put a filter on the firewall to allow traffic for certain UUIDs. Here is a list of UUID's used in DTC communication.

Endpoint Mapper Service : {E1AF8308-5D1F-11C9-91A4-08002B14A0FA}
MSDTC service : {906B0CE0-C70B-1067-B317-00DD010662DA}
RPC management Interface : {AFA8BD80-7D8A-11C9-BEF4-08002B102989}

These UUIDs are going to remain the same for any operating system as they are associated with standard protocols and services.

The following two UUID’s are for the DTCPing and WinRM tools that are used to check DTC communication between the two servers. You may like to configure the UUID’s for these tools too as we might need them for troubleshooting DTC communication issues:

WinRM : {2B7EE790-E8C8-4820-97DB-CDFF70129887}
DTCPing : {75687379-AAAA-44F6-9512-080AC70F8AD9}