title: Is it possible to use .NET Remoting + TLS 1.2 (or 1.1)?
body: <p>Recently our PCI DSS scan failed, and requires that we disable TLS 1.0 (and enable TLS 1.1 or 1.2). I found the instructions on how to do so on our Windows Server 2008 R2 box, but we have a legacy application that is using .NET Remoting (its a .NET 2.0 windows forms app/IIS hosted CSLA 1.5 data portal), which doesn't communicate with the new settings.</p>
  
  <p>I am getting the following exception:</p>
  
  <p><a href="https://i.stack.imgur.com/6FpqG.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/6FpqG.jpg" alt="enter image description here"></a></p>
  
  <p>I have attempted various configurations of combinations of TLS settings in both client and server to no avail. Such as:</p>
  
  <ol>
  <li>Disabling TLS 1.0 on both client and server (in the registry) and enabling TLS 1.2.</li>
  <li>Enabling TLS 1.1 on both client and server (in the registry).</li>
  </ol>
  
  <p>I have done some research and discovered that <a href="https://stackoverflow.com/questions/4137106/are-there-net-implementation-of-tls-1-2">.NET 4.5 framework supports TLS 1.1 and 1.2</a>, but it is unclear whether that extends to .NET remoting. Does it?</p>
  
  <p>Also, I found that <a href="https://support.microsoft.com/en-us/gp/framework_faq?wa=wsignin1.0" rel="nofollow noreferrer">Microsoft's recommendation is to upgrade to 4.5.2</a>.</p>
  
  <p>That said, this application has many dependencies and incompatibilities with .NET 4.5.2, so it would be helpful to know if I am indeed going in the right direction by upgrading or whether I should be in a mad rush to rewrite this application altogether (all options I have explored require major application changes). Even building a test application to try it out could be challenging, since I haven't dealt with .NET remoting directly in about 10 years.</p>
  
  <p>So, again my question is - does .NET remoting support TLS 1.1 or 1.2? </p>
  
  <p>Also:</p>
  
  <ol>
  <li>Is upgrading to .NET framework 4.5.2 enough to get it there? </li>
  <li>Are there more configuration settings that need to be put into place to make it communicate and if so, what are they?</li>
  <li>If upgrading to .NET framework 4.5.2 is all that is required, does the whole application need to be upgraded, just the parts that use .NET remoting, just the client that references the libraries that use .NET remoting, or some other combination?</li>
  </ol>
  
  <p>I am using:</p>
  
  <ol>
  <li>Windows Server 2008 R2 as a server.</li>
  <li>IIS 7.5 to host the remoting with SSL enababled (CSLA dataportal).</li>
  <li>Windows 7 Professional for the client.</li>
  </ol>