title: Consuming SSL SOAP Service, could not establish secure channel for SSL/TLS
body: <p>I'm working on a <code>Windows Mobile 6.5 Pro</code> application, using <code>.NET Compact Edition 3.5</code>.</p>
  
  <p>I'm able to contact the standard web service (not using SSL), but <code>HTTPS</code> won't go through. I've attempted to add another Web reference ; this one pointing to the HTTPS version. I was assuming it would generate the proper code for SSL, but nothing.</p>
  
  <p>Every time I attempt to communicate with the service via code I get the following:</p>
  
  <blockquote>
    <p>An existing connection was forcibly closed by the remote host. Could
    not establish secure channel for SSL/TLS.</p>
  </blockquote>
  
  <p><strong>I tested the same code on a <code>.NET 4.5</code> console app and I was able to successfully reach the HTTPS Web service</strong> and get back XML response without issues. </p>
  
  <p><strong>It appears that the generated Web Refence on VS2008 for HTTPS is missing something?</strong> </p>
  
  <p>There's not much code to show here besides the auto-generated code that VS2008 produces when you add a new Web Reference.</p>
  
  <p><strong>UPDATE 1:</strong>
  I've been following this post which appears to be the same issue i'm encountering but sadly I don't think it was resolved.
  <a href="https://stackoverflow.com/questions/27642714/how-can-i-establish-a-secure-channel-for-ssl-tls-from-a-handheld-device">How can I establish a secure channel for SSL/TLS from a handheld device?</a></p>
  
  <p><strong>UPDATE 2:</strong>
  After more research, Windows Mobile 6.5 Pro only appears to support TLS v1.0 while the SOAP Service I was attempting to communicate with is v1.2 (latest).</p>
  
  <p>A bit on TLS and SSL: <a href="https://www.wolfssl.com/wolfSSL/Blog/Entries/2010/10/7_Differences_between_SSL_and_TLS_Protocol_Versions.html" rel="nofollow noreferrer">Here</a>. </p>
  
  <p><strong>WS 2003</strong> had SSL 2.0/3.0 and TLS 1.0 enabled by default. The default installation did not support AES ciphers – but support could be added through a hotfix.</p>
  
  <p><strong>WS 2008</strong> also had SSL 2.0/3.0 and TLS 1.0 enabled by default, but improved the cryptographic support with new AES cipher suites.</p>
  
  <p><strong>WS 2008 R2</strong> introduced TLS 1.1 and TLS 1.2, but they were disabled by default.</p>
  
  <p><strong>WS 2012</strong> takes us a step further with TLS 1.2 enabled by default.</p>