title: Windows network drives through ssh and powershell
body: <p>When I physically go to the computer and initiate a powershell session, I am able to cd into a mapped drive (Z:), and run programs which access it.</p>
  
  <p>However when I initiate an ssh session, and try to <code>cd</code> or execute programs which access the drive it says the drive name doesn't exist, if I try and  map the drive with</p>
  
  <p><code>net use Z: \\192.168.36.3\c$\</code> </p>
  
  <p>It will tell me it is already mapped.  Programs which access the full path <code>Login failure: unknown user name or bad password</code>.</p>
  
  <p>If I try <code>cd \\192.168.36.3\c$\</code>, it will ask me for credentials, if I give my current user's credentials I will get</p>
  
  <p><code>System error 86  the specified network password is incorrect</code></p>
  
  <p>None of this happens when I walk up to the computer and run powershell.  </p>
  
  <p>The output of <code>$env:username</code> through ssh is the same for the physical session and the remote one, and it's a Windows 7 computer which I have installed BitVise ssh server, and before that freesshd.  I was able connect with both of them, but had the same problem with remote drives.  </p>
  
  <p>Is there something I have to do to get the same rights as I would physically?</p>
  
  <p>EDIT: <code>Get-PSDrive</code> physically has the mapped drive, but <code>Get-PSDrive</code> through SSH does not.  Am I not the user I am physically, despite <code>$env:username</code> telling me I am?</p>