title: Windows Authentication fails in Application but succeeds in dedicated Site
body: <p>I am trying to configure 2 ASP.NET projects in IIS where one inherits from the other.</p>
  
  <p>The base uses anonymous authentication and the derived uses windows authentication.</p>
  
  <p>So the web.config can be inherited, I would like the derived to be an application inside the base site. I have configured this but keep receiving a 401.1 error when accessing the application that is the derived.</p>
  
  <p>To test my configuration I created a brand new website, pointing to the same physical folder, in the same application pool and configured windows authentication the same as the virtual directory. Accessing this works fine.</p>
  
  <p>I have 2 folders:</p>
  
  <pre><code>Base
  Derived
  </code></pre>
  
  <p>In IIS I have configured (causes the 401):</p>
  
  <pre><code>Base (Site, Anon + Windows (also tried just anon))
  |- Derived (Application, Windows)
  </code></pre>
  
  <p>and (works fine):</p>
  
  <pre><code>Derived (Site, Windows)
  </code></pre>
  
  <p>I created the separate derived site to prove to myself it wasn't permissions related to that folder or something in the web.config of the derived site causing problems.</p>
  
  <p>There are no authorization or authentication elements in the base web.config.</p>
  
  <p>The FDQN for both sites is present in my HOSTS file and the PC is in domain.</p>
  
  <p>Is there something special about applications inside sites that makes what I am trying to achieve impossible?</p>