[kjrice]

Another area to look at is the way ASP.NET invokes the w3wp.exe process in IIS 6.0, which can eat up memory and cause an application to disconnect. There is a bug that affects applications, but obviously that is not the case here. Since I assume there is only a single application, then fencing IIS should not be of concern.

I would not suggest clustering a SQL environment although it is easily done. One area to be aware of is DTC and how it relates.

Within hardware, you can setup your data on separate controllers, gate NICs, and /or setup network load balancing. My guess would be the user's hardware/OS configuration and architecture state, in conjunction with the ISP's ability to efficiently access the network associated with EE. Make sure your internet options file setting is not over 20Mb. I can almost guarantee memory is on the minimal end and virtual memory is set to OS managed. If not, I would at least set it to 125% of current memory and make it static to avoid fragmentation. In general, you are only as fast as your slowest link. :lol: