title: Networked drive in purgatory after `net use` start-up script
body: <p>I have a BAT file that runs on startup via the group policy on an internal server. The BAT executes a nant script which then maps several external locations via <code>net use</code> command. Until now, all mappings have been to external computers that are part of a different domain via public IPs. </p>
  
  <pre><code>net use e: \\111.111.111.111\someshare$ /persistent:yes
  net use f: \\111.111.111.222\someshare$ /persistent:yes
  net use g: \\111.111.111.333\someshare$ /persistent:yes
  </code></pre>
  
  <p>This has been successful. Now, I added a new computer that is part of the <em>same network and domain</em> as the internal server. While the old mappings continue to work, the new mapping does not.</p>
  
  <pre><code>net use h: \\anothercomputer\d$\somefolder /persistent:yes
  </code></pre>
  
  <p>I only know that this doesn't work because subsequent scripts that depend on this drive mapping are all failing, saying that the location doesn't exist. If I try to run the same connection script manually, <code>net use</code> says</p>
  
  <blockquote>
    <p>System error 85 has occurred... The local device name is already in use.</p>
  </blockquote>
  
  <p>Ok, so it mapped already somewhere, somehow. So I try to unmap it using <code>net use h: /d</code> and that fails.</p>
  
  <blockquote>
    <p>The network connection could not be found.</p>
  </blockquote>
  
  <p>So I cannot map it. I cannot unmap it. Apparently it exists in some networking purgatory. What is going on here? How can I get this new location mapped and visible to my scripts?</p>