Thanks for all your help everybody. I now have some ammunition to move forward and try to solve all these problems.
Mark -----Original Message----- From: Jacob [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 13, 2001 11:48 AM To: CF-Server Subject: Re: Web Server location At 10:28 AM 12/13/2001 -0500, you wrote: >Good Morning All, > >I've got a couple odd problems and I'm all out of ideas as to where the >problem might lay. > >Set-up: Win2K, IIS 5, 1/2 gig RAM, 60 gig HD, CF5, PIII 800Mhz - The Web >Server is connected by a full T-1 to the Internet and is physically >located behind a Cisco Rounter and a Firewall Put the server in front of the firewall for now to see what happens. You can create an access-list in the router the limits what traffic goes to the server, i.e. port 80, 443, etc... >Traffic: Maybe 100 people per day. The app is a medium sized Extranet. >The Extranet is used for viewing documents (text, html and pdf's) Very >simple stuff. We do use session variables, but all are locked >appropriately. We use SQL Server 2000 which is located on a DB Server, >not the Web Server. About 98% of the queries are stored procedures. > >Problem: Clients complain that the Extranet is slow. We, of course, >don't see this problem when viewing internally since we're connected to >the Web Server through a full T-3. I also experience lag when viewing >the Extranet from home (I have IDSL 144K). One thing, in particular, >that I notice is that the blue status bar (when using IE) seems to hang >for about 2-3 seconds after the page has loaded. It doesn't matter what >page I'm viewing either. For example - I view a page with a lot of >content and then view a page with just a login form on it and the blue >status bar still hangs for the 2-3 seconds no matter what page I'm >viewing. Also, I keep receiving NT error 232 in the Web Server logs and >I can't seem to figure out where they're coming from. > >Are there any settings in either IIS or CF Admin that I should be paying >attention to? As for the 232 error - What should I look at to fix this. 232 means browser was closed or the client moved on before the output was returned. Probably because of being to slow. Also, do trace routes from home to make sure there are no issues with traffic. But if you can sufrf the net without any problem, then the problem would most not likely lie there. >These problems are very frustrating because the powers that be here tend >to point their fingers at Windows, IIS and CF as the problem. I don't >feel that those things are the problem. If anything, they're not set-up >properly. At 100 hits a day, Windows is not the problem. >Thanks in advance for all your help. > >Mark Stewart >Programmer/Analyst >CC3 >Phone: 215.672.6900 x1332 >http://www.cc3.com > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
