What are the dangers of utilizing the "No validation expected" in MSDTC

  • In our current circumstance we have two servers on two separate areas (one is in DMZ, other in inside organization) and we really want them to have the option to utilize dispersed exchanges. The exchanges would be started from the server on the inside network through connected server. The server on the DMZ would simply have the option to permit inbound exchanges. It appears to be that the best way to do this is to arrange the MSDTC with "no confirmation required" , as well as opening firewalls and altering the net profiles have record to make DNS passages on the two servers. What are the security suggestions/gambles if any of utilizing the "no confirmation required" exchange mode? Does this open up our inside arrange to expected assaults/weaknesses?

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply