>Perhaps someone else can comment on your global.asax configuration of the framework object -- I don't have enough experience in .NET to do that. It sure sounds like some kind of session mixup.
>
>There have been some documented cross-session mixups due to "kernel-mode output caching" under certain circumstances related to setting cookies -- basically resulting in the SetCookie being cached in the request and attaching other users to the same session via the cached SetCookie.
>
>This might not be at all related to your situation, but it's explained very well by Jeff Prosise in the MSDN Mag July 2006 issue: "Keep Sites Running Smoothly By Avoiding These 10 Common ASP.NET Pitfalls":
>
>http://msdn.microsoft.com/msdnmag/issues/06/07/WebAppFollies/
>
>(Look in the section on Sessions and Output Caching). This is one of the best articles I have seen on asp.net potential performance and session problems.

Thanks for the link

In my case, this is IIS 5 on Windows Server 2000. I also do not make any use of the .NET session. I simply use regular cookie for the authentication. But, IAC, the problem is on the result. Basically, I obtained the HTML output that the other user asked for instead of getting mine. As this has happened several times today, and we were under 2000 hits, this is a no go for deployment on a server that would run 1000000 hits a day. We will have to troubleshoot what causes such an unacceptable situation.