title: 'net use' over SSL fails unless port 443 is specified
body: <p>We are attempting to connect to a WebDAV server using <em>net use</em> over SSL.  On some servers we're seeing an issue in which this connection only succeeds if we specify port 443 in the URL.</p>
  
  <p><strong>Does Map</strong></p>
  
  <p><code>net use * "https://example.com:443/folder"</code><br/>
  <code>net use * "\\example.com@SSL@443\folder"</code></p>
  
  <p>and, bizarrely, so does this:
  <code>net use * "\\example.com@SSLasdf\folder"</code></p>
  
  <p><strong>Does Not Map</strong></p>
  
  <p><code>net use * "https://example.com/folder"</code><br/>
  <code>net use * "\\example.com@SSL\folder"</code></p>
  
  <p>In the non-working cases we consistently receive the following error:</p>
  
  <p><code>System error 67 has occured.</code><br/>
  <code>The network name cannot be found.</code></p>
  
  <p>We have noticed some things that might be useful information:</p>
  
  <ul>
  <li>We have a test server that's configured the same way as the prod server and it works as expected.</li>
  <li>In the non-working cases, no incoming requests are ever seen at the prod server from the failing host.</li>
  <li>All clients are based on the same image.</li>
  <li>The problem does not manifest uniformly on all clients -- some work, some don't.</li>
  <li>There is an existing, valid entry for example.com in the client DNS cache.</li>
  <li>Flushing the client DNS cache of the affected servers does not resolve the problem.</li>
  <li>Once the problem appears, it seems to stick.  That is, if I execute one of the working mappings, delete it, and then immediately execute one of the non-working mappings, the problem persists.</li>
  </ul>
  
  <p>We are utterly stumped.  Any theories?</p>