Another "Communication with the underlying transaction manager has failed."

Client: Windows XP SP2 with all updates, server: Windows Server 2003 SP1 woth all updates. Any distributed transactions fail with "Communication with the underlying transaction manager has failed" if "Mutual Authentication Required" or "Incoming Caller Authentication Required" selected. If "No Authentication Required" selected things work.

Running DTCPing revealed "Access denied" when server tries to communicate back to client. Here is the part of DTCPing server log:

++++++++++++++++++++++++++++++++++++++++++++++
DTCping 1.9 Report for
++++++++++++++++++++++++++++++++++++++++++++++
RPC server is ready
01-11, 11:21:30.668-->RPC server: received following information:
Network Name: SQL01
Source Port: 2694
Partner LOG: XPS3816.log
Partner CID: 8EFE6A42-5BEE-44AB-88EB-90AB29EF6242
++++++++++++Start Reverse Bind Test+++++++++++++
Received Bind call from XPS
Network Name: SQL01
Source Port: 2694
Hosting Machine:
01-11, 11:21:30.793-->Trying to Reverse Bind to XPS...
Test Guid:8EFE6A42-5BEE-44AB-88EB-90AB29EF6242
Name Resolution:
XPS-->172.16.100.163-->xps.hbm2.com

-->RPC reverse BIND failed
-->5(Access is denied.)
Reverse Binding to XPS Failed
In GUID
Out GUID
Reverse BIND FAILED
Session Down

What is wrong

Thank you,
Alex

.NET Development13

I am also facing a similiar issue but in my case, even after selecting "No Authentication Required" as the authentication mode, RPC fails.

++++++++++++++++++++++++++++++++++++++++++++++
DTCping 1.9 Report for IS2
++++++++++++++++++++++++++++++++++++++++++++++
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
01-29, 18:33:16.265-->Start DTC connection test
Name Resolution:
hp-->192.168.100.10-->HP
01-29, 18:33:17.968-->Start RPC test (IS2-->hp)
Problem:fail to invoke remote RPC method

-->RPC pinging exception
-->1722(The RPC server is unavailable.)
RPC test failed

My Server and Client both have XP Prof. with SP2.

please help....I am unable to figure out wats the prob....

Thanks,

Vinay

Guys, don't know if you resolved your issue or not (hope so after all this time), but see here:

http://dhanley.spaces.live.com/Blog/cns!3FF1F23549F62959!119.entry

Cause: Tracked down Access is Denied issue (see: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=321086&SiteID=1) to the fact that DHLAPTOP2 was blocking Remote Clients (i.e. GLA1AS32). On DHLAPTOP2 created the key HKLM\SOFTWARE\Policies\Microsoft\Windows NT\RPC and added the value RestrictRemoteClients (DWORD, 0). See: http://msdn.microsoft.com/security/productinfo/XPSP2/networkprotection/restrict_remote_clients.aspx for more details.

This got DTCPing to work for me.

I have this same issue, but I don't have this reg key. Any idea why that would be

I am running the most current version of XP Pro.

Trying to get to the bottom of these issues is next to impossible.