Communication with the underlying transaction manager has failed

How to resolve the error transaction via MSDTC are not working in our environment.

I leave here a solution:

Whenever an error occurs in transactions check the following points:

If this MSDTC enabled on both machines, client (where you run the web / app) and server
Check that the settings are correct
Check if the firewalls are not blocking requests
Check if the machines can "ping" each other by NetBios (by hostname)

In this case the problem was the point 4, for some reason we can not check because my
machine could ping the server, but the server could not ping my IP because it was being associated with another machine.

solution:

Remove the record of "HOST A" in the DNS Server for the machine you are having the error (in my case for some reason was not to renew
IP in the registry)

Then it was necessary to perform a reset to the router and efecutar a ipconfig / release followed by ipconfig / renew as well as a
ipconfig / flushdns on the server to clear the dns and get the correct ip.