iis-6

I have a requirement for an explicit logout button for users in a ASP.NET web app. I am using IIS6 with Basic Authentication (SSL). I can redirect to another web page but the browser keeps the session alive. I have googled around and found a way to do it by enabling an active x control to communicate with IIS and kill the session. I am in a restricted environment that does not allow forms authentication and active x controls are not forbidden as well. Has anyone else had this requirement and how have you handled it? Okay that is what I was afraid of. I have seen similar answers on the net and

I am developing an internally-facing application that needs to automatically authenticate users via Windows Authentication and fall back to Forms authentication. The fall back would occur in situations where the user on a computer logged in as a group account (such as an operations center). I'm concerned about security where a user could "spoof" the Windows Authentication account. Do any of you all know of a design pattern and pragmatic idea that would fit this specific scenario? Technical Constraints: .NET 3.5 on IIS 6 (IIS 7 is currently a non-starter in our environment) Thanks! There's an

I'm deploying an ASP.NET application to Windows Server 2003 under IIS IIS is serving html pages fine but I get a page not found when I try and serve IIS pages You may need to "register" IIS for ASP.NET applications. As an administrator, run the command "%systemroot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i". In addition, you may need to convert your web site to an application through the IIS management console. By default, IIS has ASP support disabled in IIS6. A server running a member of the Microsoft® Windows® Server 2003 family supports application server functionality, with

We have Windows 2003 Servers running SQL Server 2005 and .NET 3.5 [separately]. We have a basic ASP.NET app running on IIS 6. What, if anything, do I need to do on the application end [IIS,Framework,ASP.NET] to make it IPv6 compatible? EDIT: We do use System.DirectoryServices, System.DirectoryServices.DirectoryEntry and DirectorySearcher() to authenticate users against AD. Would those calls have to change? Rob The first thing to do would be search your code for any references to System.Net.IPAddress , and see how you're passing information around in those areas: Are you performing any "manual"

I have a library that I created with some business logic that includes writing to a System.Diagnostics.EventLog instance. The library is normally called from a Windows Service application, but now I'm trying to call those same library functions from my ASP.NET MVC application. I tried this code inside my controller to create the EventLog instance that I pass into the method that needs to write to the log. Dim log = New EventLog("Application", My.Computer.Name, "MyMVCApp") The following error is generated when the code within the library method tries to write to the log: [SecurityException:

I am trying to get ASP.Net MVC 4 working on IIS6 and am running into the always fun Directory Listing Denied error. Before you start posting about extensionless urls and how I need to read the Haacked blog post.. I have :) So with that out of the way here is the setup: I have created a new Web Site and configured it to use ASP.Net 4.0. I had to do this because the existing Default Web Site is configured for ASP.Net 2.0 and this breaks extensionless urls. Under the new web site I created a Virtual Directory with Read/Write/Log Vists/Index this resource options selected and execute permissions