iis-7.5

Short version: For IIS 7.5 web applications with Windows Authentication does the end user need to have Read file access? Long version: I have an intranet ASP.NET web app that uses windows authentication. It's installed at dozens of different companies and normally the authentication works fine: users navigate to the site e.g. http://appserver/MyApp , the app recognizes who they're logged in as and displays pages accordingly. I just installed it at a new client and encountered a problem: When connecting e.g. to http://appserver/MyApp I'm prompted for windows credentials but after entering them

I'm using IIS 7.5 on Windows Server 2008 R2 x64 Enterprise Edition. In the project we have developed with ASP.NET 4.0 we used WCF Service. But it doesn't run over domain when the software is running from local computer. Otherwise, I am getting the following error: HTTP Error 404.3-Not Found The page you are requesting cannot be served because of the extension configuration. If the page is script, add a handler. If the file should be downloaded, add a MIME map. Mekanik You should install IIS sub components from Control Panel -> Programs and Features -> Turn Windows features on or off Internet

This is a question that continues to haunt me... In an local Intranet environment, are we doomed to use "Classic" pipeline mode in our App Pool if we want to use Impersonate our Windows domain users, or is there a new way to declaratively "run as" them (so-to-speak)? My goal is to use Windows Authentication for local web applications on my Intranet so users can authenticate and run apps under their active directory account (principle). Every time I try this (Using the NetworkService identity of course), I get this error: Thanks! ;) I wrote a small app to display the current user's network

My development team is using ASP.NET 3.5 / 4.0 right now, and our sites are running on IIS 7.5. Recently, we've been having problems (about once a week) that are causing Out of Memory exceptions to be thrown in our ASP.NET applications. The "Solution" is to restart the application pool on our website. I say "Solution" because it's hardly a solution; it's more of a bandage that's just keeping our application pool running at a reasonable state. It seems to me that some application or many applications are leaking memory, which is building up over time and causing the out of memory exception.

I need some help setting up FTP on my Azure VM instance. The VM is Windows Server 2012 R2. I have set up the Web Server Role and created an FTP site in IIS. I have confirmed that I can access the FTP server with ftp command: open localhost I have also configured an FTP end point for the VM on the Azure Portal configured for the standard port 21. Lastly, I have created a firewall rule to allow all traffic in/out of port 21. Now when I try to FTP to it from my home machine I can see the server public DNS name is resolving to the proper IP and port but no connection can be made. Am I missing a