title: ERR_CONNECTION_RESET when trying to access localhost on ASP.NET Web App project
body: <p>So I've been working on this webapp project in my desktop computer, but I had to transfer it to my laptop since I have gone on holiday. The code builds fine, but when I try to access the site (<a href="http://localhost:port" rel="noreferrer">http://localhost:port</a>) in Chrome I get an ERR_CONNECTION_RESET message. I've also tried with other browsers (<em>Firefox, Microsoft Edge, Opera</em>) and I get a similar message. I also created a New Project and tried to run it with the same result. IIS Express seems to run without problems. I tried running <code>netstat -ao</code> in the cmd to see if the port assigned to the URL was being used by something else. And it was being actually used by a process with the PID:4, which turned out to be <em>NT Kernel &amp; System</em>.</p>
  
  <p><strong>Things I've tried:</strong></p>
  
  <ul>
  <li>Self signing a certificate.</li>
  <li>Writing 127.0.0.1 in the URL instead of localhost</li>
  <li>Reinstalling IIS</li>
  <li>Deleting the config files to make IIS create new ones</li>
  <li>Modifying the <code>&lt;binding protocol="http" bindingInformation="*:port:localhost"/&gt;</code> removing the <code>localhost</code> part, leaving it like this: <code>&lt;binding protocol="http" bindingInformation="*:port:" /&gt;</code></li>
  <li>Changing the port in Project Properties => Web, doesn't matter which one I pick, PID:4 always uses it.</li>
  <li>Opening <code>RegEdit</code> and setting <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP</code>'s <code>start</code> attribute from 3 to 4, presumably stopping HTTP from listening to ports. Once I did this and rebooted the PC, I tried to run the dummy project again (the one which was only the template), and this time I got an <code>unable to launch the iis express web server</code>. I tried to work around it by reinstalling IIS and modifying the config, but it didn't work. At last, I decided to leave the 'start' attribute with value 3, and return to the <code>ERR_CONNECTION_RESET</code> since I wasn't sure it had been a step forwards or backwards.</li>
  </ul>