title: Remote Debugging .Net Core 2.0 on Windows 10 IoT
body: <p>I've written a Hello World console app in .Net Core 2.0 using VS 2017 and deployed the Debug build to a Raspberry Pi 3 running Windows 10 IoT. I can execute the app remotely via PowerShell and everything seems fine.</p>
  
  <p>Having installed the Visual Studio 2017 Remote Debugging tools, I'm now trying to hook up the Remote Debugger so as I can step through my code on the Pi and I'm running into problems.</p>
  
  <p>When I try to "Attach to process" from the Debug menu in Visual Studio and enter the IP and port number supplied by the IoT device portal I get the following error:</p>
  
  <blockquote>
    <p>Unable to connect to the Microsoft Visual Studio Remote Debugger named '192.168.1.139:8116'. Connection request was rejected by the remote debugger. Ensure that the remote debugger is running in 'Windows Authentication' mode.</p>
  </blockquote>
  
  <p><a href="https://i.stack.imgur.com/ZrYKq.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ZrYKq.png" alt="enter image description here"></a></p>
  
  <p>The following screenshot of the IoT Device Portal shows both the IP and Port for Remote Debug and the fact that my app (echo.exe) is running: </p>
  
  <p><a href="https://i.stack.imgur.com/bkKbK.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/bkKbK.png" alt="enter image description here"></a></p>
  
  <p>I've tried running the remote debugger both with and without the "Run as DefaultAccount" option checked, but this seems to make no difference.</p>
  
  <p>I've also checked the firewall settings on my dev PC to ensure that it is not blocking traffic (I am connecting over the Private network)</p>
  
  <p><a href="https://i.stack.imgur.com/TPFwL.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/TPFwL.png" alt="enter image description here"></a></p>
  
  <p>Although the error message warns about Windows Authentication Mode, I can find no such setting for the remote debugger. Any help in getting the Remote Debugger attached and operational would be gratefully received.</p>